Focus Mapping for Azure requires columns that are either not present or empty in Azure's CUR

[prathmeshrks]

Describe the bug
According to Azure to Focus Mapping below Azure Mappings require columns that are unavailable or empty in Azure's CUR of type Cost and usage details (actual)

1. Below Focus column uses BillingPeriodStartDate but the value is empty in Azure CUR:
   1.1 ChargePeriodStart
   1.2 BillingPeriodStart
   1.3 BillingPeriodStart

2. Below Focus column uses BillingPeriodEndDate but the value is empty in Azure CUR:
   2.1 BillingPeriodEnd

3. Below Focus column uses BillingCurrencyCode but the value is not present in Azure CUR:
   3.1 BillingCurrency

4. Below Focus column uses AvailabilityZone but the value is not present in Azure CUR:
   4.1 AvailabilityZone

I would appreciate if someone could point me in the right direction to correctly map these column values. Note that I am using Azure's CUR of type Cost and usage details (actual). Does the mapping rules apply for all the formats that Azure allows exporting their CUR report in?

To Reproduce
NA

Expected behavior
NA

Screenshots
NA

Desktop (please complete the following information):
NA

Additional context
NA

[gauthamarcot]

AvailabilityZone, BillingAccountId, BillingAccountName,
BillingCurrencyCode, BillingPeriodEndDate, BillingPeriodStartDate, ChargeType,
ConsumedService, CostInBillingCurrency, Date, Frequency, PricingModel,
PublisherName, Quantity, ResourceLocation, ResourceName, SubscriptionName

these are required but the cur schema have these columns in azure
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,benefitId,benefitName,provider
as @prathmeshrks as already raised its not accurate and throwing and except please do look into this