Home  ›  Blog  ›  Azure Reservations
Microsoft · Azure

Azure Reservations and Savings Plans — the commitment mix that actually works.

Azure offers three layers of discount on its compute and database services: pay-as-you-go (no commitment, list price), Reserved Instances (1-year or 3-year commitment to a specific SKU, up to 72% discount), and Compute Savings Plans (1-year or 3-year commitment to an hourly spend amount, more flexible than RIs, slightly smaller discount). Layer them right and a typical enterprise Azure estate runs 35–55% below list. Layer them wrong and the customer ends up locked into commitments larger than actual consumption with no recoverable mechanism. Here is the framework.

Updated: June 2026 Reading time: 14 min Audience: Cloud Architect, FinOps Lead, IT Procurement
Azure Reservations
Mechanics

Reserved Instances vs Savings Plans — the structural choice.

An Azure Reserved Instance (RI) is a 1-year or 3-year commitment to a specific resource configuration: VM family, region, operating system. In return, Microsoft discounts the resource by up to 72% for a 3-year commitment, paid upfront or monthly. The reservation applies automatically to any matching resource consumption.

An Azure Compute Savings Plan is a 1-year or 3-year commitment to an hourly spend amount on compute services, region-agnostic and VM-family-agnostic across the Azure compute fleet. The discount is smaller (up to 65% on 3-year), but the flexibility is significantly greater: the commitment auto-applies to whatever compute the customer happens to be running. RIs lock the customer to a specific SKU; Savings Plans lock the customer to a spend amount.

When RIs win, when Savings Plans win

RIs win where the resource configuration is stable and well-understood: production VMs running 24/7 on a known SKU, SQL Database compute layers with predictable scale, AKS node pools with locked instance families. The 7–10% additional discount over Savings Plans is worth the inflexibility because the inflexibility doesn't bind.

Savings Plans win in mixed estates with changing workloads: development environments that scale up and down, modernisation programmes that change instance families, M365 backend services that auto-scale across regions. The Savings Plan's region-and-family agnostic posture protects the commitment when the underlying deployment evolves.

Azure commitment review needed?

The RI-vs-Savings-Plan mix is where most enterprise Azure estates carry 8–15% capturable savings against the current configuration.

Contact Us →
Term and payment

1-year vs 3-year — and the upfront-vs-monthly payment question.

The 3-year commitment carries roughly a 10–15% additional discount over the 1-year commitment for the same resource. For genuinely stable workloads, 3-year always wins. For workloads with horizon uncertainty (cloud-migration target architectures, M&A integration targets, future-shifted SaaS migrations), the 1-year commitment is safer despite the smaller discount.

Upfront payment versus monthly is a smaller question. The upfront-paid RI carries roughly a 2–4% additional discount over the monthly-billed equivalent, but commits cash flow at the start of the term. For most enterprises, the cash-flow cost of upfront commitment exceeds the discount captured. Monthly billing is the default recommendation unless the customer has specific cash management reasons to prefer upfront.

Exchange and refund mechanics

RIs are exchangeable but the rules are restrictive. A reservation can be exchanged for another reservation of equal or greater value, with the same or longer term, within the same region. Reservations cannot be exchanged across families freely after exchange-policy tightening in recent releases. Reservations can also be refunded — Microsoft permits up to $50,000 in annual cancellations per tenant, charged against a 12% early-termination fee on cancelled value above an in-period threshold.

Savings Plans are non-exchangeable and non-refundable. The flexibility is built into the commitment itself rather than the post-purchase exchange mechanism.

Download the Cloud Contract Negotiation Framework.

Azure commitment-strategy templates, the RI exchange playbook, and the structural patterns for managing MACC alongside reservation portfolios.

Get the framework →
Hybrid Benefit

Azure Hybrid Benefit — the third discount layer.

Azure Hybrid Benefit (AHB) is the entitlement to apply existing on-prem Windows Server or SQL Server licences (with active Software Assurance) to Azure compute, eliminating the licence component of the VM cost. For Windows Server VMs, AHB removes roughly 40% of the VM cost. For SQL Server VMs (using SA-covered SQL licences), AHB can remove 55% of the cost. AHB stacks on top of RIs and Savings Plans, producing combined discounts of 75% or more against PAYG.

In our experience across 340+ Microsoft engagements, AHB is the single most under-claimed Azure discount. Customers who have SA on Windows Server and SQL Server licences frequently fail to apply AHB to their Azure deployments. The remediation is mechanical (an admin-centre toggle), but discovery of where to apply it requires reconciliation between the on-prem licence position and the Azure VM inventory.

Azure cost line growing faster than consumption?

The combined RI/Savings Plan/AHB optimisation typically captures 22–38% reduction against the current run rate.

Contact Us →

For Azure consumption above $1M annually, independent commitment-strategy advisory typically captures cost reduction equal to five to twelve times the advisory fee within the first commitment cycle. Our cloud contract advisory practice rebalances the reservation and Savings Plan portfolio against a rightsized baseline.

Azure reservation portfolio drifting out of step with consumption?
The rebalance between RIs, Savings Plans and AHB is the highest-leverage Azure FinOps review.

We have rebalanced Azure commitments from $500K to $40M annually.

The Compliance Brief

Weekly compliance intelligence for IT leaders.