An Azure reservation is a one or three year commitment to a specific capacity in exchange for a discount over pay as you go. Because usage drifts, Azure provides two ways to correct a reservation that no longer fits. An exchange swaps it for one or more reservations that better match current usage, with the unused value carried across and no cancellation fee. A refund cancels the reservation and returns the prorated unused amount, subject to an early termination limit and a cap on how much you can refund in a given window. The buyer takeaway is that a mismatched reservation is not stranded money; it is a correction, and the right correction is usually an exchange.
Here is how each works, the rules to plan around, and when to choose which.
How does a reservation exchange work?
An exchange lets you turn in a reservation and apply its remaining value to a new one that fits your usage better, for example moving to a different VM series after a migration or consolidating several small reservations into one. The remaining value transfers across, and there is no penalty for the swap itself; the new reservation simply starts a fresh term for the exchanged amount. Exchanges are the natural tool when the need has not gone away but has changed shape, because you keep the commitment discount working rather than dropping coverage. Note that Microsoft has narrowed exchange eligibility for some products over time, most notably compute, so confirm current exchange rules for the specific reservation type before you rely on it.
How does a reservation refund work?
A refund cancels the reservation and returns the unused, prorated value, less any early termination charge that applies. Two limits shape it: refunds are capped at a defined amount within a rolling twelve month window across your billing scope, and the proration means you recover the remaining term's value, not the whole purchase. A refund is the right move when the underlying need has genuinely disappeared, a workload retired, a project wound down, with no replacement to exchange into. Because of the rolling cap, large scale unwinds need to be paced so you do not exhaust the refund allowance partway through.
When should you exchange versus refund?
Exchange when the workload changed but the commitment still has a home: a new instance series, a different region, or consolidation of fragmented reservations. Refund when the workload is gone and there is nothing to exchange into. As a rule, prefer the exchange where it is available, because it preserves discount coverage and avoids the early termination charge and the refund cap entirely. Reserve refunds for true retirements. And build the habit on the buy side: layering smaller, staggered reservations rather than one large purchase reduces how often you need either correction, because each layer is smaller and closer to its own expiry.
A worked example
A scaling fintech had bought several reservations against a VM series it later moved off as it rearchitected onto a more efficient family. Rather than let the commitments run as waste or cancel them into the refund cap, it exchanged them for reservations on the new series and consolidated three fragmented purchases into one cleaner commitment in the process. Coverage stayed matched to actual usage, no cancellation fee applied, and the refund allowance was kept in reserve for a genuinely retired workload elsewhere. The correction was administrative, not architectural, and kept the effective savings rate intact. Figures are verified against billing data and anonymised.
| Situation | Use | Why |
|---|---|---|
| Workload changed shape | Exchange | No fee, coverage preserved |
| Fragmented reservations | Exchange to consolidate | Simpler, matched commitment |
| Workload retired entirely | Refund | Recover prorated value |
Talk it through with us
If reservations have drifted out of step with your Azure usage, the fix is usually an exchange rather than wasted commitment, and we can map the cleanest correction. We take zero provider commissions and answer only to you, across AWS, Azure, GCP, and OCI. Our guarantee is plain: we reduce your cloud spend or we reimburse our service fee, on either a Fixed Fee scoped up front or a no risk Gainshare share of verified savings. Book a strategy call to scope it for your estate, and follow more analysis in The Cloud Spend Navigator.
Frequently asked questions
Can you exchange an Azure reservation?
How do Azure reservation refunds work?
Should you exchange or refund a reservation?
Put a defensible number on your cloud spend.
No provider in the room, no published price list. Tell us your footprint and we will scope the savings against your billing data — we reduce your cloud spend or we reimburse our service fee.
The Cloud Spend Navigator: what changed in cloud pricing, commitments, and FinOps — no vendor spin.