Azure organises resources in a hierarchy: management groups at the top, then subscriptions, then resource groups, then resources. Cost is shaped at every level. Subscriptions are the natural boundary for allocation and access, management groups let you apply budgets, policy, and reporting across a whole branch at once, and the scope you give a reservation decides whether its benefit floats to where usage is or sits stranded. The buyer takeaway is that the hierarchy is a financial design, not just a technical one: a structure that mirrors how you want to allocate and govern cost makes chargeback, shared commitments, and guardrails work automatically.
Here is what each level does for cost, how to decide on subscription boundaries, and how scope drives reservation utilization.
What does each level of the hierarchy do for cost?
Resource groups gather related resources and carry tags, so they are the finest grain for allocation within a workload. Subscriptions are the billing and access boundary: each one produces its own cost detail, holds its own budgets, and is the unit most organisations use for chargeback to a team or product. Management groups sit above subscriptions and let you apply Azure Policy, budgets, and cost reporting to every subscription beneath them in one place, which is how you roll cost up by division without manually summing subscriptions. None of these levels adds a charge of its own; their value is that they decide how cost data aggregates and how widely controls and commitments reach.
One subscription or many?
| Approach | What it gives you | The cost trade |
|---|---|---|
| Few broad subscriptions | Simple management, easy reservation sharing | Coarse allocation; shared costs harder to split cleanly |
| Subscription per business unit | Clean chargeback and access boundaries | More structure to maintain; needs shared reservation scope |
| Subscription per environment | Clear separation of production and non production spend | Risk of reservations stranded if scoped too narrowly |
| Many fine grained subscriptions | Maximum isolation | Reservation and management overhead can outweigh the benefit |
The right answer is enough subscriptions to draw clean allocation and access lines, arranged under a management group tree that mirrors the business, with reservations scoped broadly so benefit can float. The split should follow how you want to report and govern cost, not the current shape of the org chart.
How does structure drive reservation utilization?
An Azure reservation can be scoped to a single subscription, to a resource group, to a management group, or shared across all eligible subscriptions in the billing account. Shared scope is the lever that matters for cost, because unused benefit in one subscription automatically applies to matching usage in another, which keeps utilization high even as workloads move. A reservation pinned to one subscription only discounts usage there, so if that workload shrinks the benefit goes unused while another subscription pays on demand for the same instance type. The same logic applies to the Azure savings plan, whose benefit also follows the chosen scope. Designing the hierarchy so reservations can share broadly is one of the simplest ways to lift effective coverage without buying more commitment.
A worked example
A European SaaS company had grown to dozens of subscriptions created ad hoc by teams, with reservations bought per subscription. Utilization on those reservations sat in the seventies because benefit could not move to where usage was, and finance could not roll cost up by product without a manual spreadsheet each month. Reorganising the subscriptions under a management group tree aligned to product lines, moving reservations to shared scope, and applying budgets at the management group level lifted reservation utilization into the high nineties and gave finance clean per product reporting with no manual stitching. The reservation utilization gain alone recovered a meaningful share of the commitment that had been going to waste. Figures are verified against billing data and anonymised.
Frequently asked questions
How do management groups affect Azure cost?
Should you use one subscription or many?
How does subscription structure affect reservations?
Design the hierarchy for the bill you want
We help organisations design the Azure hierarchy so allocation, budgets, and shared commitments work without manual effort, as an independent advisory that takes zero provider commissions and answers only to you. Our guarantee: we reduce your cloud spend or we reimburse our service fee, on a Fixed Fee or a no risk Gainshare basis. Download the cloud cost optimization playbook, read the deeper Azure cost optimization guide, and pair this with multi subscription cost reporting. For monthly buyer side analysis, subscribe to The Cloud Spend Navigator.
Put a defensible number on your cloud spend.
No provider in the room, no published price list. Tell us your footprint and we will scope the savings against your billing data — we reduce your cloud spend or we reimburse our service fee.
The Cloud Spend Navigator: what changed in cloud pricing, commitments, and FinOps — no vendor spin.