The working rule is short: reservations pay the deepest discount on workloads you can predict to the instance, savings plans pay a shallower discount on spend you can only predict in aggregate — and the exit doors are radically asymmetric, because reservations can be exchanged or refunded within limits while a savings plan, once bought, cannot be cancelled, changed or exchanged at all. In 2026 the question has a deadline attached: from 1 July, Microsoft stops selling and renewing reserved instances for a long list of older VM series, forcing every estate still running them to choose between a final renewal, newer hardware, or the savings-plan route.
Published 9 October 2025 · Last reviewed 23 October 2025
An Azure reservation is a one- or three-year commitment to a specific resource shape: a VM series in a region, a database tier, a storage class. Because Microsoft knows exactly what capacity you are promising to consume, the published discount ceiling is the deepest available — up to roughly 72% off pay-as-you-go for virtual machines on a three-year term. Instance size flexibility lets the discount float across sizes within a series group, but the commitment is anchored to that series and region.
An Azure savings plan for compute commits to something different: a fixed hourly spend, for one or three years, across eligible compute services. The plan applies itself automatically, hour by hour, to whatever eligible usage yields the largest saving — across VM families, regions and operating systems, and across services such as App Service, Functions Premium, Container Apps, Container Instances and Dedicated Hosts. The ceiling is lower — up to roughly 65% on a three-year term — because Microsoft is underwriting your flexibility.
One scope fact decides part of the question before any modelling starts: savings plans cover compute only. Databases, storage, analytics and the rest of the reservation catalogue can only be committed through reservations. The choice on this page is a compute-layer choice; most committed estates carry reservations on data services regardless.
This guide is general information about Microsoft commercial offerings, not financial or licensing advice for your situation. Commitment mechanics moved in 2026 and will move again; your agreement governs. It names no firms; the firm directory lists Microsoft-capable advisors with balanced pros and cons, listed, not ranked.
| MECHANIC | RESERVATION | SAVINGS PLAN FOR COMPUTE |
|---|---|---|
| What you commit to | A specific resource shape (VM series + region, database tier, storage class) for 1 or 3 years | A fixed hourly spend on eligible compute for 1 or 3 years |
| Discount depth | Deepest published ceiling (up to ~72% on 3-year VM terms) | Lower ceiling (up to ~65% on 3-year terms) — the price of flexibility |
| Scope | Broad catalogue: compute plus databases, storage, analytics and more | Compute services only, but across families, regions and operating systems |
| How the discount lands | On matching usage in the committed series/region; size-flexible within the group | Applied automatically each hour to whatever eligible usage saves most |
| Utilization risk | Unused reserved hours are simply lost; mitigated by exchanges while they last | Hourly commitment is billed whether or not usage reaches it — under-use is pure waste |
| Exchange / modification | Compute exchanges available “until further notice” with a promised 6-month warning before removal; instance size flexibility persists either way | None. Cannot be modified or exchanged after purchase |
| Cancellation / refund | Possible within a capped annual refund allowance | None. No cancellation, no refund, runs to term |
| Conversion path | One-way self-service trade-in into a savings plan, no time limit | No path back to reservations |
| 2026 availability event | From 1 July 2026, no new purchases or renewals for legacy VM series RIs (see below) | Positioned by Microsoft as the successor instrument for those workloads |
Read the table bottom-up and the pattern is clear: every recent structural change — the trade-in, the legacy retirement, the flexibility positioning — moves customers toward the savings plan, the instrument with no exit door. That is not sinister; it is a vendor simplifying its portfolio. But it means the flexibility you are buying operationally is paid for with flexibility surrendered contractually, and that trade deserves explicit modelling rather than default acceptance.
From 1 July 2026, Microsoft stops selling and renewing one-year reserved instances for the Av2, Amv2, Bv1, D, Ds, Dv2, Dsv2, F, Fs, Fsv2, G, Gs, Ls and Lsv2 series — and stops selling and renewing reserved instances of any term for Dv3, Dsv3, Ev3 and Esv3. Existing reservations run to the end of their term; nothing terminates on the date itself, and workloads are untouched — a reservation is a billing construct, not infrastructure.
The forcing function is at renewal. An estate still running v2 and v3 series — which describes a large share of mature Azure tenants — faces a three-way fork: place a final renewal before the cutoff (honored for its full term, even three years for the one-year-only list), modernize the workload onto newer series that remain reservable, or trade into a savings plan and accept the shallower ceiling for family-agnostic coverage. Doing nothing is the fourth option, and it has a price: when coverage lapses, the workload reverts to on-demand rates silently.
The honest framing is that this retirement converts a routine renewal into a portfolio decision with a deadline — and deadline decisions made inside a vendor's own renewal motion tend to default to the vendor's preferred instrument. Modelling the fork before the renewal conversation, with someone whose fee does not depend on the answer, is the entire point of independent cloud cost-optimization work.
Reservations are a strong fit for workloads that are stable to the instance: the database VM that has run the same series in the same region for three years, steady-state production tiers, capacity you would buy hardware for in an on-premises world. Predictability is literally what the extra discount pays for — and non-compute commitments (databases, storage) have no savings-plan alternative anyway.
Savings plans are a strong fit for the changing layer: estates mid-modernization, workloads that hop families as they re-platform, multi-region deployments that rebalance, organisations that cannot forecast shape but can forecast aggregate spend. They are also now the structural answer for anything stranded on retiring VM series.
Mature FinOps practice rarely picks one. The standard portfolio puts reservations under the stable core, a savings-plan layer across the variable middle, and leaves a deliberate band of on-demand at the top for genuine elasticity — sized so that commitment utilization stays near full even in a soft quarter. The discipline that matters is sizing the layers from telemetry (sustained-use floors, not peak), revisiting quarterly, and never letting either instrument be sized by enthusiasm during a renewal or a contract-vehicle migration, when commitment appetite is at its most distorted. Note too that under MCA-E there is no default price protection on the underlying rates — commitment instruments are the price protection now, which raises the stakes on getting their shape right.
Sizing the savings plan to average spend. The hourly commitment bills every hour, including nights, weekends and the quiet quarter after a divestiture. Plans sized to daytime averages run permanently under water off-peak. Size to the sustained floor, not the mean.
Treating the trade-in as reversible. The reservation-to-savings-plan door locks behind you: no cancellation, no exchange, no path back. Trading in a deep three-year reservation with two years left surrenders real discount for flexibility you may not need. Model the residual term first.
Assuming exchanges are forever. Compute reservation exchanges survive “until further notice” — a policy Microsoft has already once scheduled for removal and then extended. The six-month warning is the only guarantee. Portfolios built on the assumption of perpetual free exchange carry a policy risk that should be priced in.
Letting legacy RIs lapse to on-demand. The July 2026 retirement produces no alert when coverage simply expires. Estates that do not inventory their v2/v3-series reservations now will discover the change as an unexplained cost increase later.
Stacking commitments on a MACC without modelling the downside together. Reservation and savings-plan purchases generally burn down a Microsoft Azure Consumption Commitment, which makes them attractive in the negotiation — and correlated in the downside. If usage falls, the hourly floor, the consumption commitment and the term all bind at once.
Buying commitments inside the vendor's renewal motion. Commitment sizing proposed by the seller's own account team during a renewal optimizes for the seller's metrics. The counter is independent telemetry-based modelling — and choosing who does that modelling is its own decision.
The other Microsoft metering fork →
The vehicle these commitments ride on →
The post-EA contract choice →
How to pick the firm for this work →
Firms that model commitment portfolios →
Every field guide on the site →
A reservation commits you to a specific resource configuration — a VM series in a region, a database tier, a storage class — for one or three years, and pays the deepest published discount in return. A savings plan for compute commits you to a fixed hourly spend across eligible compute services for one or three years; the discount ceiling is lower, but the commitment follows your usage across VM families, regions and operating systems automatically. Reservations buy depth on stability; savings plans buy flexibility on change.
No. Once purchased, a savings plan for compute cannot be cancelled, refunded, modified or exchanged — the commitment runs to term, used or not. Reservations remain the more reversible instrument: they can be refunded within a capped annual allowance, and compute reservation exchanges remain available until further notice, with Microsoft committing to at least six months’ warning before removing them. The reversibility asymmetry is a core part of the decision.
Yes — Azure offers a self-service trade-in of compute reservations into a savings plan, with no time limit. The trade-in is one-way: a savings plan can never be turned back into reservations, cancelled or exchanged. Treat the trade-in as a door that locks behind you, and model the residual reservation term you are surrendering before walking through it.
From July 1, 2026, Microsoft no longer sells or renews one-year reserved instances for a list of older VM series (Av2, Amv2, Bv1, D, Ds, Dv2, Dsv2, F, Fs, Fsv2, G, Gs, Ls, Lsv2), and no longer sells or renews any reserved instances — one- or three-year — for the Dv3, Dsv3, Ev3 and Esv3 series. Existing reservations are honored to the end of their term. A renewal placed before the cutoff is the final one; after expiry the workload either moves to newer series, shifts to a savings plan, or pays on-demand rates.
No — the savings plan instrument covers eligible compute services only. Reservations cover a much wider catalogue: databases, storage, analytics and other non-compute services can only be committed through reservations. Estates that commit database and storage capacity therefore carry reservations regardless of how the compute question is decided; the reservation-versus-savings-plan choice is really a compute-layer choice.
Reservation and savings plan purchases generally decrement a Microsoft Azure Consumption Commitment, which is one reason the instruments belong in the same negotiation as the enterprise agreement itself. The interaction cuts both ways: commitments help burn down a MACC, but layering a multi-year hourly spend floor on top of a contractual consumption commitment compounds the downside if usage falls. This is information, not advice; your agreement’s terms govern.
Sizing the layers, timing the July 2026 fork and negotiating the commitment terms is exactly what a Microsoft licensing advisor is for. The directory lists the firms that do this work, with balanced pros and cons, listed, not ranked.
Tell us the vendor, the service you need and where things stand, and we will route your brief to firms that genuinely cover that combination. The directory and matching are free for buyers, no vendor ever sees your brief, and we add no markup.
Our weekly dispatch on vendor audit programs, regional developments and one buyer move. Subscribe to The Licensing Radar.