Understand Cost Management data

This article helps you better understand Azure cost and usage data that's included in Cost Management. It explains how frequently data is processed, collected, shown, and closed. You're billed for Azure usage monthly. Although billing cycles are monthly periods, cycle start and end dates vary by subscription type. How often Cost Management receives usage data varies based on different factors. Such factors include how long it takes to process the data and how frequently Azure services emit usage to the billing system.

Cost Management includes all usage and purchases, including reservations and third-party offerings for Enterprise Agreement (EA) accounts. Microsoft Customer Agreement accounts and individual subscriptions with pay-as-you-go rates only include usage from Azure and Marketplace services. Support and other costs aren't included. Costs are estimated until an invoice is generated and don't factor in credits. Cost Management also includes costs associated with New Commerce products like Microsoft 365 and Dynamics 365 that are invoiced along with Azure. Currently, only Partners can purchase New Commerce non-Azure products.

If you have a new subscription, you can't immediately use Cost Management features. It might take up to 48 hours before you can use all Cost Management features.

Supported Microsoft Azure offers

The following information shows the currently supported Microsoft Azure offers in Cost Management. An Azure offer is the type of the Azure subscription that you have. Data is available in Cost Management starting on the Data available from date. Summarized data in cost analysis is only available for the last 13 months. If a subscription changes offers, costs before the offer change date aren't available.

Category Offer name Quota ID Offer number Data available from
Azure Government Azure Government Enterprise EnterpriseAgreement_2014-09-01 MS-AZR-USGOV-0017P May 2014¹
Azure Government Azure Government Pay-As-You-Go PayAsYouGo_2014-09-01 MS-AZR-USGOV-0003P October 2, 2018
Enterprise Agreement (EA) Enterprise Dev/Test MSDNDevTest_2014-09-01 MS-AZR-0148P May 2014¹
Enterprise Agreement (EA) Microsoft Azure Enterprise EnterpriseAgreement_2014-09-01 MS-AZR-0017P May 2014¹
Microsoft Customer Agreement Microsoft Azure Plan EnterpriseAgreement_2014-09-01 N/A March 2019²
Microsoft Customer Agreement Microsoft Azure Plan for Dev/Test MSDNDevTest_2014-09-01 N/A March 2019²
Microsoft Customer Agreement supported by partners Microsoft Azure Plan CSP_2015-05-01, CSP_MG_2017-12-01, and CSPDEVTEST_2018-05-01⁴ N/A October 2019
Microsoft Developer Network (MSDN) MSDN Platforms³ MSDN_2014-09-01 MS-AZR-0062P October 2, 2018
Pay-As-You-Go Pay-As-You-Go PayAsYouGo_2014-09-01 MS-AZR-0003P October 2, 2018
Pay-As-You-Go Pay-As-You-Go Dev/Test MSDNDevTest_2014-09-01 MS-AZR-0023P October 2, 2018
Pay-As-You-Go Microsoft Cloud Partner Program MPN_2014-09-01 MS-AZR-0025P October 2, 2018
Pay-As-You-Go Free Trial³ FreeTrial_2014-09-01 MS-AZR-0044P October 2, 2018
Pay-As-You-Go Azure in Open³ AzureInOpen_2014-09-01 MS-AZR-0111P October 2, 2018
Pay-As-You-Go Azure Pass³ AzurePass_2014-09-01 MS-AZR-0120P, MS-AZR-0122P - MS-AZR-0125P, MS-AZR-0128P - MS-AZR-0130P October 2, 2018
Visual Studio Visual Studio Enterprise – MPN³ MPN_2014-09-01 MS-AZR-0029P October 2, 2018
Visual Studio Visual Studio Professional³ MSDN_2014-09-01 MS-AZR-0059P October 2, 2018
Visual Studio Visual Studio Test Professional³ MSDNDevTest_2014-09-01 MS-AZR-0060P October 2, 2018
Visual Studio Visual Studio Enterprise³ MSDN_2014-09-01 MS-AZR-0063P October 2, 2018

¹ For data before May 2014, visit the Azure Enterprise portal.

² Microsoft Customer Agreements started in March 2019 and don't have any historical data before this point.

³ Historical data for credit-based and pay-in-advance subscriptions might not match your invoice. See Historical data may not match invoice below.

