Buying Azure Reserved VM Instances well comes down to four decisions: what to commit to, at what scope, for how long, and how much. Get those right on a rightsized baseline and reservations deliver the best per-hour rate Azure offers on predictable compute. Get them wrong, by committing to an oversized or shifting fleet, and you carry a poor-fit cost for up to three years. This guide is the buyer-side checklist we run before any purchase.
This article is part of our Azure cluster. Start with the complete guide to Azure cost optimization, the pillar this piece links up to. Reservations are the considered last move in the Cut and Lock steps of our See, Cut, Lock, Run method.
Never buy a reservation against an unoptimized fleet. A reservation locks the discount to a capacity level for the whole term, so if half your VMs are oversized you are committing to that waste for one or three years. Run VM rightsizing first, establish the stable baseline, then commit to that clean number.
Decision 1: term, one year or three
A three year reservation carries a deeper discount than one year, but it is a longer bet on your architecture staying still. Choose three years for the genuinely stable core: workloads on the same VM family that have run for many months and have no migration on the roadmap. Choose one year where there is real uncertainty, a possible re-platform, a family change on the horizon, or a workload still finding its shape. The deeper discount is not worth locking in a fleet you expect to change.
Decision 2: scope, shared or single
Reservation scope controls which resources the discount applies to. A single-subscription scope confines the benefit to one subscription; a shared scope lets the discount float across all subscriptions in the billing context, applying to whichever matching VMs are running. Shared scope almost always raises utilization of the reservation because it finds matching usage wherever it is, which is what you want unless you have a specific reason to ring-fence a subscription's benefit. Management-group scope adds a middle option for large estates.
About to make a large reservation commitment?
Our Azure cost audit models your stable baseline, recommends term, scope, and quantity per family, and stress-tests the commitment against your roadmap before you sign. On the performance model, you pay only from realized savings. No savings, no fee.
Book an Azure cost audit →Decision 3: use instance size flexibility
Reservations apply with instance size flexibility within a VM family: a reservation for one size in a family can cover other sizes in the same family in proportion to their relative footprint. This matters because it lets a reservation keep applying as you resize within a family, which you will do as part of ongoing rightsizing. When you buy, think in terms of the family and the aggregate capacity you want covered, not a single rigid size, so normal resizing does not strand the benefit.
Decision 4: how much to commit
Cover the stable floor of your usage, not the average and certainly not the peak. Look at the minimum running capacity per family over the trailing months, the level that is always on, and reserve up to that floor. Usage above the floor is better left on pay-as-you-go or covered by a savings plan, because reserving the variable layer risks paying for capacity you do not always run. The reservation-versus-plan split is covered in Azure Reservations vs Azure savings plan for compute.
Exchanges, cancellations, and Hybrid Benefit
Azure has historically allowed reservations to be exchanged for a different reservation and cancelled within defined limits, which softens the commitment, but the rules have tightened over time and should be checked before you rely on them. Layer Azure Hybrid Benefit on Windows Server reservations to remove the OS licensing component on top of the reservation discount, stacking two savings on the same VM.
| Decision | Default for stability | Default for uncertainty |
|---|---|---|
| Term | 3 years | 1 year |
| Scope | Shared | Shared |
| Quantity | The always-on floor | A conservative slice of the floor |
| Family thinking | Aggregate via size flexibility | Aggregate via size flexibility |
Term, scope, exchange, and cancellation behavior above reflect Azure as of May 2026. Verify current reservation policies, instance size flexibility groups, and exchange rules in Azure documentation before purchasing, as Microsoft revises these terms.
The Azure Cost Optimization Field Guide includes the reservation sizing worksheet and the term-and-scope decision tree we use on engagements. It is the downloadable companion to this article.
The short version
Buy Azure Reserved VM Instances only on a rightsized baseline; choose three years for the stable core and one year where change is likely, use shared scope and instance size flexibility, and reserve only the always-on floor, leaving the variable layer to a savings plan. To place the purchase inside a full plan, follow how to run an Azure cost optimization assessment. When you want the commitment modeled and bought correctly, that is exactly what our Azure cost optimization service delivers.