Azure Cost Management and Billing

Microsoft Cost Management is the set of cost tools within Azure Cost Management and Billing: it shows, analyses and monitors Microsoft Cloud costs for every scope a user has access to, from the billing account down to a resource group, while the Billing side manages the billing account, payments and invoices. Microsoft itself describes Cost Management as a suite of FinOps tools. Which costs you can see in it is decided by two things that have little to do with technology: the scope in which someone holds a role, and the agreement under which the company buys Azure. Knowing both explains why two people see different totals for the same month.

How it works

Cost Management works with scopes of two kinds. The Azure RBAC scopes are management group, subscription and resource group; a role assigned there applies to every scope beneath it. The billing scopes depend on the agreement: under an Enterprise Agreement (EA) they are billing account, department and enrollment account; under a Microsoft Customer Agreement, billing account, billing profile and invoice section; for a Cloud Solution Provider under a Microsoft Customer Agreement, billing account, billing profile and customer. Pay-as-you-go subscriptions have no billing scope of their own above the subscription.

On RBAC scopes, Cost Management Reader can view cost data and recommendations, and Cost Management Contributor can also manage budgets, exports and shared views; Microsoft recommends the latter as the least-privilege role. Neither grants access to invoices. Billing scopes use the agreement's own roles: under an EA, for example, enterprise administrator, department administrator and account owner; under a Microsoft Customer Agreement, owner, contributor, reader, invoice manager and Azure subscription creator.

Cost analysis presents costs in views. Smart views summarise costs by resource, resource group, service, subscription or reservation, with key figures and insights such as anomalies; customisable views such as Accumulated costs let you choose period, granularity, grouping and filters, and can be saved, shared and subscribed to as scheduled alerts. Behind them sit two datasets: actual cost, with purchases as they are charged, and amortized cost, with commitments spread over the usage that benefits. The smart views for resources, services and subscriptions use actual cost, the reservations view amortized cost. At daily granularity a view should span at most three months. The forecast reaches up to a year ahead and rests on a linear regression over history; Microsoft recommends at least 90 days of data.

For EA and Microsoft Customer Agreement accounts, costs usually appear within 8 to 24 hours; for pay-as-you-go, within up to 72 hours. Until the invoice, every amount is an estimate, and credits, taxes and support are not included. The portal shows the last 13 months.

Budgets with alerts are available on every scope Cost Management supports; they are the subject of the chapter Budgets, forecasts and finance. Anomaly alerts report a daily-detected anomaly in usage, a spike or a dip, and are available for subscriptions only.

Exports write cost data to a storage account on a schedule: actual and amortized cost, price sheets, reservation data, and a dataset in the FOCUS format that combines actual and amortized cost in one file. They run daily with month-to-date costs or monthly for the previous month, as CSV or Parquet. The portal can re-export up to 13 months of history, the Exports REST API up to seven years. What that data holds is the subject of the chapter Billing data and standards. For on-demand retrieval there is the Cost Details API, which Microsoft recommends for small datasets: its reports refresh every four hours, and above 2 GB a month Microsoft points to exports.

What it means for your cost

Which scope a team needs depends on which costs it owns. A subscription shows the usage of its resources. Purchases that are not usage-based, such as reservations or Marketplace offers, are visible under an EA only at the billing account, not in a department or enrollment account, and under a Microsoft Customer Agreement only at the billing profile, not in an invoice section. Management groups roll up usage-based charges only, which is why a billing account and the root management group can show different totals.

The agreement decides what is there at all. For EA and Microsoft Customer Agreement accounts, Cost Management includes all usage and purchases, reservations and savings plans among them; for accounts under the Microsoft Online Services Agreement, Marketplace purchases and commitment purchases are missing. The Cost Details API is open only to EA and Microsoft Customer Agreement customers, FOCUS exports are not available for MOSP scopes, and Cost Management does not support classic CSP or sponsorship subscriptions.

On other clouds the documentation says little. Microsoft describes Cost Management as a tool for Microsoft Cloud costs: Azure, Microsoft 365, Dynamics 365 and Power Platform. The cost details field reference notes, against a former AWS field, that the cross-cloud connector has been deprecated. AWS cost is read in the AWS console, as AWS Cost Explorer and AWS Budgets describes, or in a shared data basis.

Where it goes wrong

• Access at the wrong scope. A team gets Cost Management Reader on its subscription and cannot find its reservation purchase, which sits only at the billing scope. The other way round, department users under an EA see no cost at all while the billing account's "DA view charges" setting is off, even if they own the subscription.
• Actual cost where amortized was needed. In actual cost a reservation appears as a one-off purchase and the usage it covers shows as zero. Charging teams on that basis gives one team the whole prepayment and the others free resources. Allocation needs amortized cost.
• Exports that start too late. A daily export created between the first and fifth day of a month does not produce the previous month, and the first run can take up to 24 hours. An export set up at month-end close does not have the data when it is needed.
• Reservations missing from the subscription. A reservation purchase is tied to one billing subscription, while with a shared scope its benefit applies to usage in other subscriptions. The result is shared cost that no single subscription shows in full.
• Every feature assumed under every agreement. A management group report works under an EA and fails after the move to a Microsoft Customer Agreement, because Cost Management does not support management groups there. The documentation lists the scopes, exports and APIs each agreement offers feature by feature.

Sources

Read on 2026-10-15. Microsoft overview of Cost Management, Cost Management scopes, understand Cost Management data, start using cost analysis, create and manage exports, exports or the Cost Details API, cost details fields.