Commitment discounts such as RIs and savings plans may be part of the standard tool bag, but we bet your cloud team still loses sleep over them; they're essentially a wager on an uncertain future. If you've ever bought a three-year Azure reservation and then watched the workload get re-platformed six months later, you will know the quiet comfort of the exchange button. From 1 February 2027, that button disappears for most of Azure.
In this post we'll look at how cloud discounts work, the tools that automate them, and what Microsoft's change means for those tools and for us.
First, let's map the territory
Azure and AWS sell the same basic deal: commit to paying for a set amount of certain cloud resources for one or three years, and get a discount off pay-as-you-go (PAYG) rates. Each offers two types.
- Reservations (Azure) or Reserved Instances (AWS) commit you to a specific resource, such as a VM family in a region. They give the deepest discount but are the least flexible.
- Savings plans commit you to an hourly dollar amount of eligible spend. The discount applies automatically across regions and services. It's smaller, but it follows your usage wherever it goes.
The two clouds differ mainly in their exit clauses, which are an ITAM person's favourite part of any contract.
| Option | AWS today | Azure (from 1 Feb 2027) |
|---|---|---|
| Deepest discount | Standard RIs: no exchanges, limited modifications | Reservations: no exchanges (one final exchange for those bought before the cutoff) |
| Discount with exchange rights | Convertible RIs: smaller discount, exchangeable within the same region | None for services covered by savings plans |
| Flexible option | Savings Plans | Savings plans |
| Getting out | Resell Standard RIs on the AWS Marketplace | Cancel reservations up to US$50k in refunds per rolling 12 months, or trade them in for a savings plan |
AWS has always charged for flexibility through the smaller Convertible RI discount. Azure was more generous, pairing Standard-level discounts with near-unlimited exchanges. That generosity is what Microsoft is now withdrawing.
One point for ITAM readers: reservations and compute savings plans don't cover software licence charges such as Windows Server or SQL Server. That remains your territory, and Azure Hybrid Benefit's. (Azure's newer savings plans for databases are the exception: they can include SQL Server hourly licences.)
Enter autonomous discount management
Commitment discounts involve a trade-off. Commit too little and you overpay at PAYG rates; commit too much and you pay for capacity you don't use. Most organisations handle this with a quarterly spreadsheet and a cautious guess, which usually means under-committing.
Autonomous discount management (ADM) hands that job to software. The tool reads your billing and usage data and then buys, exchanges and rebalances commitments for you, continuously and without a human approving each purchase.
The core technique is laddering. Each commitment still runs for its full one- or three-year term, but instead of one large purchase you buy many small ones over time. Rather than one $120/hour plan bought in January, you might hold twelve $10/hour plans bought a month apart, so one expires every month. If usage drops, you don't replace the expiring rung; if it grows, the next rung is bigger. No contract is ever broken, but the portfolio can track usage within months rather than years.
The benefits:
- Higher coverage with less risk. You can safely commit to more of your usage, because the exposure is spread over many small slices.
- Less toil. Nobody has to model, approve and buy commitments every quarter.
- No technical changes. Savings come from commercial adjustments, not re-configuration.
- Measurable results. Vendors report an Effective Savings Rate (ESR): the actual saving as a percentage of PAYG cost. That makes the result easy to put in front of a CFO.
You can ladder by hand, and Microsoft and AWS both recommend staggered purchases. Doing it every month, across hundreds of subscriptions and several discount types, is where software earns its keep.
Who's in the game?
The options range from free advice to fully hands-off automation:
- Native tools. Azure Advisor and AWS Cost Explorer both recommend purchases. They're free, but advice only; someone still has to decide, buy and keep track.
- Independent specialists. Vendors including nOps, Zesty and Usage.ai automate purchasing, mostly with a share-of-savings fee and, in some cases, guarantees against under-use.
- Platform players. Flexera has assembled one of the broadest offerings. It acquired NetApp's Spot portfolio in March 2025, including Spot Eco (now Flexera One Cloud Commitment Management), and in January 2026 acquired ProsperOps, which now leads its rate optimisation capability.
So what is Microsoft changing?
From 1 February 2027, Azure reservations can no longer be exchanged for any service that savings plans also cover. Today that means VMs, Dedicated Host, App Service and the main managed databases (e.g. SQL Database). Reservations bought before the cutoff keep one final exchange, and the reservation it produces can't be exchanged again. Cancellations (within the US$50k refund limit per rolling 12 months), trade-ins to savings plans, and instance size flexibility all continue.
Does this spell the end for ADM?
The obvious take is that this is bad news for ADM vendors. Exchanges were one of their main ways to correct a commitment that no longer fitted, and without them every Azure portfolio becomes harder to steer. ProsperOps says so itself, expecting median savings rates to fall from 2027.
We think the more interesting effect is on everyone else. Faced with reservations that can't be changed, most in-house cloud teams will do the sensible, defensive thing and move to savings plans. ProsperOps expects "many (possibly most)" customers to do exactly that. The cost is significant: by ProsperOps' figures, one-year compute reservations save about 43% more than savings plans, and three-year ones about 26% more.
So the gap between a cautious DIY approach and an automated portfolio is likely to widen, not reduce. Keeping a layer of non-exchangeable reservations, laddered so it can still shrink, is exactly the fiddly, continuous and unforgiving work that software does better than a quarterly spreadsheet. Removing the exchange safety net makes the tightrope harder for everyone, but harder still for those without the tools.
This is where ITAM and FinOps meet. A reservation is now a multi-year contract with limited exit rights, and it deserves the same scrutiny as any software agreement. At TMG we help organisations set the commitment strategy, put the governance around it, and choose the right automation to run it.
What should you do before February?
- Inventory your Azure reservations. Each one's final exchange is now a scarce asset, and only reservations bought before 1 February keep that right.
- Separate the stable from the uncertain. Reserve only the baseline you are confident won't move; put everything else on savings plans.
- Tighten governance. Under the new rules, a reservation purchase is a contract decision more than a technical one, and approvals should reflect that.
- Get a baseline. Work out your current savings rate, then see what an automated approach would deliver against it. A free TMG commitment health check will show you the gap, comparing autonomous discount management with your current approach.
A final thought. For years, cloud was sold as the end of long-term commitments. Yet here we are, carefully reading terms, exit clauses and refund caps on multi-year deals. Cloud didn't make ITAM redundant; it gave us a new set of contracts to manage.
Want to talk through what the February 2027 change means for your Azure estate? Reach out to us at info@tmg100.com.
Disclosure: TMG is a Flexera partner.
The Mastermind Group (TMG) is an independent ITAM and FinOps managed services provider, working with organisations across Australia and beyond to optimise technology spend, manage risk, and get the most from their IT investments. Learn more at tmgitam.com.
