Azure Cost Management: How to Set Budgets, Alerts and Exports, and What Each Discount Saves

By The Uptime Report Team · Last reviewed: October 2026

Azure cost management runs in Microsoft Cost Management, free with Azure: set budgets and alerts first, then cut rates with reservations (up to 72% off) or savings plans (up to 65%), per Microsoft’s October 2026 pricing pages.

What is Azure cost management, and what does Microsoft Cost Management include?

Azure cost management is the job of tracking, allocating and cutting Azure spend. Microsoft’s own tool for it, Microsoft Cost Management, “is available at no additional cost as part of Azure” on supported offers, per the Microsoft Cost Management product page (October 2026). It bundles cost analysis, budgets, alerts, exports and cost allocation, and Azure Advisor feeds it rightsizing and commitment recommendations.

A budget never stops a resource. Microsoft’s budget tutorial says “Resources aren’t affected, and your consumption isn’t stopped” when a threshold is crossed. The only built-in hard stop is the Azure spending limit, and Microsoft says it “isn’t available for subscriptions with commitment plans or with pay-as-you-go pricing”; it exists on free accounts (a USD 200 limit) and credit-based subscriptions such as Visual Studio.

How do you set up budgets and alerts in Microsoft Cost Management?

Open the subscription or resource group in the Azure portal, select Budgets, set an amount and reset period, then add at least one percentage threshold with an email recipient. Add a forecasted alert so the warning lands before the money is spent. Microsoft allows up to five thresholds and five recipients per budget and evaluates budgets every 24 hours, per its Create and manage budgets tutorial.

1. Open the scope. Sign in to the Azure portal, open Subscriptions, pick the subscription and select Budgets in the menu. For a resource group: Cost Management + Billing > Subscriptions > your subscription > Resource groups > your resource group > Budgets > Add.
2. Filter and name it. Check the scope, add filters such as a resource group or the Virtual Machines service, and type a budget name.
3. Pick the reset period. Monthly, Quarterly or Annually follow the calendar. Pay-as-you-go, MSDN and Visual Studio subscriptions can instead use Billing month, Billing quarter or Billing year to match the invoice.
4. Set an expiration date. The budget resets to the same amount each period and is deleted when it expires.
5. Enter the amount. The portal suggests one from the highest forecasted cost. Quarterly and annual amounts are split evenly across the months.
6. Add alert conditions. For each line choose Type (Actual or Forecasted), a % of budget between 0.01% and 1000%, and up to five email addresses. Add azure-noreply@microsoft.com to approved senders.
7. Attach an action group (optional). Select Manage action group to trigger automation; this works on subscription and resource group budgets only.
8. Add an anomaly alert. From Azure Home select Cost Management, confirm the subscription scope, then Cost alerts > + Add > Alert type: Anomaly. This needs the Cost Management Contributor role or higher, per Microsoft’s anomaly guide.

A starting alert set for one subscription

The five lines below are our suggested starting configuration, not a Microsoft default. They use all five thresholds a budget allows: one forecasted line for early warning and four actual-cost lines that escalate from the subscription owner to finance and, at 100%, to an action group. Adjust the percentages to the client’s tolerance.

How fast does each cost signal arrive?

No Cost Management signal is real time. Cost data typically lands 8 to 24 hours after the usage, budgets are evaluated every 24 hours and emails go out within an hour of an evaluation. Stacked, spend at hour 0 can be visible by hour 24, caught by the next evaluation by hour 48 and emailed by hour 49 (our arithmetic on the budgets tutorial).

Microsoft’s own pages disagree on budgets for a new subscription. The Cost Management data page says “at subscription creation time you can immediately configure a budget”, while the budgets tutorial says a new subscription “can’t immediately create a budget” and may need up to 48 hours. Create each landing subscription at least two days before cutover so its budget is in place either way, and add that step to the wave plan in your public cloud migration runbook.

