Estimate before deployment; analyze after deployment
The clearest AZ-900 distinction is timing and evidence. A planned architecture has configuration assumptions but no actual usage history. A running environment produces measured consumption, charges and trends.
Plan
Use the Azure Pricing Calculator to model services, regions, sizes, quantities and expected usage before committing to an architecture.
Observe
Use Cost Analysis to inspect actual and forecast cost across an available billing or resource-management scope.
Control
Use budgets, alerts, exports, allocation metadata and optimization practices to make spending visible and actionable.
AZ-900 decision rule
“What might this design cost?” points to the Pricing Calculator. “What did we spend, where is it trending, and who should be alerted?” points to Cost Management.
Compare the tools by question answered
Trace the factors that can change Azure cost
Azure cost is not determined by a product name alone. A useful estimate traces the configuration and consumption units that the selected service meters.
- Resource type and service tier: compute size, storage performance, database tier and feature selection can change the rate.
- Consumption: runtime, requests, transactions, capacity, operations and retained data affect usage-based charges.
- Region: availability and prices can differ between Azure regions.
- Network traffic: inbound and outbound data-transfer patterns, routing and destination can affect cost.
- Commitment and licensing choices: eligible reservations, savings mechanisms, hybrid benefits and agreements can change effective cost.
- Operations: idle resources, oversized compute, unnecessary retention and abandoned environments create avoidable spending.
- Support, marketplace products and taxes: these may appear outside a simple service estimate depending on the account and purchase.
Always inspect the current pricing page and calculator assumptions for the exact service. A static exam-preparation page cannot provide a reliable live quotation.
A budget alerts you; it does not automatically stop resources
A Cost Management budget compares accumulated or forecast cost with configured thresholds. Notifications make owners aware of risk; action groups can support an automation workflow in eligible configurations. The budget itself is not a hard technical quota and does not automatically deallocate VMs, delete resources or prevent every new charge.
Tags can add metadata such as application, environment, owner or cost center. They help group and filter supported cost data when applied consistently, but they neither change unit prices nor replace subscription and resource-group design. Not every charge inherits or exposes tags in the same way, so cost-allocation design must be tested against actual billing data.
Safe cost-control loop
Estimate → deploy with ownership metadata → measure actual cost → compare with forecast → alert responsible owners → investigate drivers → optimize without breaking reliability, security or performance.
Worked scenario: estimating and governing a training platform
A team plans a web application, database, storage and outbound content delivery. Finance needs a forecast before approval and monthly accountability after launch.
- Model the planned services, region, sizes, quantities, hours and data transfer in the Azure Pricing Calculator.
- Document every estimate assumption, including traffic growth and nonproduction runtime. Present a range when usage is uncertain.
- Organize resources at appropriate scopes and apply consistent owner, environment and cost-center tags where supported.
- After deployment, use Cost Analysis to compare actual and forecast cost by service, resource group, subscription or supported tag.
- Create budgets and threshold alerts for responsible owners. Treat them as early-warning controls, not shutdown switches.
- Review Advisor recommendations, idle resources, sizing, schedules, retention and commitment options against technical requirements.
- Update the estimate with actual usage so future planning becomes more accurate.
Common AZ-900 mistakes
- Using Cost Analysis to price an architecture that has not been deployed.
- Treating a Pricing Calculator estimate as an invoice guarantee.
- Assuming a budget automatically stops services at the threshold.
- Assuming tags change resource prices or enforce configuration.
- Ignoring region, data transfer, service tier and resource lifetime.
- Accepting every optimization recommendation without checking workload risk.
- Comparing the estimate and bill without comparing their underlying assumptions.
- Publishing a fixed “Azure price” without a date, currency, configuration and official source.
AZ-900 practice checks with explanations
An architect must estimate a proposed VM, database and storage design before deployment. Which tool?
Best answer: Azure Pricing Calculator. It models a planned configuration; Cost Analysis requires cost data from actual usage.
A manager wants to identify which service generated last month’s increase. Which capability?
Best answer: Cost Analysis in Microsoft Cost Management. It supports filtering and grouping available cost data to investigate drivers.
Finance wants an email when forecast spending reaches 80% of a monthly target. Which control?
Best answer: A Cost Management budget with an alert threshold. The alert informs stakeholders but does not itself stop resources.
Teams want cost reports grouped by application owner. What should they plan?
Best answer: A consistent tagging and scope strategy, verified against supported cost data. Tags improve categorization but do not lower the unit price.
Frequently asked questions
What is the Azure Pricing Calculator used for?
The Azure Pricing Calculator models planned Azure service configurations and produces an estimate before deployment. The result depends on the services, region, quantities, usage assumptions, pricing options and support choices entered.
What does Microsoft Cost Management do?
Microsoft Cost Management helps organizations analyze billed and forecast costs, group and filter usage, create budgets and alerts, export cost data and identify optimization opportunities within supported billing scopes.
Does an Azure budget automatically stop resources?
No. A budget tracks cost or usage against thresholds and can send alerts or trigger an action-group workflow where supported. It does not automatically shut down Azure resources merely because the threshold is reached.
Do Azure tags reduce the price of resources?
No. Tags add business metadata that can help categorize and analyze supported cost data, but a tag does not change a service's unit price or technical configuration by itself.
Why can an Azure bill differ from a Pricing Calculator estimate?
An estimate uses assumptions. Actual cost can differ when consumption, region, data transfer, service tier, discounts, reservations, licensing, taxes, support or resource lifetime differs from the model.
Official Microsoft references
- Current AZ-900 study guide
- Describe Cost Management in Azure
- Estimate costs with the Azure Pricing Calculator
- Start using Cost Analysis
- Cost Management best practices
Prices and features change. Use official Microsoft pricing and billing data for purchasing decisions. ITCertPath provides original learning scenarios and does not reproduce confidential Microsoft exam questions.