On February 1, 2027, two Azure changes land on the same day, and the one getting the headlines is the smaller of the two. Microsoft is raising prices on virtual machines and storage by 8% to 17% in seven regions and by roughly 25% on legacy v1 and v2 VM series everywhere. On that same date, any reservation you buy for a VM, App Service or SQL Database stops being exchangeable. A price increase costs you a percentage. A commitment you can no longer reshape costs you whatever your forecast gets wrong for the next one to three years.
FinOps teams have spent the last few years treating Azure reservations as a soft commitment: buy the three-year term for the deep discount, and if the workload moves to a new series or region, exchange it. That safety valve is what made aggressive reservation coverage defensible in a budget review. After February 1, it is gone for new purchases.
What Microsoft changed, and what it left alone
The pricing side came through Azure Service Health notifications in early October. Techzine’s breakdown lists the regional increases: 17% in North Europe (Dublin), 11% in France Central and France South, 9% in West Europe (Amsterdam), Norway East and Norway West, and 8% in Southeast Asia (Singapore). Microsoft published only a list of exemptions, not a list of affected services; v7 VM generations and several storage types (standard block blobs, tables, queues, Azure Container Storage) are exempt. The legacy series take a separate global increase of about 25%, which replaces the regional one rather than stacking on top of it. nOps lists the affected series as Bv1, D, Ds, F, Fs, G, Gs, Ls, NP and HC on the v1 side, and Av2, Amv2, Dv2, Dsv2, Fsv2 and Lsv2 on the v2 side.
The commitment side is documented on Microsoft’s own reservation exchange policy page, and the wording is precise: “reservations purchased after this date aren’t eligible for exchange if the corresponding service is supported by savings plans.” That covers Azure Virtual Machines, App Service, SQL Database “and similar services,” plus any compute or database product that becomes savings plan eligible later. Reservations bought before February 1 keep “the right to one final exchange.”
Three things did not change, and they matter for planning:
- Instance size flexibility stays. A reservation still floats across sizes within its family, so a D4 commitment can still cover two D2s.
- The cancellation cap stays at $50,000. Per the exchange and refund policy, total canceled commitment cannot exceed $50,000 in a rolling 12-month window per billing profile or enrollment.
- Trade-in to a savings plan stays. You can still convert a reservation into a savings plan at any time.
Reservations for products that savings plans don’t cover, such as Azure VMware Solution, are outside the new rule entirely.
The calendar, read as a decision sequence
From now until January 31: unlimited exchanges, old prices
This is the last window in which a new reservation carries full flexibility. Microsoft’s own Scenario 1 says a reservation purchased before February 1 can be exchanged “as many times as you like” until that date. Techzine reports that existing reservations hold their fixed price until the end of the term for the compute they cover, while a savings plan’s hourly commitment buys less capacity once underlying rates rise.
Put those together and the logic for stable workloads in the seven affected regions is unusual: commitments bought before February 1 lock in today’s rate and keep an exchange in reserve. A Dublin workload that will still be running in 2028 is a strong candidate for a reservation purchased in December, not one purchased in March.
The exception is anything on v1 or v2 hardware. New reservations on those legacy series stopped on July 1, 2026, and the Dv2 and Dsv2 families retire on May 1, 2028. Migrate first, then commit on the target series. Because v7 is exempt from the regional increase, it is the obvious place to land if your workloads are compatible.
February 1: the auto-renewal trap
Microsoft’s Scenario 4 is the one most teams will miss. A renewal “is processed as a cancellation of the original reservation and a new reservation purchase,” so a reservation that auto-renews after February 1 comes back as a new purchase under the new terms. It is not exchangeable. Your old flexible reservation quietly turns into a rigid one because a checkbox was ticked in 2024.
The fix is administrative. Pull every reservation with a renewal date after February 1, 2027, switch auto-renew off, and put each one on a review list with an owner and a date. Renewal becomes a decision rather than a default.
After February 1: one exchange left, and it is one-way
The “one final exchange” is narrower than it sounds. Scenario 1 spells out that if you exchange a pre-February reservation after the cutoff, “the new reservation isn’t exchangeable,” because exchanges are also processed as a refund and a new purchase. Scenario 3 adds a useful detail: the right applies per quantity, so exchanging 2 of 10 units leaves the other 8 with their own final exchange intact. Use it on the units whose future you are least sure of, and only after you know where the workload is going.
Your remaining exits all cost something:
- Trade-in to a savings plan. Microsoft’s trade-in rules require the new savings plan’s lifetime commitment to equal or exceed the reservation’s remaining commitment, and “you can’t exchange a savings plan for a reservation or for another savings plan.” Savings plans typically discount less than reservations, so a trade-in is a permanent step down in discount depth.
- Cancellation. It is capped at $50,000 a year, and Microsoft calculates refunds on “the lowest price of either your purchase price or the current price.” Microsoft also notes a possible future 12% early termination fee, which it is not charging today.
Against a multi-year reservation portfolio, a $50,000 annual ceiling is a pressure valve, not an exit.
What this does to commitment strategy
The practical effect is that reservations and savings plans stop being near-substitutes. Before, you could buy a reservation for the discount and count on exchanges if things changed. After February 1, a reservation is a fixed bet on a specific family in a specific region, and a savings plan is the only flexible instrument left. Microsoft says as much in its policy note: reservations “remain the appropriate option for predictable, stable workloads,” while savings plans suit “evolving or dynamic workloads.”
That pushes three changes into the FinOps operating model:
- Split your coverage target by workload stability, not by discount. Commit reservations only against usage with at least a year of stable history and no planned migration. Cover everything else with savings plans, even at a shallower discount. Our reservations vs savings plans guide walks through the stability test.
- Move the migration decision ahead of the purchase decision. Under the old policy, you could commit first and exchange later. Now a reservation bought on Dv5 in March and a planned move to v7 in June is a stranded commitment.
- Re-forecast the savings plan line for the seven regions. If your savings plan covers Dublin or Paris usage, the same hourly commitment will cover less after February 1, and the overflow bills at the new pay-as-you-go rate. Budget the difference now rather than discovering it in the March invoice.
The regional increase is one more data point in a pattern this site has tracked through 2026: memory and component costs flowing into ordinary compute pricing and capacity scarcity changing what a commitment is for. The exchange change is different in kind. It does not move a rate; it moves risk from Microsoft’s balance sheet to yours. Every reservation purchased after February 1 means your forecast has to be right, because Microsoft no longer absorbs the cost of it being wrong.
If you run a meaningful Azure estate, the work for the roughly 100 days left is concrete: inventory reservations by renewal date, disable auto-renew on anything renewing after the cutoff, finish v1 and v2 migrations, and make your stable-workload purchases before February 1 while they still carry an exchange. For the wider Azure cost picture, our Azure cost management guide covers the rest of this year’s changes.