How do you allocate Azure costs with tags?

Turn on tag inheritance so subscription and resource group tags are stamped onto every child resource’s usage records, then group cost analysis by tag. Microsoft applies inherited tags to the current month within 24 hours, and the setting works on Enterprise Agreement (EA), Microsoft Customer Agreement (MCA) and Microsoft Partner Agreement (MPA) Azure plan accounts, per its tag inheritance guide.

1. Open Cost Management (not Cost Management + Billing) at an EA billing account, MCA billing profile or subscription scope.
2. Under Settings (Configuration, Manage billing profile or Manage subscription), edit Tag inheritance and turn on automatic application of subscription and resource group tags.
3. Pick the winner on a clash: resource tags by default, or the inherited tag if your tagging lives at subscription level.

Inherited tags are written to usage records, not to the resources, so an Azure Policy rule that audits untagged resources still flags them. Shared costs such as a hub network need cost allocation rules (Settings > Configuration > Cost allocation), which split cost by fixed whole-number percentages or in proportion to compute, storage, network or total cost. The invoice itself does not change.

For MSPs the catch is scope: Microsoft lists cost allocation rules for EA, MCA-E and MCA-online customers only, and they exclude reservations and savings plans. A CSP customer on an Azure plan gets tag inheritance but not allocation rules, so chargeback for those tenants runs on tags exported into your own reporting.

How do you export Azure cost data on a schedule?

Create a Cost Management export that writes cost files to an Azure Storage account daily or monthly, as CSV (optionally Gzip) or Parquet (optionally Snappy). Microsoft says data should land within 4 hours of a run starting (the whole process can take up to 24 hours), and an existing export can be rerun for up to 13 months of history in one-month chunks, per the exports tutorial.

1. In Cost Management pick a billing scope, then Exports > + Create and a template.
2. Add datasets (up to 10 per flow): cost and usage details in FOCUS format, which combines actual and amortized cost, plus price sheet or reservation data if you resell commitments.
3. Point it at a blob or file storage account and choose the format; partitioning is always on and schedules run in UTC.

Partners exporting from the partner billing account or a customer tenant need an active subscription in the CSP tenant, and storage firewalls work only in the same tenant, not for cross-tenant exports (Microsoft Learn, exports tutorial). For CSP clients, export monthly to a storage account the client owns: Microsoft says cost history stays with the old billing account when a client moves to a new partner, and those files are what your PSA or billing tool, the kind compared in our MSP software guide, needs for chargeback.

Which Azure discounts save the most, by Microsoft’s own numbers?

Spot Virtual Machines carry the highest stated discount, up to 90%, followed by Azure Hybrid Benefit stacked with reservations (up to 80% for Windows Server, up to 85% for SQL Server), Azure Reservations alone (up to 72%) and Azure savings plan for compute (up to 65%). Where Microsoft footnotes a maximum, it rests on one specific resource, usually a single VM in East US, per its pricing pages as of October 2026.

Two fine-print rules change the math. Reservation discounts “apply only to the infrastructure costs and not to the software costs”, so a Windows VM without Hybrid Benefit still pays its Windows meter (Microsoft Learn). Savings plan for compute likewise “doesn’t cover software, networking, or storage charges” (Microsoft Learn, savings plan overview).

Reservation or savings plan: what order does Microsoft recommend?

Microsoft’s decision guide says reservations give the greatest savings for stable workloads that will not change instance family or region, and savings plans suit workloads that move between families, services or regions. It recommends a five-step order that removes waste before any commitment is bought:

1. Right-size first: “Discounts reduce rates, not waste.”
2. Exchange underutilized reservations into better-fitting ones.
3. Trade in underutilized reservations for savings plans when usage is variable.
4. Buy new reservations only for stable, well-understood workloads.
5. Add savings plans last, sized to a clean, optimized baseline.

