Skip to main content

Guide · Azure · Commitments

Azure reservations: what changes on February 1, 2027, and what should you do before?

By Younes Jedouane · Published

The short answer

From February 1, 2027, an Azure reservation bought for a service that savings plans cover (virtual machines, App Service, SQL Database and similar services) can no longer be exchanged. Reservations bought before that date keep one final exchange, and until then you can exchange them as often as you like: now is the time to review them one by one, auto-renewal included.

The rule in one sentence

In Microsoft’s words: starting February 1, 2027, reservations purchased after this date aren’t eligible for exchange if 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.

In practice, Microsoft is steering workloads that change towards savings plans, which are more flexible, and keeping reservations for steady workloads. Reservations are still on sale. What goes away is the safety net: you can no longer fix a wrong size, region or term with an exchange. After the deadline, a bad purchase is either paid to the end of its term or traded in for a savings plan.

One detail explains everything that follows: Microsoft processes an exchange as a cancellation, a refund and a new purchase. That is why the four scenarios below play out the way they do, and why auto-renewal is the trap.

Four scenarios, depending on the purchase date

Microsoft illustrates the rule with four scenarios for a one- or three-year compute or database reservation. In every case, you can still trade the reservation in for a savings plan at any time.

Your situationWhat Microsoft says
Bought before February 1, 2027Exchange it as many times as you like until February 1, 2027. If you exchange it after that date, the new reservation can’t be exchanged.
Bought on or after February 1, 2027No exchanges at all. Trade-in for a savings plan and cancellation, within its limits, remain.
Bought before, several quantities, partial exchange afterWith 10 quantities, exchanging 2 after the deadline leaves each of the remaining 8 with its own final exchange.
Bought before, renewed afterA renewal, automatic or manual, counts as a cancellation plus a new purchase: the new reservation follows the 2027 rules and can’t be exchanged.

The fourth scenario is the most common and the easiest to miss. A three-year reservation bought in 2024 that reaches its end in 2027 with auto-renewal on becomes a brand-new reservation, locked in for its new term. If the workload it covers has changed in the meantime, you find out too late.

Who is affected, and who isn’t

Any reservation for a compute or database service that savings plans cover is in scope. Savings plans come in two families: compute (virtual machines, Dedicated Host, App Service) and databases. A service that becomes eligible for savings plans after February 1, 2027 is caught by the rule too: reservations you already hold for it then keep one final exchange.

Microsoft excludes three cases:

  • services that savings plans don’t cover, such as Azure VMware Solution: an Azure VMware Solution reservation is not affected;
  • deprecated products and services approaching end of life;
  • cloud environments that don’t support savings plans yet.

If you buy Azure through a CSP partner, note this: according to Microsoft, a CSP customer can’t exchange, cancel, renew or refund a reservation themselves; they ask their partner to do it. Build your partner’s lead time into your plan.

What doesn’t change

  • Instance size flexibility for virtual machines is untouched: a reservation still applies across sizes in the same family.
  • Cancellation is still available: total cancelled commitment can’t exceed USD 50,000 in a rolling 12-month window, per billing profile or Enterprise Agreement enrollment. Microsoft doesn’t charge early termination fees today, but says it may in the future.
  • Trade-in for a savings plan: a compute reservation can be traded for a compute savings plan, a database reservation for a database savings plan. The new plan’s total commitment must at least match what is left on the reservation, and a savings plan can’t later be exchanged for a reservation or another savings plan.
  • Reservations are still sold, and Microsoft still recommends them for steady, predictable workloads: when fully used, they give the biggest savings.

The auto-renewal trap

According to Microsoft, auto-renewal is turned on by default when you buy a reservation. It doesn’t extend the existing reservation: it buys a new one at expiry, with the same SKU, region, scope and quantity unless you change them. And because a renewal is a new purchase, any reservation renewed after February 1, 2027 can’t be exchanged.

Microsoft sends a reminder email 30 days before expiry for terms of a year or more, and again on the expiry date. Those emails go to the reservation’s owners and administrator and, depending on your agreement, to Enterprise Agreement contacts or your CSP partner: not necessarily to whoever runs the workload. The protective step is to open every reservation in the Azure portal, check its renewal setting and decide now, not 30 days out.

The checklist before February 1, 2027

