Azure Reservations buy a specific instance family (D-series, E-series, etc.) in a specific region for one or three years. The 3-year discount runs 60 to 72 percent against pay-as-you-go. Azure Savings Plans for Compute buy a dollar-per-hour commitment that applies across instance families, regions, and OS, with a 3-year discount of 28 to 65 percent depending on instance type. The decision is not discount magnitude. It is workload predictability. Steady-state workloads in known SKUs take Reservations. Variable workloads with unknown future SKU mix take Savings Plans.
This page is the 2026 reference for the two Azure commitment vehicles. List discounts per instance family and term, the exchange and refund mechanics, the per-workload decision matrix, the interaction with Hybrid Benefit, and the typical commitment-mix mistakes. Built from Microsoft Azure pricing documentation (May 2026), the Azure cost management billing constructs, and advisor-led Azure commitment reviews during 2024 to 2026.
2026 commitment pricing snapshot
Both Reservations and Savings Plans are 1-year or 3-year prepay or monthly bill commitments. They apply against compute usage. They do not apply against storage, networking, software-included costs, or PaaS resource consumption. Reservations also exist for SQL Database, Cosmos DB, Synapse, App Service, Redis, and a growing list of PaaS services with their own per-service discount tables.
| Commitment | 1-year discount | 3-year discount | Coverage scope |
|---|---|---|---|
| Reserved VM Instance | 40 to 48 percent | 60 to 72 percent | Specific instance family, region, OS |
| Reserved VM Instance (Standard_D-series) | ~36 percent | ~62 percent | D2-D96 v5, fixed region |
| Reserved VM Instance (Standard_E-series memory) | ~41 percent | ~64 percent | E2-E96 v5, fixed region |
| Reserved VM Instance (Standard_F-series compute) | ~38 percent | ~58 percent | F2-F72 v2, fixed region |
| Reserved VM Instance (Standard_M memory-optimised) | ~45 percent | ~68 percent | M-series, fixed region |
| Savings Plan for Compute | ~11 percent | 28 to 65 percent | Across families, regions, OS |
| Reserved SQL DB vCore | ~22 percent | ~33 percent | Specific vCore commitment |
| Reserved Cosmos DB throughput | ~20 percent | ~65 percent | Specific RU/sec commitment |
| Reserved App Service Premium v3 | ~40 percent | ~55 percent | Specific tier and region |
The 3-year Reserved Instance discount on a Standard_D8s_v5 in East US runs at approximately 62 percent against pay-as-you-go. The 3-year Savings Plan discount on the same instance runs at approximately 34 percent. The Reservation wins by 28 percentage points when the workload runs that exact SKU in that exact region for the full three years. If the workload moves to a different family during the term, the Reservation utilisation drops and the cost of the unused commitment cancels the discount advantage.
How Reservations work
Azure Reservations are a fixed-quantity prepay or monthly bill commitment for a specific instance configuration. The scope can be a subscription, a management group, or shared across the entire enrollment (the recommended default for enterprise estates). When a running VM matches the reservation profile, the reservation discount applies automatically with no required configuration on the VM.
Reservation matching is exact on instance series and size flexibility group. A Standard_D8s_v5 reservation matches a running Standard_D8s_v5 perfectly, partially matches a Standard_D16s_v5 (consumes 2 reservation units), and matches a Standard_D4s_v5 (consumes 0.5 reservation units). The size flexibility table applies only within the same series and within the same VM generation.
Reservations can be exchanged for other Reservations of equal or greater value during the term, with no exchange fee. Refunds are capped at $50,000 per 12-month period per enrollment. The 2023 policy change ended free unlimited refunds. Cancellations beyond the cap require Microsoft approval and may incur fees.
Reservation utilisation reporting shows the percentage of reservation hours actually consumed by matching VMs. Best-in-class enterprise estates run at 95 to 100 percent utilisation. Below 85 percent utilisation, the reservation cost is no longer beating pay-as-you-go and the commitment should be exchanged or refunded.
How Savings Plans work
Azure Savings Plans commit to a fixed hourly dollar spend on compute. The commitment applies against any matching compute usage anywhere in the enrollment, with no constraint on instance family, region, OS, or VM size. The discount per compute hour runs at a lower percentage than the equivalent Reservation, but the flexibility eliminates utilisation risk.
Savings Plans cover VMs (most series), Azure Container Instances, Container Apps, App Service Premium v3 and Isolated v2, Premium v3 dedicated hosts, Azure Functions Premium, and Azure Dedicated Host. They do not cover Spot VMs, Reserved Instances themselves, software-included VM pricing (Windows licensing, RHEL), or PaaS services that have their own Reservations (SQL, Cosmos).
The commitment is in dollars per hour, billed continuously. A $10 per hour 3-year Savings Plan commits to $87,600 per year and $262,800 over the three-year term. Microsoft applies the committed dollar amount against eligible compute consumption at the Savings Plan rate, then bills any compute consumption above the commitment at pay-as-you-go.
Savings Plans cannot be exchanged or cancelled. The hourly commitment runs for the full term regardless of consumption. Underutilisation is paid to Microsoft as a sunk cost.
The non-cancellation rule: Savings Plans have no refund, no exchange, and no cancellation mechanism. The full commitment is owed for the full term. This is materially different from Reservations and is the most consequential commercial difference between the two vehicles. Size the Savings Plan commitment conservatively against the 95th-percentile compute floor, never against the average.
The per-workload decision matrix
The right commitment vehicle depends on three workload properties: SKU stability, region stability, and term certainty. The decision table below matches workload pattern to vehicle.
| Workload pattern | Recommended vehicle | Why |
|---|---|---|
| Production VMs in known SKU and region, stable for 3 years | 3-year Reserved Instance | Highest discount, low utilisation risk |
| Production VMs in known SKU and region, planned migration in 12-18 months | 1-year Reserved Instance | Captures most of the discount with refund flexibility at year-end |
| Production workload with stable spend but uncertain SKU mix | 3-year Savings Plan for Compute | Lower discount, but flexibility prevents stranded reservation cost |
| Dev/test environments running 8 hours per day | Auto-shutdown + pay-as-you-go | Reservations and Savings Plans pay for unused hours; auto-shutdown is cheaper |
| Burst workloads with high variability | Spot VMs or pay-as-you-go | No commitment vehicle is cheaper than not committing for true variable workloads |
| SQL Database, Cosmos DB, Synapse | Service-specific Reservation | Compute Savings Plan does not cover PaaS services |
| Mixed estate, predictable floor + variable peak | Reservations for the floor, Savings Plan for the rest | Captures the best discount on the floor, flexibility on top |
The most common mistake is over-committing to Reservations and ending up with utilisation in the 70 to 85 percent range, where the effective discount is below what a Savings Plan would have delivered. The second-most common is under-committing to Reservations and running too much production at pay-as-you-go, paying full list price on stable workloads.
Interaction with Azure Hybrid Benefit
Azure Hybrid Benefit (AHB) is a separate cost optimisation that converts on-premise Windows Server or SQL Server licences with active Software Assurance into Azure compute discounts. AHB stacks with both Reservations and Savings Plans.
A Windows VM running under AHB pays the Linux compute rate plus a small Hybrid Benefit adjustment, removing the Windows licence component (approximately $0.092 per vCPU per hour for Windows Server). A 3-year Reserved Instance on a Standard_D8s_v5 Windows VM in East US lists at approximately $1,180 per month. Adding AHB reduces this to approximately $580 per month. That is a further 51 percent saving on top of the reservation discount. AHB is the single largest cost optimisation available to Windows-heavy Azure estates.
AHB requires Software Assurance entitlements for the underlying Windows Server cores. The audit risk is real: claiming AHB without sufficient SA entitlement triggers a compliance event during Microsoft Software Asset Management engagements. See our Azure Hybrid Benefit guide for the entitlement and audit rules.
Building the commitment portfolio
The optimised commitment portfolio for a $10M per year Azure compute estate typically looks like this.
| Spend layer | Vehicle | Typical allocation | Effective discount |
|---|---|---|---|
| Stable production floor (predictable SKU and region) | 3-year Reservations | 50 to 60 percent of compute spend | 60 to 72 percent vs pay-as-you-go |
| Mixed production with SKU drift expected | 3-year Savings Plan | 20 to 25 percent | 30 to 50 percent vs pay-as-you-go |
| Year-over-year planning buffer | 1-year Reservations or Savings Plans | 10 to 15 percent | 20 to 48 percent vs pay-as-you-go |
| Variable dev/test, burst, spot-eligible | Pay-as-you-go or Spot VMs | 5 to 15 percent | 0 to 70 percent off via Spot |
The blended effective discount across the portfolio typically lands at 40 to 55 percent against full pay-as-you-go pricing, with the upper end achieved when AHB is layered on Windows workloads.
Commercial levers
Reservations and Savings Plans are list-priced. The discount table is fixed by Microsoft and is not separately negotiable. The negotiation levers around Azure commitments operate on the surrounding agreement structure.
First, the Microsoft Azure Consumption Commitment (MACC). Reservations and Savings Plans consumption count toward MACC commitment burn-down, allowing customers to satisfy a multi-year Azure commitment partially through Reservations. The MACC tier discount stacks on top of the Reservation discount.
Second, the Enterprise Agreement Microsoft Customer Agreement-Enterprise (MCA-E) versus standard MCA. EA and MCA-E customers receive level-based Azure pricing that applies to the underlying pay-as-you-go rate before Reservation discount, compounding the saving. Level D pricing is typically 12 to 18 percent below Level A.
Third, exchange and refund rights. The standard Reservation exchange and $50,000 refund cap can be improved through negotiation for large customers, with bespoke caps written into the MACC or EA amendment. Customers planning aggressive cloud workload migration during the term benefit materially from negotiating exchange flexibility upfront.
For the broader Azure commercial framework see Azure MACC vs CTP, Azure MACC negotiation, Azure Hybrid Benefit, Microsoft EA Complete Guide, the Microsoft vendor hub, and our cloud contract negotiation service.