Exchange rules tighten soon. From February 1, 2027, new reservations for services that savings plans support, including Azure Virtual Machines, are not exchangeable; reservations bought before that date keep one final exchange. Refunds stay capped at USD 50,000 of cancelled commitment in a 12-month rolling window per billing profile or enrollment, and Microsoft charges no early termination fee for now (Microsoft Learn, exchanges and refunds).

What does one D4s v5 VM cost under each discount?

A Standard_D4s_v5 Linux VM (4 vCPUs, 16 GiB of memory) in East US lists at $0.192 an hour pay-as-you-go, or $140.16 a month at 730 hours. A 3-year reservation, $1,993 for the term, brings that to $55.36 a month, 60.5% less; a 1-year reservation at $1,038 saves 38.3%. All prices come from the Azure Retail Prices API on October 20, 2026.

Method: we queried the free, unauthenticated Retail Prices API with api-version 2023-01-01-preview, the only version that returns savings plan rates. Reservation rows carry the total price for the term even though their unitOfMeasure field reads “1 Hour”, so we divided by 12 or 36 months. A month is 730 hours (8,760 hours in a 365-day year divided by 12). Spot prices move with capacity; the $0.040531 rate is a snapshot.

A commitment is paid whether the VM runs or not, so the real question is how many hours it runs. Pay-as-you-go cost rises with every hour; a 1-year reservation wins above 61.7% of the year’s hours ($1,038 divided by $1,681.92), a 3-year reservation above 39.5%, a 1-year savings plan above 68.6% and a 3-year savings plan above 46.0%, assuming no other usage absorbs the savings plan commitment (our arithmetic on the API prices).

The Windows version: why Hybrid Benefit matters more than the term

The same VM running Windows lists at $0.376 an hour, $274.48 a month. Of that, $0.184 an hour ($134.32 a month) is the Windows license, which no reservation discounts. Azure Hybrid Benefit removes it, and Hybrid Benefit plus a 3-year reservation brings the bill to $55.36, 79.8% less, close to Microsoft’s “up to 80%” claim on the Hybrid Benefit page.

Hybrid Benefit has its own floor: Microsoft requires a minimum of 8 Windows Server core licenses per VM, so this 4-vCPU D4s v5 still consumes 8 (Microsoft Learn, Azure Hybrid Benefit for Windows Server). Switching an existing VM’s license type only changes a metadata flag and does not restart it. The Windows VM pricing page puts it plainly: “Azure covers the cost of the OS, while you pay for just the VM compute costs.” The benefit lasts only for the Software Assurance or subscription license term; when that lapses Microsoft says you must renew, disable the benefit or deprovision, so track renewal dates beside the support dates in our Windows Server end of life tracker.

Do other VM sizes and regions get closer to Microsoft’s headline discounts?

No. Across 6 Linux sizes in East US and West Europe, every 3-year reservation the API prices saved 60.5% after rounding (60.48% to 60.51%), 11.5 points under Microsoft’s “up to 72%”, and 3-year savings plans saved 45.0% to 56.2% against “up to 65%”. West Europe D-series savings plans saved 9 points less than East US, per the Retail Prices API on October 26, 2026.

For a client quote, that means modelling 60.5% for a 3-year reservation and 45% to 56% for a 3-year savings plan on general-purpose Linux sizes, not Microsoft’s maximums. West Europe also lists the D4s v5 at $0.23 an hour, 19.8% above East US, so a region move can outweigh the commitment choice.

What do Azure Advisor cost recommendations check?

Azure Advisor flags a VM for shutdown when the P95 of maximum CPU stays under 3%, the P100 of average CPU over the last 3 days is 2% or less, and outbound network stays under 2% across 7 days. It recommends a smaller SKU only when the new size keeps utilization under set ceilings, per Microsoft’s Advisor VM recommendation rules.