⁴ Quota IDs are the same across Microsoft Customer Agreement and classic subscription offers. Classic CSP subscriptions are not supported.

The following offers aren't supported yet:

Category Offer name Quota ID Offer number
Azure Germany Azure Germany Pay-As-You-Go PayAsYouGo_2014-09-01 MS-AZR-DE-0003P
Cloud Solution Provider (CSP) Microsoft Azure CSP_2015-05-01 MS-AZR-0145P
Cloud Solution Provider (CSP) Azure Government CSP CSP_2015-05-01 MS-AZR-USGOV-0145P
Cloud Solution Provider (CSP) Azure Germany in CSP for Microsoft Cloud Germany CSP_2015-05-01 MS-AZR-DE-0145P
Pay-As-You-Go Azure for Students Starter DreamSpark_2015-02-01 MS-AZR-0144P
Pay-As-You-Go Azure for Students³ AzureForStudents_2018-01-01 MS-AZR-0170P
Pay-As-You-Go Microsoft Azure Sponsorship Sponsored_2016-01-01 MS-AZR-0036P
Support Plans Standard support Default_2014-09-01 MS-AZR-0041P
Support Plans Professional Direct support Default_2014-09-01 MS-AZR-0042P
Support Plans Developer support Default_2014-09-01 MS-AZR-0043P
Support Plans Germany support plan Default_2014-09-01 MS-AZR-DE-0043P
Support Plans Azure Government Standard Support Default_2014-09-01 MS-AZR-USGOV-0041P
Support Plans Azure Government Pro-Direct Support Default_2014-09-01 MS-AZR-USGOV-0042P
Support Plans Azure Government Developer Support Default_2014-09-01 MS-AZR-USGOV-0043P

Free trial to pay-as-you-go upgrade

For information about the availability of free tier services after you upgrade to pay-as-you-go pricing from a Free trial, see the Azure free account FAQ.

Determine your offer type

If you don't see data for a subscription and you want to determine if your subscription falls under the supported offers, you can validate that your subscription is supported. To validate an Azure subscription is supported, sign in to the Azure portal. Then select All Services in the left menu pane. In the list of services, select Subscriptions. In the subscription list menu, select the subscription that you want to verify. Your subscription is shown on the Overview tab and you can see the Offer and Offer ID. The following image shows an example.

Example of the Subscription Overview tab showing Offer and Offer ID

Costs included in Cost Management

The following tables show data that's included or isn't in Cost Management. All costs are estimated until an invoice is generated. Costs shown don't include free and prepaid credits.

Included Not included
Azure service usage (including deleted resources)⁵ Unbilled services (e.g., free tier resources)
Marketplace offering usage⁶ Support charges - For more information, see Invoice terms explained.
Marketplace purchases⁶ Taxes - For more information, see Invoice terms explained.
Reservation purchases⁷ Credits - For more information, see Invoice terms explained.
Amortization of reservation purchases⁷
New Commerce non-Azure products (Microsoft 365 and Dynamics 365) ⁸

⁵ Azure service usage is based on reservation and negotiated prices.

⁶ Marketplace purchases aren't available for MSDN and Visual Studio offers at this time.

⁷ Reservation purchases are only available for Enterprise Agreement (EA) and Microsoft Customer Agreement accounts at this time.

⁸ Only available for specific offers.

Please note Cost Management data only includes the usage and purchases from services and resources that are actively running. Cost data is historical and will include resources, resource groups, and subscriptions that have been stopped, deleted, or cancelled and may not reflect the same resources, resource groups, and subscriptions you see in other tools, like Azure Resource Manager or Azure Resource Graph, which only show the current resources that are deployed in your subscriptions. Not all resources emit usage and therefore may not be represented in the cost data. Similarly, some resources are not tracked by Azure Resource Manager and may not be represented in subscription resources.

How tags are used in cost and usage data

Cost Management receives tags as part of each usage record submitted by the individual services. The following constraints apply to these tags:

  • Tags must be applied directly to resources and aren't implicitly inherited from the parent resource group.
  • Resource tags are only supported for resources deployed to resource groups.
  • Some deployed resources may not support tags or may not include tags in usage data.
  • Resource tags are only included in usage data while the tag is applied – tags aren't applied to historical data.
  • Resource tags are only available in Cost Management after the data is refreshed.
  • Resource tags are only available in Cost Management when the resource is active/running and producing usage records. For example, when a VM is deallocated.
  • Managing tags requires contributor access to each resource or the tag contributor RBAC role.
  • Managing tag policies requires either owner or policy contributor access to a management group, subscription, or resource group.

