Azure Reservations: the discount, the flexibility, the trap.
Three-year Azure reservations cut compute 40–72% below pay-as-you-go — the single largest lever in an Azure estate. But the deepest discount is also the tightest lock-in. This note sets out how reservations, Savings Plans and Hybrid Benefit actually price out, where the utilisation risk sits, and how to structure commitments so the saving survives contact with a changing workload.
Reservations are worth it only for compute you are confident will run above 60% utilisation for the term. For stable production, a 3-year Standard reservation (55–72% off, up to ~80% stacked with Azure Hybrid Benefit) is unmatched. For anything uncertain, an Azure Savings Plan trades roughly 5–10 points of discount for freedom across VM series, region and service. Getting the mix wrong — over-committing Standard RIs — is the most expensive Azure cost-management mistake we see, and it is entirely avoidable.
01 Key findings
The published discount is the floor, not the ceiling. 1-year reservations save 36–40% and 3-year reservations 55–72% versus pay-as-you-go. Inside an Enterprise Agreement, buyers with representation consistently capture a further 8–22% through MACC-bundled terms.
60% utilisation is the break-even line. Reservations only pay below list for workloads running above ~60% utilisation for the committed term. Below that, Savings Plans or pay-as-you-go win outright.
The 3-year decision is a risk decision. The extra 15–32 points over the 1-year rate is only earned if the workload stays put. Our break-even lands at roughly 18–24 months.
Hybrid Benefit is the multiplier most estates leave on the table. Stacking Azure Hybrid Benefit on a reserved Windows VM reaches 75–82% off — yet 20–40% of eligible VMs never have it enabled.
Scope and management, not the purchase, decide the outcome. Subscription-scoped reservations and the absence of a quarterly review let portfolios drift to 40–60% underutilisation, erasing the saving that justified the commitment.
02 Discount by term & service
Reservation discounts vary by VM series, region and term. The figures below are representative published savings against pay-as-you-go, with the additional band enterprise buyers negotiate inside an EA renewal. PaaS reservations follow the same logic across a widening service range.
| Service / VM series | 1-year reservation | 3-year reservation | Enterprise negotiated |
|---|---|---|---|
| D-series (general purpose) | ~38% | ~58% | up to 63% |
| E-series (memory optimised) | ~36% | ~55% | up to 61% |
| F-series (compute optimised) | ~37% | ~57% | up to 62% |
| M-series (large memory) | ~33% | ~51% | up to 58% |
| NC / ND-series (GPU) | ~36% | ~54% | up to 60% |
| SQL DB / Managed Instance | 27–59% by tier | +3–8% via MACC | |
| Cosmos DB | 30–65% by throughput | +3–8% via MACC | |
| App Service plans | 15–35% | +3–8% via MACC | |
03 Discount depth
How the instruments stack against a pay-as-you-go baseline for a representative Windows general-purpose VM. Each step trades flexibility for depth — the deepest bar is also the most locked-in.
The bars show list-level depth. Inside an EA, a bundled MACC commitment adds a further 3–8 points to reservation discounts on the VM series you flag as high-priority — and zone-flexible reservation rights that let the saving follow workloads across a geography rather than expiring when they move.
04 Reservations vs Savings Plans
Azure compute commitments come in three forms. The right portfolio uses all three: Standard reservations for stable load, Convertible for workloads in transition, and Savings Plans for everything variable.
| Attribute | Standard reservation | Convertible reservation | Azure Savings Plan |
|---|---|---|---|
| Discount depth | Deepest (55–72% at 3yr) | 5–8% below Standard | 10–65%, below RI rates |
| Flexibility | Exchange, no refund beyond cap | Exchange for equal/greater value | Across VMs, AKS, App Service |
| Refund / cancellation | $50,000 annual cap | Exchange-based | No series lock; hourly commit |
| Best-fit workload | Stable, predictable, always-on | Uncertain future or series shift | Dev/test, bursty, containerised |
Standard reservations also support instance size flexibility: a single D4s v3 reservation can cover two D2s v3 instances, or partially apply to a D8s v3 with the remainder used elsewhere. Estates that leave it disabled forfeit real optimisation value the moment their workload mix shifts. For the full head-to-head, see Azure Reservations vs Savings Plans.
05 The utilisation trap
The discount is advertised; the risk is not. A 3-year Standard reservation is a fixed cost whether or not the capacity is used. Every point of unused reservation is money already spent against nothing.
Over-committing to specific series without instance flexibility orphans the reservation the moment the architecture changes. Subscription-scoped reservations cannot be shared across a multi-subscription estate, stranding capacity in one place while other subscriptions pay full price. And buying without a management process lets portfolios drift to 40–60% underutilisation within a year. Microsoft's own recommendation tool is biased toward reserving at current usage — an independent view that models planned change typically finds 15–25% fewer reservations are warranted.
Guard against it with a quarterly review tracking three numbers: reservation utilisation (target above 80%), coverage of eligible compute (target 60–80%), and committed cost versus on-demand per workload. Read Microsoft's dashboard sceptically — it counts any hour where reserved capacity was consumed, regardless of whether it was the optimal allocation, so effective utilisation is usually lower than reported.
06 Purchase framework
Four questions decide the commitment, in order. Answer them before opening the Azure portal, not after.
Baseline stable compute
Isolate the always-on workloads running above ~60% utilisation for the term you are considering. Everything below that line belongs on a Savings Plan or pay-as-you-go, not a reservation.
Choose the term
Weigh the extra 15–32 points a 3-year reservation adds against the risk of change. If you cannot commit to the workload staying put for 18–24 months, take the 1-year rate.
Set scope & flexibility
Default reservations to shared (billing-account) scope and enable instance size flexibility, so the commitment follows the estate rather than stranding in one subscription or series.
Negotiate inside the EA
Time reservation terms to your EA renewal: 3–8% beyond published rates, zone flexibility, expanded exchange rights, and RI spend that counts toward the MACC target.
07 Scope & Hybrid Benefit
Two configuration choices move more money than the reservation term itself. Scope determines whether a reservation can be applied across your estate: reservations set to a single subscription or resource group cannot cover consumption elsewhere, so shared scope is the safer default for multi-subscription organisations.
Azure Hybrid Benefit is the multiplier. Applying existing Windows Server and SQL Server licences to a reserved VM lifts the combined discount to 75–82% against pay-as-you-go — but it is never automatic. It must be enabled per VM, and 20–40% of eligible VMs in mixed estates run without it. See the Azure Hybrid Benefit guide for the eligibility rules, and the Complete Microsoft EA Guide for how reservations sit inside the wider commitment.
Microsoft's Azure account executives hold discount authority they apply selectively. Buyers who bring a clear roadmap — planned migration, growth trajectory, commitment timeline — consistently earn better reservation terms than those who accept published pricing. The published rate is the floor of that authority, not the ceiling.
08 Our recommendation
Above-60% always-on compute you can vouch for over 18–24 months. Take the deepest term, enable instance flexibility, set shared scope, and stack Hybrid Benefit on every eligible Windows VM.
Uncertain series or architecture in flux. Trade 5–8 points of discount for exchange rights, or stay on the 1-year term until the workload settles.
Dev/test, bursty and AKS/App Service load. Commit hourly spend for 10–65% off without series lock, and keep reservations for the stable core only.
Structure the commitment before you buy
Our Cloud & FinOps practice baselines utilisation, models the term, and negotiates reservation and Savings Plan terms inside your EA renewal.
The Licensing Edge
Weekly cloud and licensing intelligence for enterprise IT leaders. 3,000+ subscribers.