Treat the dollar figure on a resize recommendation as a ceiling. Microsoft says the recommendations “don’t take into account the presence of Reserved Instances (RI) / Savings plan purchases”, so listed savings can exceed what is possible, and a cross-series resize can raise cost if the old size was reserved. Check reservation coverage before acting, and match it to the downtime rules in the client’s uptime commitments.

How do MSPs run Azure cost management for CSP customers?

For Cloud Solution Provider (CSP) partners, Microsoft Cost Management works only for subscriptions moved to the Azure plan under a Microsoft Customer Agreement. Admin agents and billing admins see invoiced costs in the partner tenant; customers see nothing until the partner enables the cost visibility policy, and then they see pay-as-you-go retail rates, per Microsoft’s Cost Management for partners guide.

1. Sign in to the partner tenant, open Cost Management + Billing and select the billing scope.
2. Select Customers and pick the customer (the list does not appear if you are signed in to the customer tenant).
3. Set the cost visibility policy for Azure usage charges to Yes. Admin agents can set it for many customers through the Update Customer API.

What keeps partner earned credit switched on?

Partner earned credit (PEC) depends on access, not on the invoice. Microsoft requires an active Microsoft AI Cloud Partner Program agreement and an eligible Azure RBAC role on the customer’s resources, set up through admin on behalf of (AOBO), Azure Lighthouse or named accounts, and it calculates PEC daily. Microsoft’s own example shows a 15% PEC turning a USD 10 unit price into USD 8.5 (Partner Center, how PEC is calculated).

Customers can remove that access at any time, and Microsoft says partners who “coerce customers to assign them appropriate access for the sole purpose of earning partner earned credit” risk losing eligibility (Partner Center, PEC overview). AOBO is also not recreated automatically after a subscription transfer. Month-end check: in the partner tenant’s cost analysis, group by PartnerEarnedCreditApplied, list each customer showing False, and compare that subscription’s Access control (IAM) assignments against your eligible role.

What should a managed Azure agreement spell out?

Write down five things the Microsoft documents leave to the partner and client: who holds access, who owns commitments, which rate the client is quoted, what automation may stop, and where cost history lives. Each line below maps to a Microsoft rule that bites when the contract is silent.

• Access: the partner identity and RBAC role on each subscription, since PEC is recalculated daily from that access.
• Commitments: who pays for a reservation bought on the customer’s scope. Refunds are capped at USD 50,000 per 12 months per Microsoft Partner Agreement customer, and VM reservations bought after February 1, 2027 cannot be exchanged, so a 3-year term can outlive a 1-year contract (Microsoft Learn).
• Rates: whether quotes follow the retail pay-as-you-go view the client sees in the portal or your invoice price, as set out in your managed IT services pricing.
• Auto-stop authority: which resource groups a budget runbook may stop, and at which threshold.
• Data: a monthly export to client-owned storage, because cost history does not follow a client to a new partner.

Which Azure cost lever should you pull first?

Remove idle resources first, then move interruptible work to Spot, apply Hybrid Benefit and Dev/Test pricing, and only then buy commitments. For a D4s v5 in East US, a 1-year reservation needs the VM running more than 61.7% of hours to beat pay-as-you-go, and a 3-year reservation more than 39.5%, based on Retail Prices API list prices for October 2026.

How do you make an Azure budget actually stop VMs?

Chain four pieces: a budget, an Azure Monitor action group, a Logic App that reads which threshold fired, and an Azure Automation runbook that stops VMs. Microsoft’s budget scenario stops VMs in a noncritical resource group at 80% of a monthly budget and every VM at 100%. It reacts only after the up-to-48-hour lag shown earlier.

