Azure Reservation Exchange Rules set to tighten from February 2027
Microsoft has announced a change to how Azure reservations can be exchanged. From February 1, 2027, reservations purchased for services also covered by Azure savings plans - including Azure Virtual Machines, Azure App Service, and Azure SQL Database - will no longer be eligible for exchange to a different reservation.
Today, if capacity needs shift, a workload moves region, or a different VM type is a better fit, customers can exchange a reservation for one that matches. From February 1, 2027, that option disappears for newly purchased reservations in the affected services. Two related options stay in place, though: instance size flexibility still applies automatically within a VM family, and a reservation can still be traded in for a savings plan at any time. What's disappearing is specifically the ability to exchange one reservation for a different reservation.
Reservations bought before the deadline aren't affected. Organizations can keep exchanging them as often as needed until February 1, 2027, and retain the right to one final exchange after that date.
The restriction only applies where savings plans exist. Reservations are unaffected for products approaching end of life, for services without savings plan coverage such as Azure VMware Solution, or in environments that don't support savings plans.
What this means for your organization
Getting a reservation purchase wrong now carries a higher cost: it can no longer be corrected by exchanging into a different reservation. Trading in for a savings plan remains the fallback. This matters most for organizations that exchange reservations often due to shifting capacity, VM types, or regions.
It's a good time to review your Azure optimization strategy before the deadline, including whether savings plans suit your more dynamic workloads better. Want support with that assessment? Get in touch.
