Open sxdjt opened 8 months ago
Hi @sxdjt,
We had a working group call today, two ppl on the call confirmed that out-of-the-box Azure Export datasets have both of these fields. I feel this is more likely connected to converter's validation logic. There is a sample file in the repo, I'd recommend checking out the validator --help flag to see the argument that can help you pass in the sample data for testing.
Hello @csyvenkyteck - I downloaded the sample file and the conversion ran as expected.
I'm not sure why I am missing those fields in the exported data. Is there a difference between exporting from Azure Portal vs. using the cost management API? I can't imagine there would be, but...
I confirm that in our org, those two fields do not exist in the raw billing exports. (EA agreement, US-based).
@sxdjt, @MmmmJoel, I'm unsure what else I can add. My previous posts assumed you are using the Azure Cost Mgmt. Export facility on an EA account type.
Just to verify, today I called the following APIs and can confirm yet again these fields exist in the output:
https://management.azure.com/providers/Microsoft.Billing/billingAccounts/{{billingAccount}}/providers/Microsoft.CostManagement/costDetailsOperationResults/
@csyvenky-finops I think that is the issue; exporting the data from Azure Portal gives different results that using the API. Not sure if Microsoft intended that or not...
Describe the bug
After downloading an Azure EA detailed billing file and running the converter, it fails saying
BillingCurrencyCode, CostInBillingCurrency' not found in data
.To Reproduce Steps to reproduce the behavior:
Expected behavior The converter runs as advertised.
Screenshots See attached files containing detailed error message and the headers of the downloaded billing file.
Desktop (please complete the following information):
csv_headers.txt error_out.txt