Azure VM Price Increases and Retirements: What to Do Before 2027
Microsoft’s latest Azure virtual machine announcements give organizations a reason to revisit what they’re running, what it costs, and how long it can stay there. Selected older VMs are getting more expensive, several widely used series have a retirement date, and the infrastructure decisions you could comfortably postpone are becoming harder to ignore.
Somewhere, a modernization plan last updated in March 2020 just felt a disturbance in the Force.
The immediate concern is straightforward: protecting the budget and keeping applications available. The opportunity is more interesting. With the right engineering help, this transition could leave you paying less for comparable performance, operating a more resilient environment, and finally making progress on improvements that have been waiting for a quieter quarter.
Apparently, the quieter quarter has scheduling conflicts.
What Is Changing and When
Beginning February 1, 2027, Microsoft will roll out price increases of approximately 25% for selected older v1 and v2 VM series. Separately, Dv3, Dsv3, Ev3, and Esv3 VMs will retire on November 15, 2029. Those are different groups with different consequences. The pricing announcement affects the economics of continuing to run certain older infrastructure. The retirement announcement establishes a deadline for moving the affected applications: after retirement, those v3 sizes will no longer be available to create, resize into, run, or purchase. Microsoft’s retirement guidance confirms the timeline and applicable cloud exclusions.
There is also a separate regional pricing update beginning February 1, 2027. Selected VM and storage services in seven regions across Europe and Southeast Asia will see increases ranging from approximately 8% to 17%. Exclusions matter here. The older VM series covered by the approximately 25% increase are excluded from the regional increase, as are several newer VM series and storage services. Adding every announced percentage together would make for an alarming spreadsheet, but not an accurate one.
Beginning February 1, 2027, pricing will increase for specific Azure Virtual Machines and Azure Storage services in the following Azure regions:
| Azure region | Price increase |
|---|---|
| EU West (Amsterdam) | 9% |
| EU North (Dublin) | 17% |
| France Central | 11% |
| France South | 11% |
| Norway East | 9% |
| Norway West | 9% |
| Southeast Asia (Singapore) | 8% |
Your actual exposure depends on the resources you use, where they run, and how you purchase them.
Existing Reserved Instances retain their contracted pricing benefits through expiration. That provides breathing room, although the loss of renewal options for affected series means the eventual transition still needs attention. Uncovered usage can move to pay-as-you-go rates when a reservation expires. Savings Plans also deserve review because pricing for affected VMs changes with the underlying rates. A discount commitment is useful; it still needs to fit the infrastructure you intend to operate. Microsoft’s reservation transition guide explains the purchasing changes.
Start With the Applications, Not the VMs
For decision makers, the first useful outcome is a clear picture of which applications are affected and when their costs or operating options change. A VM inventory alone won’t tell you whether the finance system needs priority treatment, whether a reservation expires next month, or whether an application has been quietly consuming twice the capacity it needs.
This is where a partner like TrustedTech can bring engineering and commercial expertise into the same conversation. Engineers can identify the affected workloads, measure how they actually perform, and evaluate replacement options. Those findings then support a plan that accounts for reservation timing, migration effort, and the business’s tolerance for disruption.
The objective is to find a newer VM series or an alternative service that delivers the performance the application needs at a lower effective cost. Sometimes that means a newer VM with a lower rate. Sometimes, better performance allows a smaller configuration or fewer instances. For suitable applications, a managed database or application service may reduce the infrastructure your team has to maintain.
The savings need to survive contact with the workload. A cheaper hourly rate loses some charm if it comes with slower reporting, additional licensing costs, or a migration that consumes the next six weekends.
Moving to newer generations can also require changes to operating system images, storage interfaces, or networking support. Microsoft has lifted previously announced growth restrictions on selected v4 families, widening the available options, but destination capacity still depends on the VM size and region. Good engineering work establishes compatibility and availability before anyone commits to a production date. Microsoft’s modernization guidance reinforces the need to validate readiness and move in controlled waves.
That gives you a sensible short-term path: address the workloads facing the earliest financial impact, prove the migration approach, and move them during planned maintenance windows. The longer-term work can then follow a schedule tied to application priorities and measurable business value.
Use This Deadline to Reopen the Modernization Plan
Which brings us back to that modernization plan.
When COVID hit, many organizations made the decisions necessary to keep people working and businesses functioning. Broader improvements understandably slipped. Years later, some of those temporary arrangements have acquired documentation, dependencies, and the quiet confidence of permanent infrastructure.
These Azure changes create a reason to reopen the plan and reassess it against today’s needs. An application that needs a new VM may also be overdue for an operating system update. A database migration may be the right moment to evaluate a managed service. A workload review may reveal that capacity added during an emergency is still being billed long after the emergency ended.
You can tackle those opportunities in stages. An urgent VM move does not require completing the entire modernization roadmap first.
Funding That May Cover Part of the Work
There may also be help paying for the work. Microsoft offers funding, Azure credits, and deployment assistance for eligible projects through programs such as Frontier Accelerate for Azure. Depending on eligibility and the approved scope, that support can cover some, and potentially all, of a defined assessment or implementation engagement. Microsoft also offers qualifying deployment assistance at no cost through Cloud Accelerate Factory.
Partners like TrustedTech can help determine which resources fit the project and coordinate access to them. Funding needs confirmation before it becomes a line in the business case, but it deserves investigation before the project gets shelved again on the assumption that the budget cannot support it.
Next Steps
The useful outcome here is an environment that costs less to run, supports the business reliably, and gives your internal team fewer aging infrastructure problems to work around.
A conversation with TrustedTech’s engineering team can establish which workloads need attention, where comparable performance may be available at a lower rate, and how to turn those findings into a funded, manageable implementation plan.
That modernization document has had a respectable shelf life. It might finally be time to give it an execution date.