Microsoft itself suggests an order that avoids paying for commitments you don’t need: remove waste first, fix existing commitments next, and only then buy new ones. Here it is, applied to the deadline.

  1. List your reservations and their dates

    On the Reservations page of the Azure portal, note for each one the service, the end date and the auto-renewal setting. The list shows reservations you own or can read; the tenant-level reservation administrator or reader roles show all of them.
  2. Measure how well they are used

    Each reservation shows its last known utilization; selecting it opens the history. A poorly used reservation is commitment paid for nothing: look at those first. Cost Management can also alert you on reservation utilization.
  3. Right-size before touching commitments

    Microsoft puts it bluntly: discounts reduce rates, not waste. Remove or downsize idle and oversized resources first.
  4. Exchange what needs exchanging, while it’s free

    Until February 1, 2027 there is no penalty and no annual limit on exchanges: another size, region or term, within the same product family. The new purchase must be worth at least what is left on the returned reservation, and it starts a new term. Only an owner or reservation administrator can do it.
  5. Or trade it in for a savings plan

    For a workload that moves between sizes, regions or services, trade-in is the lasting way out. Check the hourly commitment before you confirm: Microsoft warns that the default may not cover every machine the reservation used to cover.
  6. Decide on renewal, one reservation at a time

    Keep auto-renewal for a steady workload you are sure about; turn it off, or change quantity and term, for the rest. Renewal is the moment a reservation becomes final.
  7. Set the rule for future purchases

    After the deadline, buying a reservation is final. Write down your house rule: reservations for what is steady and measured, savings plans for everything else.

Reservation or savings plan after the deadline?

A reservation commits you to an instance family, in one region, for one or three years. A savings plan commits you to an hourly spend that applies automatically to eligible services in every region. Microsoft recommends reservations for workloads that run continuously with no expected change of type, family or region, and savings plans for workloads that evolve or move between regions.

The question to ask about every commitment

“Will this workload still be here, at the same size and in the same region, in a year? In three?” If the answer is an easy yes, the reservation is still the best price. If you hesitate, the savings plan gives you back the flexibility exchanges used to provide. To see where each of your reservations stands, the 2027 deadline simulator tells you, reservation by reservation, which of Microsoft’s scenarios applies and by when to decide.

Microsoft’s free tools help you prepare this review, each with its own limits. That is the subject of the guide on Azure Advisor, Cost Management and Azure Copilot.

What Finozio measures

From Pilot, Finozio’s Reservations page re-reads your Azure reservations and savings plans every night, read-only. What you see there:

  • the 30-day utilization of each reservation, as calculated by Azure; below 60%, it is flagged;
  • its end date and auto-renewal status, with an alert 60, 30 and 7 days before expiry;
  • the share of your eligible spend covered by reservations and by savings plans;
  • from Audit Spring, the reservation and savings plan purchases recommended by Azure Advisor, priced in euros among your savings, with a 30-minute debrief.

Start with your Azure baseline

The free scan gives you your subscription’s inventory and what it cost over the last 30 days, read-only and with no credit card. It doesn’t read your reservations: it shows you where to look before you review them.

Free Azure scan

Frequently asked questions

Can a reservation bought before 2027 still be exchanged?

Yes. Until February 1, 2027 you can exchange it as many times as you like. After that date it has one final exchange left, and the reservation you get from that exchange can’t be exchanged again.

Does auto-renewal change anything?

Yes. Microsoft treats a renewal as cancelling the original reservation and buying a new one. A reservation renewed after February 1, 2027 therefore follows the new rules and can’t be exchanged. Auto-renewal is on by default when you buy.

Can I still cancel a reservation?

Yes, the cancellation policy isn’t changing: total cancelled commitment can’t exceed USD 50,000 in a rolling 12-month window, per billing profile or Enterprise Agreement enrollment.

Is an Azure VMware Solution reservation affected?

No. Services that savings plans don’t cover, such as Azure VMware Solution, are excluded from the rule, as are products approaching end of life and clouds that don’t offer savings plans yet.

I buy Azure through a CSP reseller: who does the exchange?

Your partner. According to Microsoft, a CSP customer can’t exchange, cancel or renew a reservation themselves: they ask their partner, who does it for them. Allow for their lead time in your plan.

Microsoft sources

Every fact about Microsoft comes from its official documentation; the date is that of the version we read. Microsoft updates these pages: its own page prevails.

Read next