PayG monthly export columns not matching documentation

Question

PayG monthly export columns not matching documentation

Erik Post 70

Hello, I have a question on monthly exports created for a Pay-as-you-Go subscription (offer ID MS-AZR-0003P). When I run the export and look at the resulting file, the included columns do not match the documentation on https://learn.microsoft.com/en-us/azure/cost-management-billing/automate/understand-usage-details-fields. For example column InvoiceId is missing, as well as BillingPeriodStart and BillingPeriodEndDate, to name a few.

Also some columns are named differently, for example UsageDateTime instead of Date.

How can I get the format as documented on https://learn.microsoft.com/en-us/azure/cost-management-billing/automate/understand-usage-details-fields?

1 answer

Your answer

Answer 1

Ryan Hill 30,326 Microsoft Employee Moderator

Trying using API outlined in Get cost details for a pay-as-you-go subscription documentation. You can also try using the CLI command az costmanagement export create --name DemoExport --type Usage \--scope "subscriptions/00000000-0000-0000-0000-000000000000" --storage-account-id cmdemo \--storage-container democontainer --timeframe MonthToDate --storage-directory demodirectory, see Get usage data with the Azure CLI. Using the API is the preferred method for PAYG. I've reached out to the team for any additional clarity and will update with any findings.

Erik Post 70 Reputation points

2023-07-04T11:36:41.1533333+00:00

Hi Ryan, thanks for your reply.

I tried creating a new export via Azure CLI, but this yields the same result as defining an export via the Portal. As in, the columns in the resulting CSV do not match the documentation on Understand usage details field. But maybe I'm misunderstanding what data is available for what subscription and account types?

One difference I could see is that with Azure CLI it is possible to specify a timeframe value of TheLastBillingMonth, which is very useful for my purposes. It seems that this timeframe is not available via the Portal.
Ryan Hill 30,326 Reputation points Microsoft Employee Moderator

2023-07-06T14:14:52.33+00:00

@Erik Post this is being investigated; however, I was advised to do a minor change to the PowerShell command. For --type use the value of ActualCost or AmortizedCost instead of Usage. Usage as been deprecated and new fields aren't added to that dataset.
Erik Post 70 Reputation points

2023-07-07T08:40:47.42+00:00

Hi Ryan, thanks for looking into this.

I tried creating the export with azure cli and type set to ActualCost but this results in an error message that ActualCost is not a valid value and that the only valid value is Usage.

So if indeed the Usage dataset is different than the ActualCost or AmortizedCost datasets that would explain the difference in fields. For a CSP account I have exports set up that have type ActualCost and that data matches the fields in the documentation.

So question now is how to get the ActualCost dataset for the PayG subscriptions?

Share via

PayG monthly export columns not matching documentation

1 answer

Your answer