1. Automation account and runbook. Create an Azure Automation account with a managed identity (Run As accounts “retired on 30 September 2023”, per Microsoft Learn) and give that identity at least the Virtual Machine Contributor role on the target scope. Import the Stop Azure V2 VMs runbook from the Runbook gallery, now served from Microsoft’s Azure Automation GitHub organization; its README says it signs in with the system-assigned identity.
2. Two webhooks. Create webhook “Optional” with the noncritical resource group as its parameter and webhook “Complete” with none. Copy both URLs at creation: Microsoft says they cannot be viewed again.
3. Logic App. Trigger: When an HTTP request is received. Parse JSON on the budget payload, then branch on NotificationThresholdAmount: at least 0.8 and below 1 posts to Optional; 1 or more posts to Complete. Add an email action to each branch. With a single threshold, Microsoft says you can call the runbook straight from the action group and skip the Logic App.
4. Action group. Monitor > Alerts > Manage actions > add an action group with a Logic App action pointing at step 3.
5. Budget. Create the budget at subscription or resource group scope (action groups work nowhere else), add actual-cost thresholds at 80% and 100%, attach the action group, and filter to Publisher Type: Azure and Charge Type: Usage so a reservation purchase cannot trip it (budgets tutorial).

Check that the runbook deallocates. Microsoft’s Stop-AzVM reference says the -StayProvisioned switch “stops a virtual machine, but does not deallocate it. The account is charged for the stopped virtual machine.” Even deallocated VMs keep paying for disks and networking (Microsoft Learn, VM states and billing), and the recipe touches VMs only, so App Service plans and databases keep billing.

How we compiled this

We compiled this from 36 primary Microsoft sources: 26 Microsoft Learn and 2 Partner Center articles, 7 Azure pricing and product pages and Microsoft’s Stop Azure V2 VMs runbook README, plus Azure Retail Prices API queries for 6 Linux VM sizes in East US and West Europe, all accessed October 20 to 26, 2026. Prices are Microsoft list prices in USD; monthly, annual and break-even figures are our arithmetic at 730 hours a month. We did not test any tool or customer tenant, and negotiated EA, MCA and CSP prices will differ.

Frequently asked questions

How do I enable Azure Cost Management?

The switch sits in a different place for each agreement. On an MCA, a Billing Profile Owner sets Billing profiles > Policies > Azure charges to Yes. On an EA, an Enterprise Administrator turns on “Account owners can view charges” (and the department equivalent). Then assign Cost Management Reader at subscription or resource group scope (Microsoft Learn). CSP customers need their partner to enable the cost visibility policy.

Why can’t I see my costs in Azure Cost Management?

Check four things. A new subscription can take up to 48 hours before all features work; classic CSP subscriptions and offers such as Azure for Students and Microsoft Azure Sponsorship aren’t supported; summarized data covers only the last 13 months; and costs from before an offer change disappear (Microsoft Learn, Cost Management data). On an EA, the view-charges setting must also be on.

Does Azure Cost Management include Microsoft 365 charges?

Partly, and only for specific offers. Microsoft says Cost Management “includes costs associated with New Commerce products like Microsoft 365 and Dynamics 365 that are invoiced along with Azure” (Microsoft Learn). Support costs are excluded, costs are estimates until invoiced and ignore credits, and MOSA (web direct) accounts exclude Marketplace and reservation purchases, showing only usage.

Can I connect Azure Cost Management to Power BI?

Yes, if you have a direct MCA or an EA. The Microsoft Cost Management connector for Power BI Desktop needs Enterprise Administrator (read-only) on an EA, or Contributor on an MCA billing account or profile, and handles up to an estimated USD 5 million of raw cost details (Microsoft Learn). Other agreements, including CSP, should load scheduled exports into Power BI instead.

What is the difference between Azure Cost Management and Azure Advisor?

Microsoft Cost Management reports and controls spend: cost analysis, budgets, alerts, exports and allocation. Azure Advisor recommends changes, such as shutting down a VM whose P95 CPU stays under 3% for 7 days (Microsoft Learn), and Microsoft’s reservation recommendations use your last 30 days of usage (Azure Reserved VM Instances FAQ). Microsoft pulls Advisor cost recommendations into Cost Management and updates them daily.