If you don't see a specific tag in Cost Management, consider the following questions:

  • Was the tag applied directly to the resource?
  • Was the tag applied more than 24 hours ago?
  • Does the resource type support tags? Some resource types don't support tags in usage data. See Tags support for Azure resources for the full list of what is supported.

Here are a few tips for working with tags:

  • Plan ahead and define a tagging strategy that allows you to break down costs by organization, application, environment, and so on.
  • Group and allocate costs using tag inheritance to apply resource group and subscription tags to child resource usage records. If you were using Azure policy to enforce tagging for cost reporting, consider enabling the tag inheritance setting for easier management and more flexibility.
  • Use the Tags API with either Query or UsageDetails to get all cost based on the current tags.

Cost and usage data updates and retention

Cost and usage data is typically available in Cost Management within 8-24 hours. Keep the following points in mind as you review costs:

  • Each Azure service (such as Storage, Compute, and SQL) emits usage at different intervals – You might see data for some services sooner than others.
  • Estimated charges for the current billing period are updated six times per day.
  • Estimated charges for the current billing period can change as you incur more usage.
  • Each update is cumulative and includes all the line items and information from the previous update.
  • Azure finalizes or closes the current billing period up to 72 hours (three calendar days) after the billing period ends.
  • During the open month (uninvoiced) period, cost management data should be considered an estimate only. In some cases, charges may be latent in arriving to the system after the usage actually occurred.

The following examples illustrate how billing periods could end:

  • Enterprise Agreement (EA) subscriptions – If the billing month ends on March 31, estimated charges are updated up to 72 hours later. In this example, by midnight (UTC) April 4.
  • Pay-as-you-go subscriptions – If the billing month ends on May 15, then the estimated charges might get updated up to 72 hours later. In this example, by midnight (UTC) May 19.

After your billing period ends and your invoice is created, it can take up to 48 hours later for the usage data to get finalized. If the usage file isn't ready, you'll see a message on the Invoices page in the Azure portal stating Your usage and charges file is not ready. After the usage file is available, you can download it.

Once cost and usage data becomes available in Cost Management, it will be retained for at least seven years. Only the last 13 months are available from the portal. For historical data before 13 months, please use Exports or the Cost Details API.

Rerated data

Whether you use the Cost Management APIs, Power BI, or the Azure portal to retrieve data, expect the current billing period's charges to get rerated. Charges might change until the invoice is closed.

Cost rounding

Costs shown in Cost Management are rounded. Costs returned by the Query API aren't rounded. For example:

  • Cost analysis in the portal - Charges are rounded using standard rounding rules: values more than 0.5 and higher are rounded up, otherwise costs are rounded down. Rounding occurs only when values are shown. Rounding doesn't happen during data processing and aggregation. For example, cost analysis aggregates costs as follows:
    • Charge 1: $0.004
    • Charge 2: $0.004
    • Aggregate charge rendered: 0.004 + 0.004 = 0.008. The charge shown is $0.01.
  • Query API - Charges are shown at eight decimal places and rounding doesn't occur.

Historical data might not match invoice

Historical data for credit-based and pay-in-advance offers might not match your invoice. Some Azure pay-as-you-go, MSDN, and Visual Studio offers can have Azure credits and advanced payments applied to the invoice. The historical data shown in Cost Management is based on your estimated consumption charges only. Cost Management historical data doesn't include payments and credits. Historical data shown for the following offers may not match exactly with your invoice.

  • Azure for Students (MS-AZR-0170P)
  • Azure in Open (MS-AZR-0111P)
  • Azure Pass (MS-AZR-0120P, MS-AZR-0123P, MS-AZR-0125P, MS-AZR-0128P, MS-AZR-0129P)
  • Free Trial (MS-AZR-0044P)
  • MSDN (MS-AZR-0062P)
  • Visual Studio (MS-AZR-0029P, MS-AZR-0059P, MS-AZR-0060P, MS-AZR-0063P)

Next steps

  • If you haven't already completed the first quickstart for Cost Management, read it at Start analyzing costs.