Friday 20th November 2026
From 1 February 2027, Microsoft is introducing targeted changes to Azure infrastructure pricing and reservation exchange rights. Combined with the retirement of selected v3 Virtual Machine series in 2029, these updates create an important planning point for anyone responsible for Azure cost, infrastructure and platform strategy.
These are not blanket price increases across every Azure service. The impact depends on the services you consume, VM generations, deployment regions, purchasing arrangements and existing commitments. The starting point should be evidence from your own estate, not headline percentages.
There are two separate pricing changes, and they should be assessed separately.
This applies to pay-as-you-go, Enterprise Agreement and Microsoft Customer Agreement rates in every region, so a workload can be affected even if it runs in UK South or UK West. Existing Reserved Instances keep their benefit for the rest of their term, while savings plans will reflect the higher underlying VM rates. The exact scope should be confirmed against the relevant Microsoft advisory before modelling.
These percentages apply by deployment region, not billing currency. A UK organisation could therefore be exposed through workloads deployed in Dublin, Amsterdam, France, Norway or Singapore. UK South and UK West are not included in this update, although that is no guarantee for future pricing.
The regional update excludes several services, including some older VM families that are already covered by the 25% change. Model the two areas of exposure independently rather than adding both percentages to the same resources. Do not rely on the Service Health Impacted Resources view as a complete inventory either; validate exposure against actual resource, meter, region and pricing data.
The Dv3, Dsv3, Ev3 and Esv3 series retire on 15 November 2029. After that date, they can no longer be created, resized into, run or purchased. Reservation purchases and renewals for these series have already ended, so existing reservation expiry dates should now drive migration and commitment planning.
Migration timing depends on more than the retirement date. You need to know which applications depend on affected VMs, who owns them, whether operating systems and applications are compatible with the destination, which regions and sizes can meet future needs, and when change windows and resources are available.
Microsoft has also lifted capacity growth restrictions for selected v4 series (including Dv4, Dsv4, Ev4 and Esv4), although quota approval remains subject to regional capacity.
Moving to a newer VM family is not a simple swap. Generation 1 Dv2 and Dv3 VMs cannot convert in place to Generation 2, so redeployment may be required. For retiring v3 workloads, Microsoft identifies v5 as the smoother, lower-disruption path. v6 and v7 need additional readiness checks across four key gates:
More detail is available in Microsoft Learn: Assess readiness for v6 and v7 VMs.
Newer infrastructure may suit some workloads, but savings and performance gains should not be assumed. For some, right-sizing on the current platform will be the answer; others may justify a newer VM generation or a managed service. Base the decision on technical and commercial evidence, not the age of the VM.
From 1 February 2027, reservations purchased on or after that date cannot be exchanged where the service is supported by a savings plan. This includes Azure Virtual Machines, Azure App Service and Azure SQL Database. Reservations bought before the deadline can be exchanged repeatedly until then and keep one final eligible exchange afterwards.
VM instance-size flexibility, the cancellation policy and eligible trade-ins to savings plans remain unchanged. See Microsoft's full policy: Changes to the Azure reservation exchange policy.
Reservations or savings plans? Reservations suit stable, predictable workloads. Savings plans apply a fixed hourly commitment, so higher rates consume it faster and leave more usage charged at pay-as-you-go rates. Either way, a commitment should follow a validated workload decision. Buying a reservation for infrastructure that is about to be resized, moved or modernised locks your commercial assumptions to a technical state that is already changing.
Don't wait for the changes to appear on your Azure bill. Bytes has developed scripts that can be run against your environment to identify potentially affected resources and give you a clearer view of your exposure.
Get in touch with Bytes to discuss Microsoft's announcements and arrange an assessment.
Want to keep informed? Sign up to our Newsletter