.png)
Key takeaways
1
The wrong scope can quietly waste a well-sized reservation.
2
For most metered products, unused hourly reservation benefit is lost but commitment units differ by product, so verify the rules for yours.
3
A stopped VM may still incur costs until it is deallocated.
4
Savings Plans provide more flexibility but usually lower discount depth.
5
Careful sizing matters because refunds and exchanges have limits, and the exchange rules are set to tighten on February 1, 2027.
Azure Reservations reduce the cost of stable, predictable Azure usage by applying discounted rates to matching resources for a committed term typically one or three years, though the term options depend on the product.
Microsoft advertises savings of up to 72% for qualifying virtual machines, but the real result depends on the service, region, term, configuration, and utilization. Reservations change billing only. They do not modify workloads, deploy infrastructure, or guarantee capacity.
The trade-off is precision. A reservation can save more than a flexible commitment, but an incorrect SKU, region, quantity, or scope can leave paid benefits unused.
Microsoft advertises savings of up to 72% for qualifying virtual machines, but the real result depends on the service, region, term, configuration, and utilization. Reservations change billing only. They do not modify workloads, deploy infrastructure, or guarantee capacity.
The trade-off is precision. A reservation can save more than a flexible commitment, but an incorrect SKU, region, quantity, or scope can leave paid benefits unused.
What Azure Reservations actually do
An Azure Reservation is a billing discount for eligible resource usage. You select the reservation attributes, such as service, SKU, region, term, quantity, and scope. Azure then checks usage each hour and automatically applies the discount when the attributes match. See Microsoft’s overview of what Azure Reservations are for the full model.
For virtual machines, a reservation generally covers compute. Storage, networking, and software licensing remain separate. Azure Hybrid Benefit may reduce eligible Windows Server or SQL Server licensing costs.
A Reserved VM Instance lowers the price of matching usage but does not guarantee deployment capacity. Upfront and monthly reservation payments have the same total cost.
For virtual machines, a reservation generally covers compute. Storage, networking, and software licensing remain separate. Azure Hybrid Benefit may reduce eligible Windows Server or SQL Server licensing costs.
A Reserved VM Instance lowers the price of matching usage but does not guarantee deployment capacity. Upfront and monthly reservation payments have the same total cost.
Discount, capacity priority, and a capacity guarantee are three different things
| Mechanism | What it does | Capacity guarantee? |
|---|---|---|
| Reserved VM Instance (reservation) | Discounts billing for matching usage | No |
| Capacity priority | Designates data-center capacity as important for your deployments to improve access | No — no SLA |
| On-Demand Capacity Reservation | Sets aside compute for a VM size in a region or zone, billed at pay-as-you-go | Yes — backed by an SLA |
A reservation can be configured with capacity priority to improve your odds of launching instances, but Microsoft is explicit that capacity priority does not carry an SLA.
If you need a guarantee for business continuity, disaster recovery, or mission-critical scale-out an On-Demand Capacity Reservation is the separate, SLA-backed product, and it is billed at pay-as-you-go rates whether or not the reserved capacity is used.
A reservation and a capacity reservation can be combined: term-commitment discounts can apply to the used or unused capacity reservation.
If you need a guarantee for business continuity, disaster recovery, or mission-critical scale-out an On-Demand Capacity Reservation is the separate, SLA-backed product, and it is billed at pay-as-you-go rates whether or not the reserved capacity is used.
A reservation and a capacity reservation can be combined: term-commitment discounts can apply to the used or unused capacity reservation.
How reservation discounts apply
Reservation benefits are hourly and, for most metered products, use-it-or-lose-it. If matching usage is unavailable in a given hour, the unused quantity for that hour generally does not roll into the next hour or offset a later traffic peak.
That hourly model fits VM matching and many database and storage reservations, but commitment units are not uniform across products. Blob Storage reserved capacity is a fixed-capacity commitment purchased in 100-TiB or 1-PiB blocks, and Microsoft Foundry Provisioned Throughput Reservations commit a fixed number of provisioned throughput units for a one-month or one-year term.
Always confirm the meter, commitment unit, and matching rules for the specific reservation before relying on the hourly rule.
That hourly model fits VM matching and many database and storage reservations, but commitment units are not uniform across products. Blob Storage reserved capacity is a fixed-capacity commitment purchased in 100-TiB or 1-PiB blocks, and Microsoft Foundry Provisioned Throughput Reservations commit a fixed number of provisioned throughput units for a one-month or one-year term.
Always confirm the meter, commitment unit, and matching rules for the specific reservation before relying on the hourly rule.
Two separate ordering rules
Azure applies commitment benefits in a defined order. Two things are easy to conflate, so it helps to treat them separately.
Reservation scope priority. If you hold reservations at more than one scope, Azure evaluates them from the narrowest to the broadest and applies the most specific match first:
Reservation → eligible pre-purchase plan → Azure Savings Plan → pay-as-you-go
Reservations are evaluated before Savings Plans because they are more restrictive. For the mechanics, see Microsoft’s guidance on how a reservation discount is applied and the Azure savings plan for compute overview.
Instance size flexibility can reduce mismatch risk for supported VM families. For example, one reservation normalized for a larger VM may cover multiple smaller VMs in the same eligible size group. It does not create unlimited flexibility across unrelated families, services, or regions.
Reservation scope priority. If you hold reservations at more than one scope, Azure evaluates them from the narrowest to the broadest and applies the most specific match first:
- Resource group
- Subscription
- Management group
- Shared
Reservation → eligible pre-purchase plan → Azure Savings Plan → pay-as-you-go
Reservations are evaluated before Savings Plans because they are more restrictive. For the mechanics, see Microsoft’s guidance on how a reservation discount is applied and the Azure savings plan for compute overview.
Instance size flexibility can reduce mismatch risk for supported VM families. For example, one reservation normalized for a larger VM may cover multiple smaller VMs in the same eligible size group. It does not create unlimited flexibility across unrelated families, services, or regions.
How Azure reservation scope works
Azure reservation scope is the billing boundary that determines which matching resources can receive the discount. It does not change resource permissions, deployment behavior, or ownership.
| Scope | Discount can cover | Best fit | Main risk |
|---|---|---|---|
| Resource group | One resource group | Isolated team or application | Highest mismatch risk |
| Subscription | One subscription | Stable cost-center ownership | Usage cannot spill into another subscription |
| Management group | Eligible subscriptions in that group and billing scope | Business-unit pooling | More reporting complexity |
| Shared | Eligible subscriptions in the billing context | Broad utilization | Requires showback or chargeback allocation |
Shared scope offers the widest chance of matching usage in a multi-subscription environment. Narrower scope can suit chargeback or separation requirements.
Scope can be changed after purchase without restarting the term, and a multi-quantity reservation can also be split across scopes. See Microsoft’s steps to manage and rescope a reservation, and this internal guide to Azure Savings Plan scope for a deeper comparison.
Scope can be changed after purchase without restarting the term, and a multi-quantity reservation can also be split across scopes. See Microsoft’s steps to manage and rescope a reservation, and this internal guide to Azure Savings Plan scope for a deeper comparison.
The stopped VM billing trap
A VM in the Stopped state is still allocated to a host and remains billed for compute. That usage may continue consuming a matching reservation benefit even though the operating system is not running.
A VM in the Stopped (Deallocated) state releases the underlying compute and is not billed for VM compute. Storage and some networking charges can continue. Once deallocated, the reservation benefit can move to another matching VM in scope. If no match exists, that hourly reservation benefit goes unused.
A VM in the Stopped (Deallocated) state releases the underlying compute and is not billed for VM compute. Storage and some networking charges can continue. Once deallocated, the reservation benefit can move to another matching VM in scope. If no match exists, that hourly reservation benefit goes unused.
Warning:
An operating system shutdown is not the same as Azure deallocation. Verify automation scripts and shutdown policies by checking the VM power state, not only whether the guest OS is off.
This distinction should be part of every Azure VM cost optimization review, especially for development environments with nightly shutdown schedules.
Reservations versus Savings Plans
Reservations work best when the service, region, and configuration are stable. Azure Savings Plans work best when eligible spend continues but the underlying compute or database mix changes.
| Decision factor | Reservation | Savings Plan |
|---|---|---|
| Commitment basis | Specific eligible resource attributes | Fixed hourly spend |
| Term | Typically one or three years (varies by product) | Compute: one or three years; databases: one year |
| Flexibility | Lower | Higher across eligible usage |
| Published maximum | Up to 72% for qualifying VMs | Up to 65% for compute; up to 35% for databases |
| Cancellation | Refund possible within policy limits | Cannot be canceled or refunded |
| Best use | Stable baseline | Changing eligible usage |
Savings Plan benefits are hourly and do not roll over. Compute plans exclude software, storage, and networking. Database plans cover eligible infrastructure and software IP costs. Inspect meter-level coverage before sizing.
For a detailed decision model, read the internal guide, Azure Reservations versus Savings Plans, or Microsoft’s page on how to decide between a savings plan and a reservation.
What Azure reservations can cover
Reservation eligibility varies by product. Common examples include VMs, Dedicated Hosts, Azure SQL, managed databases, Cosmos DB, Synapse, Fabric, Databricks, eligible storage capacity, and selected provisioned AI throughput.
Microsoft currently advertises up to 72% savings for qualifying VMs and up to 80% for Azure SQL Database. The SQL figure combines a three-year reserved capacity commitment with Azure Hybrid Benefit in Microsoft’s specified Business Critical example. It is not a reservation-only discount applicable to every SQL deployment.
Microsoft also publishes examples of up to 70% for qualifying provisioned AI throughput and up to 38% for a specified Blob Storage scenario. Treat headline percentages as examples, not forecasts.
Microsoft currently advertises up to 72% savings for qualifying VMs and up to 80% for Azure SQL Database. The SQL figure combines a three-year reserved capacity commitment with Azure Hybrid Benefit in Microsoft’s specified Business Critical example. It is not a reservation-only discount applicable to every SQL deployment.
Microsoft also publishes examples of up to 70% for qualifying provisioned AI throughput and up to 38% for a specified Blob Storage scenario. Treat headline percentages as examples, not forecasts.
Note:
reservation mechanics are not uniform. Scope options, regional matching, supported terms, quantity units, and flexibility rules differ from one reservation product to another.
Storage (fixed-capacity blocks) and Foundry Provisioned Throughput (one-month or one-year PTU commitments) show how far the mechanics can vary. Validate the product-specific attributes on the relevant Microsoft pricing or purchase page before treating any rule as universal.
Storage (fixed-capacity blocks) and Foundry Provisioned Throughput (one-month or one-year PTU commitments) show how far the mechanics can vary. Validate the product-specific attributes on the relevant Microsoft pricing or purchase page before treating any rule as universal.
Before you buy: eligibility and exclusions
Reservations do not apply to every subscription type, offer, or service. Run a quick pre-purchase check before you commit:
- Agreement and offer type. Reservation discounts apply to resources in subscriptions purchased through Enterprise Agreement, Microsoft Customer Agreement, Cloud Solution Provider (CSP), and individual plans with pay-as-you-go rates. Resources in other offer types don’t receive the discount.
- Billing context. A reservation can only be scoped to subscriptions in the same billing context, so confirm the target subscriptions sit under the same billing profile or enrollment.
- Purchaser permissions. You need reservation owner or purchaser rights on the billing subscription, plus at least read access on a management group if you scope there.
- Unsupported services. Some consumption models are excluded. Reservation discounts do not apply to Azure SQL Database serverless, and Azure Cosmos DB serverless accounts are not supported for reservations either. Check the specific service’s reservation page before assuming coverage.
Refunds, exchanges, and trade-ins
Reservations provide more exit options than Savings Plans, but the limits matter.
Microsoft allows reservation refunds up to a combined USD 50,000 in canceled commitments within a rolling 12-month window for the billing profile or enrollment. Red Hat plans, SUSE Linux plans, and pre-purchase plans are excluded. Microsoft is not currently charging an early termination fee, though it notes a 12% fee may apply in the future.
The exchange policy is tightening. Per Microsoft’s current reservation exchange-policy guidance, starting February 1, 2027, reservations purchased on or after that date are no longer eligible for exchange when the corresponding service is supported by Savings Plans that covers Azure Virtual Machines, Azure App Service, Azure SQL Database, and similar services.
Reservations purchased before February 1, 2027 keep the right to one final exchange (processed as a cancellation, refund, and new purchase). The change excludes services not covered by Savings Plans, such as Azure VMware Solution, and products approaching end of life.
Regardless of the exchange rules, eligible reservations can still be traded in for a Savings Plan at any time, with no time limit.
The Azure commitment management strategy guide explains how exchange limits and refund caps affect planning.
The exchange policy is tightening. Per Microsoft’s current reservation exchange-policy guidance, starting February 1, 2027, reservations purchased on or after that date are no longer eligible for exchange when the corresponding service is supported by Savings Plans that covers Azure Virtual Machines, Azure App Service, Azure SQL Database, and similar services.
Reservations purchased before February 1, 2027 keep the right to one final exchange (processed as a cancellation, refund, and new purchase). The change excludes services not covered by Savings Plans, such as Azure VMware Solution, and products approaching end of life.
Regardless of the exchange rules, eligible reservations can still be traded in for a Savings Plan at any time, with no time limit.
The Azure commitment management strategy guide explains how exchange limits and refund caps affect planning.
Size the commitment safely
Start with the hourly floor, not the monthly average. Average usage can hide overnight or weekend drops that create unused benefits.
Use this process:
Use this process:
- Review 7-day, 30-day, and 60-day reservation recommendations.
- Separate stable production usage from temporary projects.
- Confirm the SKU, region, scope, and instance-size flexibility.
- Remove planned migrations, decommissions, and expiring environments.
- Buy below the verified floor when uncertainty remains.
- Recheck utilization after purchase before adding another commitment.
- Purchased quantity: 10 normalized units
- Matching hourly floor: 8 units
- Expected utilization: 8 divided by 10, or 80%
- Unused amount: 2 units each hour with no additional match
After you buy: monitor utilization and allocation
A reservation is not “set and forget.” Broad scopes (shared and management group) improve utilization but add allocation and reporting considerations. Review these metrics after purchase, before adding any further commitment:
- Utilization percentage how much of each matching hour the reservation actually covers.
- Unused quantity or hourly commitment the portion of the commitment expiring unused, hour by hour.
- Amortized cost the commitment spread across its term rather than shown as a single upfront charge, which is how you compare it fairly against on-demand spend.
- Effective savings realized discount versus the pay-as-you-go equivalent.
- Departmental allocation showback or chargeback across teams for shared and management-group scopes.
Build a layered strategy
A practical Azure commitment portfolio has three layers:
The goal is economically useful coverage without stranded commitment.
- Reservations for stable resources with predictable attributes
- Savings Plans for consistent spend that changes across eligible services or regions
- Pay-as-you-go or Spot for genuinely variable and interruptible demand
The goal is economically useful coverage without stranded commitment.
How Usage.ai fits in
Azure Reservations can deliver significant savings through long-term commitments, but choosing the right scope, purchasing the right reservation, and adapting as workloads change can be challenging.
Usage.ai analyzes your Azure compute usage and automates Azure Reservation management based on your consistent usage patterns. Instead of relying on manual forecasting and one-time purchasing decisions, Usage.ai continuously optimizes your reservation strategy as your Azure environment evolves.
With its Flex Insured Commitments program, teams can capture up to 72% savings available through Azure Reservations without taking on the long-term commitment risk. If a Reservation costs more than the equivalent pay-as-you-go usage, Usage.ai provides cashback protection to help cover the difference.
The result is a managed Azure Reservation strategy that combines Microsoft commitment discounts with automation, flexibility, and protection as your cloud environment evolves.
Usage.ai analyzes your Azure compute usage and automates Azure Reservation management based on your consistent usage patterns. Instead of relying on manual forecasting and one-time purchasing decisions, Usage.ai continuously optimizes your reservation strategy as your Azure environment evolves.
With its Flex Insured Commitments program, teams can capture up to 72% savings available through Azure Reservations without taking on the long-term commitment risk. If a Reservation costs more than the equivalent pay-as-you-go usage, Usage.ai provides cashback protection to help cover the difference.
The result is a managed Azure Reservation strategy that combines Microsoft commitment discounts with automation, flexibility, and protection as your cloud environment evolves.
Frequently asked questions
Can Azure reservation scope change after purchase?
Yes. Authorized users can change a reservation between supported scopes without restarting its term. Only subscriptions within the same billing context are eligible.
What happens to unused reservation hours?
For most metered products, unused reservation benefit expires each hour and does not roll forward or offset later usage. Commitment units differ by product, so confirm the meter and matching rules for your specific reservation.
Can an Azure Reservation be canceled?
Eligible reservations can be returned for a prorated refund, subject to product restrictions and the USD 50,000 rolling 12-month cancellation limit.
Do reservations cover software licenses?
Usually not for VM reservations. VM compute, storage, networking, and software licenses are separate meters. Azure Hybrid Benefit may reduce eligible licensing costs.
Which is better, a reservation or Savings Plan?
Choose a reservation for a stable, predictable resource configuration. Choose a Savings Plan when eligible spend is consistent but services, regions, or configurations may change.
Share
Facebook
X
LinkedIn
Reddit
