Azure-CSP billing export column headers use camelCase iso PascalCase

[jcoetsie]

Azure CSP cost record export files use camelcase iso PascalCase as column header names.

billingAccountName,partnerName,resellerName,resellerMpnId,customerTenantId,customerName,costCenter,billingPeriodEndDate,billingPeriodStartDate,servicePeriodEndDate,servicePeriodStartDate,date,serviceFamily,productOrderId,productOrderName,consumedService,meterId,meterName,meterCategory,meterSubCategory,meterRegion,ProductId,ProductName,SubscriptionId,subscriptionName,publisherType,publisherId,publisherName,resourceGroupName,ResourceId,resourceLocation,location,effectivePrice,quantity,unitOfMeasure,chargeType,billingCurrency,pricingCurrency,costInBillingCurrency,costInUsd,exchangeRatePricingToBilling,exchangeRateDate,serviceInfo1,serviceInfo2,additionalInfo,tags,PayGPrice,frequency,term,reservationId,reservationName,pricingModel,unitPrice

When using the Azure provider, it fails due to this

columns_missing = [ │ │ │ │ │ 'BillingAccountId', │ │ │ │ │ 'BillingAccountName', │ │ │ │ │ 'BillingCurrencyCode', │ │ │ │ │ 'BillingPeriodEndDate', │ │ │ │ │ 'BillingPeriodStartDate', │ │ │ │ │ 'ConsumedService', │ │ │ │ │ 'CostInBillingCurrency', │ │ │ │ │ 'Date', │ │ │ │ │ 'PublisherName', │ │ │ │ │ 'ResourceLocation', │ │ │ │ │ ... +2

[varunmittal91]

hi @jcoetsie , should there be a different provider for azure-csp?

[jcoetsie]

Hi,

I think so as several issues occur when using Azure CSP cost exports:

• Different columns compared to Azure EA cost exports

• Azure reservation cost (commitments) are billed at 0; extra steps are needed to create a cost record that has all data. Microsoft states it too (Reservation purchases are only available for Enterprise Agreement (EA) and Microsoft Customer Agreement accounts at this time.) (https://learn.microsoft.com/en-us/azure/cost-management-billing/costs/understand-cost-mgt-data#costs-included-in-cost-management)

So, another converter light be a good idea that is if it is technically feasible to convert the CSP based billing data. I do not think it is... It will need to be assessed by this team on the technical feasibility.

If not, we should state azure convertor is only for Azure EA and Azure CA customers.