Is Azure Cost Management free?

Yes for supported offers. Microsoft says Microsoft Cost Management “is available at no additional cost as part of Azure” on paid subscriptions and free trials (Microsoft, October 2026). You pay only for what you build around it, such as the storage account that receives exports or the Logic App and Automation runbook a budget triggers.

Sources

1. Microsoft, Microsoft Cost Management product page. Accessed October 2026.
2. Microsoft Learn, What is Microsoft Cost Management. Accessed October 2026.
3. Microsoft Learn, Tutorial: Create and manage budgets. Accessed October 2026.
4. Microsoft Learn, Use cost alerts to monitor usage and spending. Accessed October 2026.
5. Microsoft Learn, Identify anomalies and unexpected changes in cost. Accessed October 2026.
6. Microsoft Learn, Group and allocate costs using tag inheritance. Accessed October 2026.
7. Microsoft Learn, Create and manage Azure cost allocation rules. Accessed October 2026.
8. Microsoft Learn, Tutorial: Create and manage Cost Management exports. Accessed October 2026.
9. Microsoft Learn, Azure Advisor: resize or shut down underutilized VMs. Accessed October 2026.
10. Microsoft Learn, Get started with Cost Management for partners. Accessed October 2026.
11. Microsoft Learn, Decide between a savings plan and a reservation. Accessed October 2026.
12. Microsoft Learn, What are Azure savings plans for compute. Accessed October 2026.
13. Microsoft Learn, Self-service exchanges and refunds for Azure Reservations. Accessed October 2026.
14. Microsoft Learn, Software costs not included with Azure Reserved VM Instances. Accessed October 2026.
15. Microsoft Learn, Use Azure Spot Virtual Machines. Accessed October 2026.
16. Microsoft Learn, Azure Hybrid Benefit for Windows Server. Accessed October 2026.
17. Microsoft Learn, Azure spending limit. Accessed October 2026.
18. Microsoft Learn, Azure Retail Prices REST API overview. Accessed October 2026.
19. Microsoft, Azure Retail Prices API query: Standard_D4s_v5, eastus. Accessed October 2026.
20. Microsoft, Azure Reserved Virtual Machine Instances pricing page. Accessed October 2026.
21. Microsoft, Azure savings plan for compute pricing page. Accessed October 2026.
22. Microsoft, Azure Hybrid Benefit offer page. Accessed October 2026.
23. Microsoft, Azure Spot Virtual Machines product page. Accessed October 2026.
24. Microsoft, Azure Dev/Test pricing page. Accessed October 2026.
25. Microsoft, Windows Virtual Machines pricing page. Accessed October 2026.
26. Microsoft Learn, Dsv5 sizes series. Accessed October 2026.
27. Microsoft Learn, Manage costs with budgets (budget scenario). Accessed October 2026.
28. Microsoft Learn, Assign access to Cost Management data. Accessed October 2026.
29. Microsoft Learn, Understand Cost Management data. Accessed October 2026.
30. Microsoft Learn, Create visuals with the Cost Management connector in Power BI Desktop. Accessed October 2026.
31. Microsoft Learn, Migrate from Run As accounts to managed identities. Accessed October 2026.
32. Microsoft Learn, Stop-AzVM (Az.Compute) reference. Accessed October 2026.
33. Microsoft Learn, States and billing status of Azure Virtual Machines. Accessed October 2026.
34. Microsoft Partner Center, Partner earned credit overview. Accessed October 2026.
35. Microsoft Partner Center, How partner earned credit is calculated. Accessed October 2026.
36. Microsoft, Azure Retail Prices API (6 VM sizes, eastus and westeurope). Accessed October 2026.
37. Microsoft Learn, Use existing runbooks and modules (Runbook gallery). Accessed October 2026.
38. Microsoft Azure Automation on GitHub, Stop Azure V2 VMs runbook README. Accessed October 2026.