Cost Management in Azure
AZ-900 AZ-900 · Describe Azure management and governance
What affects costs in Azure?
Azure bills by metered usage, and the exam expects you to describe the factors that drive a bill up or down. The main ones:
- Resource type: different services cost different amounts — a large virtual machine costs more than a small one, and a managed database costs more than raw storage.
- Size and tier: within a service, bigger and faster costs more — a VM with 32 CPUs costs more than one with 2, and a Premium storage account costs more than a Standard one.
- Region: prices vary by region, because datacenter costs differ around the world. The same VM can cost noticeably more in one region than another.
- Usage time: many resources bill by the hour or second while they run. A VM that runs 24/7 costs roughly three times one that runs only during office hours.
- Data transfer: data going into Azure (ingress) is free; data leaving Azure (egress) to the internet is charged. Moving large amounts of data out is a classic surprise bill.
- Commitments and licences: reservations, savings plans, and the Azure Hybrid Benefit reduce prices for committed or already-licensed workloads (see the pricing guide).
Two of these are exam favourites. First, location matters: choosing a region is a cost decision as well as a latency one. Second, egress costs, ingress is free: the exam tests this asymmetry directly, often with a scenario about a company moving data out of Azure and being surprised by the bill.
Estimating before you spend: the pricing calculator
The Azure pricing calculator estimates what a planned deployment will cost before you build it. You pick services, regions, tiers, and usage levels, and it produces a monthly estimate you can save, share, and export. It is the tool for the question "what will this cost?" asked before spending anything. The exam pairs it with cost predictability: a team that estimates first is practising cost predictability. Note what the calculator is not: it does not show what you have already spent (that is Cost Management), and it does not compare on-premises costs with Azure costs (that is the Total Cost of Ownership calculator, a related but separate tool).
Controlling spend: Cost Management
Once resources are running, Microsoft Cost Management is the tool for understanding and controlling actual spending. Its capabilities:
- Cost analysis: break down spending by resource, resource group, subscription, service, region, or tag — so you can see exactly where the money goes. Cost analysis answers "what are we spending on?"
- Budgets: set a spending limit for a subscription, resource group, or service over a period (monthly, quarterly, annual). Budgets do not stop spending by themselves — they are thresholds that trigger alerts.
- Alerts: notify people when spending approaches or exceeds a budget, or when spending is forecast to exceed it. Alerts can trigger automation through action groups — for example, sending an email, or running a runbook that shuts down non-essential resources.
- Recommendations: Cost Management (with Azure Advisor) suggests savings — deleting idle resources, resizing over-provisioned VMs, buying reservations for steady workloads.
- Exports: send cost data to storage or a reporting tool for finance teams and deeper analysis.
The exam's trap here is budgets: a budget alerts you, it does not enforce a hard spending cap. If a question asks how to be notified when spending reaches a threshold, the answer is budgets plus alerts. If it asks how to stop spending, the honest answer is that budgets alone do not do that — automation triggered by the alert can.
Tags: organising for cost and governance
A tag is a name-value pair attached to a resource, resource group, or subscription — for example, Department: Finance, Environment: Production, or Project: Website-Redesign. Tags have two main purposes. First, cost allocation: because Cost Management can break spending down by tag, a company can see exactly what each department, project, or environment costs. Second, organisation and governance: tags let teams find, filter, and manage resources by owner, environment, or purpose, and Azure Policy can require tags on new resources.
Three details matter for the exam. Tags are not inherited automatically: tagging a resource group does not tag the resources inside it (although a policy can be set to inherit tags). Tags are metadata only: they do not control access, enforce rules, or change how a resource behaves — they label it. And a resource can have up to 50 tags, each a name-value pair. If a scenario asks how to track which department's resources cost what, the answer is tags plus Cost Management — not separate subscriptions, not separate regions.
Worked example: controlling a runaway bill
A company's Azure bill doubles in one month. The investigation: cost analysis by resource group shows the increase is entirely in the development subscription; cost analysis by tag shows the tagged owner is a test project that was supposed to be deleted; and the breakdown by meter shows the cost is data egress from a storage account that a test script is reading repeatedly. The fixes: delete the test project, set a monthly budget with an alert at 80% for the development subscription, and require a Project tag on all new resources via Azure Policy so the next runaway cost can be traced in minutes. Estimate first (pricing calculator), watch spending (Cost Management), trace it (tags), prevent repeats (policy) — the cost-management story in one incident.
Related tool: the Total Cost of Ownership calculator
One more cost tool is worth knowing, although the objectives do not name it directly: the Total Cost of Ownership (TCO) calculator. Where the pricing calculator estimates what a planned Azure deployment will cost, the TCO calculator compares the full cost of running workloads on-premises (hardware, power, cooling, staff, datacenter space) with the cost of running the same workloads in Azure. It is the tool for the business case — "should we move at all?" — rather than for the budget of a deployment you have already decided to build. Keep the three cost tools apart: the TCO calculator compares on-premises with Azure, the pricing calculator estimates a planned Azure deployment, and Cost Management analyses what you have actually spent.
Exam traps to watch for
- Thinking a budget stops spending. Budgets trigger alerts when spending crosses a threshold; they do not cap spending by themselves.
- Confusing the pricing calculator with Cost Management. The calculator estimates costs BEFORE deploying; Cost Management analyses costs AFTER spending.
- Assuming tags are inherited. Tagging a resource group does not tag its resources; inheritance needs an Azure Policy.
- Forgetting that data leaving Azure costs money. Ingress is free, egress is charged — a common surprise in exam scenarios about large downloads.
Practice questions
Test yourself on this guide. Answers are checked instantly, with a full explanation for each question.
Q1.A company wants to be notified by email when its monthly Azure spending reaches 80% of its planned limit. What should it configure?
Explanation: Cost Management budgets define a spending threshold, and alerts notify people when spending approaches or exceeds it. Azure Policy enforces configuration rules, not spending notifications. A resource lock prevents deletion or modification of resources. There is no native hard spending cap on a subscription — budgets alert, they do not block spending.
Exam objective: AZ-900 Describe cost management in Azure: describe cost management capabilities in Azure
Q2.Before deploying a new application, a team wants to estimate what it will cost to run each month in a specific region. Which tool should it use?
Explanation: The pricing calculator estimates the cost of a planned deployment before it is built. Cost Management cost analysis reports on spending that has already happened. Azure Advisor gives recommendations (including cost ones) for existing resources. Azure Monitor collects metrics and logs for operations, not cost estimates.
Exam objective: AZ-900 Describe cost management in Azure: explore the pricing calculator
Q3.A company runs identical virtual machines in two Azure regions and notices the monthly bill differs between them. What best explains this?
Explanation: Azure prices vary by region because datacenter costs differ, so identical resources can cost different amounts in different regions. VMs are billed by size and time, not per user. A price difference does not mean one region's VMs are faster. The pricing calculator gives estimates, but the bill difference here is a real regional price difference, not an estimating error.
Exam objective: AZ-900 Describe cost management in Azure: describe factors that can affect costs in Azure
Q4.A company uploads 5 TB of data into Azure for free, then downloads 5 TB back to its offices and receives a large data-transfer charge. What explains the charge?
Explanation: Data transfer into Azure is free; data leaving Azure to the internet is charged — the asymmetry explains the bill. Uploading is not charged. The region affects resource prices, not this transfer charge. And Azure does not charge for movement in both directions — ingress is free.
Exam objective: AZ-900 Describe cost management in Azure: describe factors that can affect costs in Azure
Q5.A company wants to see how much each department spends on Azure, so it adds a Department tag (Finance, Sales, Engineering) to every resource. What does this tagging enable?
Explanation: Cost Management can break spending down by tag, so tagging by department enables per-department cost reporting. Tags do not delete resources, control access, or change prices — they are metadata for organisation and reporting.
Exam objective: AZ-900 Describe cost management in Azure: describe the purpose of tags
Q6.An administrator tags a resource group with Environment: Production. Which statement about the resources inside the group is correct?
Explanation: Tags are not inherited automatically: tagging a resource group does not tag the resources inside it (a policy can be configured to inherit tags, but it is not the default). Tagging does not move resources or change their subscription, and it does not prevent modification — tags are metadata only.
Exam objective: AZ-900 Describe cost management in Azure: describe the purpose of tags
Q7.Which of the following is a factor that can affect the cost of an Azure virtual machine?
Explanation: VM cost depends on its size (CPU, memory) and its region, among other factors. The number of Entra ID users does not affect VM pricing. The portal's appearance is irrelevant. The number of resource groups has no effect on VM cost.
Exam objective: AZ-900 Describe cost management in Azure: describe factors that can affect costs in Azure
Q8.A finance team wants a monthly report of Azure spending that it can analyse in its own reporting tool. Which Cost Management capability provides this?
Explanation: Cost Management exports send cost data out (to storage or a reporting tool) for external analysis. Budgets set spending thresholds. Alerts notify people about spending. Recommendations suggest savings — none of them produces a data feed for an external reporting tool.
Exam objective: AZ-900 Describe cost management in Azure: describe cost management capabilities in Azure