Describe Azure management and governance
Azure Cost Management
CoreEstimate before deployment, analyze actual spending, and organize cost data.
Aligned to the AZ-900 skills measured as of July 20, 2026; product behavior verified August 23, 2026.
Why this matters
Costs are shaped by multiple technical and commercial choices. Fundamentals questions distinguish an estimate from ongoing analysis and metadata from enforcement.
Must Know
- Azure cost can vary with resource type and size, usage duration, region, data transfer, redundancy, support, licensing, and commitment choices.
- The Azure pricing calculator models estimated costs from selected services, regions, quantities, and usage assumptions before deployment.
- Microsoft Cost Management supports analysis of actual spending, budgets, alerts, exports, and cost optimization insights for supported scopes.
- A budget tracks spending against a threshold and can trigger alerts; it does not automatically stop resources or guarantee a spending cap.
- Tags are key-value metadata used to organize, report, and group costs. They are not hierarchy levels and do not automatically inherit without a separate mechanism.
Compare and Distinguish
- Pricing calculator vs Cost Management: predeployment estimate versus ongoing analysis and control visibility.
- Estimate vs invoice: modeled assumptions versus actual measured usage and commercial terms.
- Budget vs automatic stop: threshold tracking and notification versus resource shutdown.
- Tag vs resource group: cross-cutting metadata versus a management container.
Scenario examples
- An architect compares two potential regions and quantities in the pricing calculator.
- Finance analyzes current subscription spend and configures a budget alert in Cost Management.
- Resources receive department and cost-center tags for reporting across resource groups.
Exam traps
- Resource count alone does not determine cost.
- A pricing-calculator result is not a binding invoice.
- A budget alert does not by itself stop a workload.
- Tags do not automatically inherit or grant access.
Key takeaways
- Model before deployment; analyze actual spend after deployment.
- Include region, transfer, time, and commitment in cost reasoning.
- Use tags as metadata, not as a management hierarchy or enforcement control.
Ready for the quiz?
- Which tool estimates an undeployed design?
- Which capability analyzes actual spending?
- What can a tag do, and what can it not do?
Related objectives
- D3.1.S1 — Describe factors that can affect costs in Azure
- D3.1.S2 — Explore the pricing calculator
- D3.1.S3 — Describe cost management capabilities in Azure
- D3.1.S4 — Describe the purpose of tags