Rebuild your commitment discounts before Azure's exchange policy changes

Azure just changed the game for commitment discounts. Here’s what I’m actually doing about it.

You’ve probably seen by now that Azure’s reservation exchange policy is changing. From February 1, 2027, newly purchased reservations for savings-plan-eligible services (VMs, App Service, SQL DB, and so on) can no longer be exchanged. Reservations bought before the cutoff keep one final exchange. After that, the flexibility we’ve relied on is gone.

In my client engagements I’ve leaned heavily on reservations. They offer the higher discount, and thanks to exchanges and instance size flexibility they were surprisingly adaptable. You just had to play the game: adjust the reservations to the effective SKU footprint once or twice a month. It’s ongoing work, but it paid off every single time. Savings plans I only used for the rest: workloads that reservations couldn’t cover, or that were too volatile to commit to a specific SKU.

That model relied on exchanges. So with this change, the real question is: what now?

My recommendation is to start rebuilding the commitment footprint today, not in 2027. Think of it like a pension plan: you don’t want a single big one, you want several, maturing at different times. The same logic applies here. The target is many small savings plans and reservations rather than a few large ones, staggered so that a portion of the commitment rolls off every year, ideally quarterly or even monthly.

Two reasons this matters:

• Once you’re in a savings plan you lose exchangeability. SPs can’t be exchanged. So a single big SP just relocates the inflexibility. A ladder keeps you liquid.
• Something always coming due means a regular, low-stakes moment to re-optimise as your fleet and pricing evolve, instead of one big cliff.

To get the ladder started, you can mix 1-year and 3-year savings plans and reservations across different start dates. One caveat from the field: commitment discounts don’t stack with your enterprise discount. So for some workloads a 1-year SP barely beats the discount you already have and may not pay off. Check the math per case before you commit.

Use the runway until Feb 2027 to consolidate reservations onto the SKUs you actually want long-term, and start laddering your SPs in parallel. The teams who start now get to do this deliberately, on their own schedule, rather than scrambling to rebuild a whole commitment footprint against a hard deadline.