Azure's February 2027 reservation exchange change: what to exchange, trade in and buy
In brief
Azure reservations bought after February 1, 2027 for savings plan services can't be exchanged. What changes, what doesn't, and a worked portfolio to act on.
Steve Elliott · · 7 min read
On this page
Azure reservations bought after February 1, 2027 for services that savings plans cover, including Virtual Machines, App Service and SQL Database, can't be exchanged. Reservations bought before that date keep one final exchange, and trade-in to a savings plan stays open, so the ten weeks left are the last window for unlimited exchanges.
The decisions are which reserved instances to exchange now, which to trade in, which renewals to stop, and how to split new commitments between reservations and savings plans once the rule is live. Policy details below are as of November 2026.
What exactly changes on February 1, 2027?
Microsoft Learn's exchange and refund page says reservations purchased after February 1, 2027 aren't eligible for exchange if the corresponding service is supported by savings plans. It names Virtual Machines, App Service and SQL Database "and similar services". Microsoft's July 30, 2026 announcement gives the fuller list:
- Compute. Virtual Machines (including exchanges between non-premium and premium storage sizes), Dedicated Host and App Service.
- Databases. Azure Database for PostgreSQL, Azure Database for MySQL, Azure DocumentDB, Cosmos DB, SQL Database and SQL Managed Instance.
Products that become savings plan eligible later fall under the same rule, with one final exchange for existing reservations.
Microsoft's policy-change page works through four scenarios. In short:
- A reservation bought before February 1, 2027 can be exchanged as often as you like until that date, then once more. That last exchange is processed as a cancellation, refund and new purchase, and the new reservation can't be exchanged.
- A reservation bought after February 1, 2027 can't be exchanged.
- If you exchange part of a quantity after the deadline, say 2 of 10, the other 8 each keep their one final exchange.
- A renewal that happens after February 1, 2027, automatic or manual, counts as a new purchase. The renewed reservation can't be exchanged.
Microsoft's stated reason is that the change brings exchange policy into line with the flexibility savings plans already offer, and gives customers a "clear, predictable framework for choosing the right commitment-based discount for each workload." In our view, that is fair, and the effect is that flexibility moves into savings plans and reservations become firm bets on a configuration.
What doesn't change?
Microsoft lists these as unaffected:
| Item | Status as of November 2026 |
|---|---|
| Instance size flexibility for VMs | Unchanged. A reservation still applies across sizes in the same flexibility group |
| Cancellation and refund | Unchanged. Total canceled commitment can't exceed $50,000 in a rolling 12 months per billing profile or enrollment (per customer for CSP) |
| Trade-in to savings plans | Unchanged and available at any time, including for reservations bought after the deadline |
| Azure VMware Solution | Not affected, because savings plans don't cover it |
| Deprecated products near end of life; clouds without savings plans | Excluded |
| Buying and renewing reservations | Still available |
Two exchange-page mechanics matter here. First, the new reservation's total lifetime commitment must be equal to or greater than the remaining commitment of the one returned, and it starts a new term from the exchange date. Second, exchange refunds don't count against the $50,000 cancellation limit. So an exchange can redirect or extend a commitment, but it can't shrink it. Neither can a trade-in, which has the same floor. The only way to reduce committed dollars is cancellation, inside the $50,000 limit.
How does trade-in work, and what does it cost you?
Compute reservations (Virtual Machines, Dedicated Host, App Service) trade in for a compute savings plan; database reservations for a savings plan for databases. You can trade in up to 100 reservations in one savings plan purchase, and partial quantities are allowed.
Trade-in is a one-way door: Microsoft says savings plan purchases are final and can't be canceled or exchanged for a reservation. Microsoft's decision guide says that when fully utilized, reservations can provide greater savings than savings plans for stable workloads. Azure's pricing page puts compute savings plans at up to 65% off pay-as-you-go and the savings plan for databases at up to 35%, on select services.
The savings plan for databases, announced in March 2026, covers SQL Database (including Hyperscale and serverless), SQL Managed Instance, PostgreSQL, MySQL, Cosmos DB, DocumentDB and Database Migration Service. SQL Server hourly licenses on Azure VMs and Azure Arc draw down the commitment at pay-as-you-go rates. Microsoft's savings plan overview and its March announcement list one- and three-year terms; the pricing page lists one year only. Confirm with your account team before planning around a three-year database plan.
An illustrative portfolio: what to do with each reservation
The numbers below are made up to show the mechanics. They don't describe any company or reflect Azure prices. Take an enterprise with five reservations costing $147,000 a month, reviewed in December 2026.
| Reservation | Monthly cost | Utilization | Situation | Action before February 1 |
|---|---|---|---|---|
| ERP VMs, 3-year | $30,000 | 98% | Stable for years | Keep. Don't spend the exchange |
| Analytics VMs, 3-year | $40,000 | 60% | Moving to a newer VM series in 2027; about 12 months left | Exchange now if the target is known |
| App Service, 1-year | $12,000 | 85% | Apps moving between regions next year; 8 months left | Trade in to a compute savings plan |
| SQL Database vCore, 1-year | $15,000 | 95% | Auto-renews in March 2027 | Decide before the renewal |
| Azure VMware Solution | $50,000 | 97% | Unaffected | No action |
ERP VMs. Instance size flexibility absorbs resizing within its group, and the unused final exchange is insurance.
Analytics VMs. This one wastes $16,000 a month and has about $480,000 of commitment left, which any replacement must at least match:
- A new 1-year reservation would need $40,000 a month, repeating the over-commitment.
- A new 3-year reservation sized to real usage, say $24,000 a month, cuts the monthly bill by $16,000. But the lifetime commitment rises to $864,000 and runs to the end of 2029 or early 2030.
- A 1-year compute savings plan with the same $480,000 lifetime, the default trade-in figure of about $54.79 an hour, pays off only if other eligible compute fills it. At savings plan rates, those dollars buy less coverage.
- Cancellation is capped at $50,000 in any rolling 12 months.
In our view, exchange now only if the target VM series and region are settled. If they aren't, keep the final exchange for later in 2027, when the target is known, and accept a few more months of waste; the remaining commitment, and so the minimum replacement, falls each month. Microsoft doesn't say whether a reservation created by an exchange before February 1 keeps its own final exchange, so confirm before relying on it.
App Service. Its $96,000 of remaining commitment can fund a 1-year compute savings plan at about $10.96 an hour that follows the apps across regions. That is the default trade-in figure, and it covers less than the $16.44 an hour the reservation did, so the rest runs at pay-as-you-go rates. Sizing by Microsoft's method means a $144,000 one-year commitment. Check eligibility: the pricing page lists only Premium v3 and Isolated v2 App Service plans.
SQL Database. Under Microsoft's renewal scenario, a March 2027 renewal produces a reservation that can't be exchanged. If the database is staying put, renewing is fine; trade-in remains the exit. If a move to SQL Managed Instance or an elastic pool is likely, exchange before the March renewal, and turn off auto-renew if the move isn't ready; the exchange page allows exchanges within the SQL product family. If a move to PostgreSQL is likely, a savings plan for databases is the better fit, because cross-family exchanges aren't allowed.
What should you do before February 1, 2027?
- List every reservation with its service, purchase date, expiry, auto-renew setting and 30-day utilization. Flag those covered by savings plans.
- Right-size first. Microsoft's own sequence starts here, because "discounts reduce rates, not waste."
- Exchange the underused ones where the target configuration is settled. Each starts a new term.
- Review renewals due after February 1. Turn off auto-renew where undecided, so a renewal doesn't create a non-exchangeable reservation.
- Trade in reservations covering dynamic workloads, sized from the trade-in page's method not the default hourly commitment, which Microsoft warns may fall short.
- Bring forward approved purchases only. A reservation bought before February 1 keeps a final exchange. We think that justifies moving up a purchase already approved for a stable workload, not buying one early for the option alone. Microsoft doesn't say how a purchase on February 1 itself is treated, so don't plan one for that day.
- Record which reservations still hold their final exchange, so nobody spends one by accident.
What should you buy after February 1, 2027?
Azure applies reservation benefits first, because they are more restrictive and usually carry greater discounts, then savings plans. Savings plan benefit is use-it-or-lose-it each hour. Microsoft's decision guide points the same way: right-size, fix existing commitments, buy reservations only for stable workloads, then size savings plans to the clean baseline.
In our view, after the deadline a reservation should pass one test: would you bet the configuration won't change for the term? If yes, the deeper discount is worth the lost exchange. If not, use a savings plan. We also think 1-year reservations become more attractive relative to 3-year ones, because time is now the main exit; the others are trade-in to a lower-discount plan and cancellation capped at $50,000 in any rolling 12 months. Track commitment utilization and effective savings rate together, so a cheaper-looking reservation that sits idle shows up as the cost it is.
A commitment is a funding decision as much as a pricing one, and it is easier to make well when the owner, the workload and the budget it draws on are visible in one operating model.
None of this is contract or accounting advice. Confirm the terms that apply to your agreement with Microsoft or your partner.
Sources
- Microsoft Learn, Self-service exchanges and refunds for Azure Reservations, updated July 29, 2026
- Microsoft Learn, Changes to the Azure reservation exchange policy, updated August 31, 2026
- Microsoft Community Hub FinOps Blog, Reservation exchanges for Azure services covered by savings plans, Kyle Ikeda, July 30, 2026
- Microsoft Learn, Self-service trade-in for Azure savings plans, updated September 14, 2026
- Microsoft Learn, Decide between a savings plan and a reservation, updated October 29, 2026
- Microsoft Learn, What are savings plans?, updated October 29, 2026
- Microsoft Learn, How a savings plan discount is applied, updated October 29, 2026
- Microsoft Learn, Azure saving plan cancellation policies, updated October 29, 2026
- Microsoft Learn, Instance size flexibility, updated July 17, 2026
- Microsoft Azure, Azure savings plans pricing, accessed November 21, 2026
- Microsoft Community Hub FinOps Blog, Announcing savings plan for databases, March 18, 2026, updated September 11, 2026
Frequently asked questions
Can I still exchange Azure reservations after February 1, 2027?
Only some. Reservations bought before February 1, 2027 for services covered by savings plans keep one final exchange, and the reservation it produces can't be exchanged again. Reservations for those services bought after that date can't be exchanged. Services savings plans don't cover, such as Azure VMware Solution, keep the existing exchange policy.
Does the change affect Azure reservation cancellations or refunds?
No. Microsoft says the cancellation policy isn't changing. Total canceled commitment still can't exceed $50,000 in a rolling 12-month window per billing profile or enrollment, and no early termination fee is charged as of November 2026, though Microsoft says one might be introduced. Exchange refunds don't count against the $50,000 limit.
Should I trade in my reservations for a savings plan before the deadline?
Not necessarily. Trade-in stays available after February 1, 2027, including for new reservations, so there is no deadline for it. It suits workloads that move across regions or services. It is irreversible: savings plans can't be canceled or exchanged, and Microsoft says fully utilized reservations can save more on stable workloads.
Does a reservation that auto-renews after February 1, 2027 keep its exchange?
No. Microsoft treats a renewal after February 1, 2027, automatic or manual, as a cancellation and new purchase, so the renewed reservation can't be exchanged. It can still be traded in for a savings plan. If you haven't decided on a workload's future, review the auto-renew setting before the renewal date.
Steve Elliott
Published November 22, 2026
More on FinOps & Cloud
FOCUS, commitments, shared cost.
Keep reading
Top Product Marketing Events to Attend in 2027
Product marketing events for 2027, from the Product Marketing Summit series and PMM Leaders Summit to launch festivals and local meetups, with dates and tips for attending.
Top Product Marketing Conferences to Attend in 2027
The major conferences for product marketers in 2027, including SaaStr AI Annual, UNBOUND, the Product Marketing Summit and Web Summit, with dates and locations by region.
Effective savings rate: the commitment number finance should ask for
Coverage and utilization can both look healthy while commitments save little. Why finance should ask for effective savings rate, and how to check the math.
FOCUS 1.4 and invoice reconciliation: matching cloud cost data to what accounts payable pays
Why cloud cost data rarely matches the invoice, what FOCUS 1.4's Invoice Detail and Billing Period datasets add, and a month-end routine for controllers.