Cost Management in Azure

AZ-900 AZ-900 · Describe Azure management and governance

By Abu Anns · Last updated 20 November 2026Exam version: AZ-900 (skills measured as of July 20, 2026)

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:

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:

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.

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.

Advertisement

Exam traps to watch for

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?

Report an error

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?

Report an error

Q3.A company runs identical virtual machines in two Azure regions and notices the monthly bill differs between them. What best explains this?

Report an error

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?

Report an error

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?

Report an error

Q6.An administrator tags a resource group with Environment: Production. Which statement about the resources inside the group is correct?

Report an error

Q7.Which of the following is a factor that can affect the cost of an Azure virtual machine?

Report an error

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?

Report an error