MICROSOFT LICENSING · MODULE 7 · MICROSOFT AZURE
Azure Reservations or Savings Plans:
Which option fits which workload?
Both models can reduce Azure costs. The difference is the commitment: a reservation fits stable usage of a particular resource, while a savings plan offers more flexibility for changing compute or database usage.
The short answer
Stable workload: consider a reservation. Changing workload: consider a savings plan.
Azure offers lower rates when an organisation commits for a set period. The key question is not only the potential discount, but whether the purchased commitment will actually be used every hour.
- 01Reservations fit continuously stable resources, sizes, and regions.
- 02Savings plans fit changing compute services, VM families, or regions more easily.
- 03Unused hourly commitment is lost under both models and does not roll over.
- 04Savings plans cannot be cancelled or exchanged for reservations after purchase.
- 05Optimise and right-size resources first; purchase a pricing commitment afterwards.
Explained simply · The essential terms
Three terms for Azure pricing benefits
Reservations and savings plans reduce rates in return for a time commitment. They do not eliminate unused or oversized resources.
Azure Reservation
A commitment to a particular matching resource or configuration and region, commonly for one or three years.
Reserved VM Instance
A virtual-machine reservation. It is primarily a billing benefit and does not automatically guarantee capacity.
Savings plan
A fixed hourly spend commitment that automatically applies to eligible usage and provides more flexibility than a reservation.
A practical example: A VM is expected to run unchanged in one region for three years. A reservation may fit. If VM families, services, or regions change regularly, a savings plan may be more flexible.
Understand the logic first
Why does Microsoft offer a lower rate?
Pay-as-you-go consumption remains flexible and is billed at the standard usage rate. Reservations and savings plans reduce rates because the organisation accepts a longer financial commitment.
Flexible without a longer commitment
The resource is billed based on use. This is flexible but does not provide the rate benefit of a longer commitment.
Commitment to matching resource usage
The discount applies to usage matching the selected service, SKU, region, and benefit scope.
Commitment to hourly spending
The organisation commits to a fixed amount of eligible spend per hour. Azure automatically applies the benefit within the selected scope.
An oversized or unnecessary VM remains inefficient with a reservation or savings plan. Microsoft therefore recommends removing waste and right-sizing resources before buying commitments.
Azure Reservations
How does a reservation work?
A reservation is a billing benefit for matching Azure usage. After purchase, Azure automatically applies the discount to resources matching the selected attributes.
| Attribute | What does it mean? | What should you check? |
|---|---|---|
| Configuration | A particular service, SKU or instance family and, where applicable, region | If usage changes, the discount may no longer match. |
| Term | Commonly one or three years, depending on the offering | Purchase only against a reliable long-term baseline. |
| Payment | Up front or monthly; Microsoft states that the total price is the same | Monthly payment does not shorten the commitment. |
| Application | Automatically applied to matching running resources in the selected scope | Without matching usage, part of the reservation remains unused. |
| Unused hour | Use it or lose it: unused reservation hours expire | They cannot be carried into a later day or month. |
An Azure Reserved Virtual Machine Instance is primarily a pricing and billing model. Organisations requiring guaranteed or prioritised capacity must assess the dedicated capacity options separately.
Azure savings plans
How does a savings plan work?
A savings plan does not reserve a single VM. The organisation instead commits to a fixed hourly spend, and Azure automatically applies the discount to eligible usage.
| Attribute | What does it mean? | What should you check? |
|---|---|---|
| Commitment | A fixed amount of spend per hour | A stable minimum usage should cover this amount. |
| Flexibility | Application across participating services and regions within the scope | Not every Azure service or charge type is eligible. |
| Term | Compute savings plan: one or three years; database savings plan: currently one year | Confirm the exact product and term before purchase. |
| Application | Azure applies the benefit to eligible usage receiving the highest discount first | Usage above the hourly commitment is billed at the regular rate. |
| Unused hour | Unused hourly commitment expires | It does not roll over and is not refunded. |
Microsoft does not allow cancellation, refund, or conversion of a savings plan into a reservation. The hourly commitment should therefore be selected conservatively.
Direct comparison
Reservation or savings plan?
The most economical discount is the one that is actually used. A theoretically larger saving offers little value if the commitment does not match real consumption.
| Question | Azure Reservation | Savings plan |
|---|---|---|
| What is the commitment based on? | Matching resource or configuration and region | Fixed hourly spend |
| Which usage does it suit? | Stable, continuous, and predictable | Dynamic, changing, or spread across eligible services and regions |
| Flexibility | Lower, depending on product and instance-size flexibility | Higher within participating services and the selected scope |
| Potential savings level | Often highest when fully utilised | Often lower, but applied more broadly |
| If consumption declines | Unmatched reservation hours expire | Unused hourly commitment expires |
| Ending the commitment | Refund or exchange only within applicable limits and rules | No cancellation or refund |
Where is the benefit applied?
The scope determines which resources benefit
Reservations and savings plans can use differently sized benefit scopes. A broader scope improves the chance of matching usage but also spreads the benefit across a wider organisation.
One resource group
The benefit applies only to matching eligible resources in the selected resource group.
One Azure subscription
Matching resources within one selected subscription can receive the benefit.
Several related subscriptions
The benefit can apply to eligible resources in subscriptions belonging to both the management group and the same billing context.
Shared billing context
The benefit applies more broadly to matching eligible usage within an EA enrollment or MCA billing profile.
Define who funds the commitment, who consumes it, and how costs and savings are allocated internally. Scope can be changed later without restarting the term.
Connect licensing and FinOps
How do Hybrid Benefit and commitments work together?
Azure Hybrid Benefit, reservations, and savings plans address different cost components. They can therefore work together for eligible services.
Reduces an eligible software component
Existing Windows or SQL licences with the required entitlements can reduce the licensing component of selected Azure offerings.
Reduces matching resource-usage rates
For Reserved VM Instances, a reservation primarily covers compute; Windows, networking, and storage are not automatically included.
Reduces eligible usage up to the hourly amount
The compute savings plan excludes software, networking, and storage. The newer database savings plan has its own coverage rules.
A reservation or savings plan does not automatically grant Windows or SQL usage rights. Licensing entitlement and cloud-price optimisation must be assessed separately and then evaluated together.
Important policy change
What changes for reservations on 1 February 2027?
Microsoft is restricting exchanges for certain reservations when the corresponding service is supported by savings plans. Refund rules and trade-ins for eligible reservations remain separate.
Previously purchased reservations
Reservations bought before 1 February 2027 retain one final exchange for affected services.
New reservations
Reservations bought from this date cannot be exchanged when the corresponding service is supported by savings plans. Exceptions apply to unsupported or certain retiring services.
The cancellation limit remains
Refunds currently cannot exceed USD 50,000 in remaining commitment within a rolling 12-month period per applicable billing scope.
Purchases remain final
A savings plan cannot be cancelled, refunded, or exchanged for a reservation. Eligible reservations may, however, be traded in for a new savings plan under Microsoft's rules.
CSP customers cannot always perform actions such as exchange, refund, or renewal themselves. The relevant Microsoft partner may need to complete the transaction.
Practical examples
Which model typically fits?
| Situation | Typical direction | Why? |
|---|---|---|
| A production VM runs continuously with the same family and region | Assess a reservation | Usage is stable and highly predictable. |
| VM sizes and regions change regularly | Assess a savings plan | The benefit can apply more flexibly to eligible usage. |
| A VM may be retired in six months | Start with pay-as-you-go and planning | A long commitment could become unused. |
| A stable Windows VM with eligible existing Windows licences | Assess reservation plus Hybrid Benefit | Compute rates and the software component can be optimised separately. |
| Many changing resources but stable minimum hourly spend | Assess a conservative savings plan | Configuration changes while a reliable cost baseline remains. |
Review before purchase
Eight questions for a defensible decision
- 01Have unused resources been removed and active resources right-sized?
- 02Which usage genuinely runs continuously across the proposed term?
- 03Will the service, SKU or VM family, and region remain stable?
- 04What is the conservative baseline rather than the short-term peak?
- 05Which scope provides strong utilisation and clear cost ownership?
- 06Have existing reservations, savings plans, and Azure Hybrid Benefits been considered?
- 07Which agreement, role, refund, and exchange rules apply to the specific purchase?
- 08Who will monitor utilisation, coverage, expiry, and auto-renewal after purchase?
Key takeaway
The best discount is the commitment that fits actual usage.
A reservation is powerful for stable, clearly attributable usage. A savings plan provides more flexibility. Both should be based on an optimised, conservative, and regularly monitored baseline.
Current and verifiable
Official Microsoft sources used for this article
Coverage, available products, and economic impact vary by Azure service, agreement, and purchase date. Review the current Microsoft terms before every purchase.
- 01Microsoft Learn: Decide between a savings plan and a reservation↗ (opens in a new tab)
- 02Microsoft Learn: What are Azure Reservations?↗ (opens in a new tab)
- 03Microsoft Learn: What are savings plans?↗ (opens in a new tab)
- 04Microsoft Learn: How reservation discounts are applied↗ (opens in a new tab)
- 05Microsoft Learn: Savings plan scopes↗ (opens in a new tab)
- 06Microsoft Learn: Reservation exchanges and refunds↗ (opens in a new tab)
- 07Microsoft Learn: Savings plan cancellation policy↗ (opens in a new tab)
- 08Microsoft Azure: Azure Hybrid Benefit↗ (opens in a new tab)
Note: This article provides clear orientation and does not replace an individual pricing, agreement, or licensing assessment.