Azure Migrate classic appliance retires September 2026

If you are running a VMware exit into Azure through Azure Migrate's agent-based replication, the date worth checking this week is not on next year's calendar. It has already passed. Microsoft's own tutorial for agent-based VMware migration carries a retirement notice with two dates in it, and the first of the two is behind us.

What the notice actually says

Four facts, in the order they matter to someone with replication running right now:

• The final recovery point for existing replications was 31 May 2026. Past.
• Support for migrating those existing replications runs until 30 September 2026. That is roughly six weeks from today.
• The classic replication appliance retires 30 September 2026.
• All new migrations on the agent-based path must use the simplified appliance. There is no "start one more wave on the old appliance" option.

Why the passed date is the urgent half

Most end-of-support posts are about planning: here is a date, here is the runway, here is the sequence. This one is not, and the difference is worth naming plainly. A retirement date ahead of you is a scheduling problem. A recovery-point date behind you means the tool has already stopped doing the part of the job you were relying on, and nothing in your change calendar told you.

So the first action is not a plan, it is a look. Open the appliance and read the most recent recovery point for every replication you have running through it. Whatever the console shows, Microsoft's notice is the vendor's statement about what the platform will produce going forward, and the retirement date is the point at which migrating those replications stops being supported at all. If your cutover runbook assumes a current recovery point on the far side, that assumption needs re-testing against what is actually there — before you find out during a cutover window.

Six weeks of supported migration, then none

From 19 August 2026, the gap to 30 September is six weeks. That is enough time to finish a wave that is already staged and tested. It is not enough time to discover the problem, re-plan the destination, re-seed replication on a different appliance, and run a clean cutover for a large estate. Which of those two positions you are in is the whole question, and it is answerable in an afternoon.

1. Inventory what is still on the classic appliance. Not what the migration plan says — what the appliance is actually replicating today, VM by VM.
2. Read the most recent recovery point on each. This is the check that tells you whether you are finishing a migration or restarting one.
3. Move every new migration to the simplified appliance now. The notice is unambiguous on this point, and starting new work on a path that retires in six weeks buys nothing.
4. Decide, per VM, between finishing and re-seeding. Anything that cannot realistically cut over inside the window should be re-planned onto the simplified appliance deliberately rather than by deadline.
5. Put 30 September 2026 on the change calendar as a hard stop, not as a review point.

A second, weaker signal on the Azure Site Recovery side

Related but separate, and it deserves the hedge: Microsoft's end-of-support 2026 lifecycle page lists Azure Site Recovery's "Classic VMware protection scenario" at 29 March 2026 — also already past. That is a different product line from the Azure Migrate replication appliance, and a lifecycle-page listing is not a description of your tenant. Treat it as a reason to open Azure Site Recovery and check your own configuration, not as a conclusion about it. If you are protecting VMware workloads through the classic scenario, that is a second conversation to have this month rather than next quarter.

The other input nobody put in the model: memory

Here is where the tooling deadline meets the destination decision. A VMware exit that lands on-premises usually means buying new hypervisor hosts, and a hypervisor host is mostly memory — the DIMMs are frequently the largest single line on the quote. Memory pricing is therefore a live input to the exit arithmetic in 2026, and it compounds with the VMware licensing increases that started the conversation. Labelled honestly:

• Actuals. TrendForce, published 18 August 2026, reported 2Q26 results: combined revenue of the top five NAND Flash brands rose 77% quarter-on-quarter to US$68.87 billion. That is reported revenue for a quarter that has closed, not a projection.
• Forecast. TrendForce, published 3 July 2026, forecast conventional DRAM contract prices up 13–18% quarter-on-quarter in 3Q26 and NAND up 10–15%.
• Forecast. TrendForce, published 9 July 2026, forecast server DRAM contract prices up 13–18% quarter-on-quarter in 3Q26, and noted that multi-year long-term agreements signed by US cloud providers cap the increases for those customers.
• Forecast. IDC, published 2 June 2026, forecast 2026 global PC shipments down 11.3% while average selling prices rise around 17%, with the memory shortage persisting through 2027. IDC's figure is the whole PC market — it does not split commercial from consumer, so do not read it as a business-PC number.

None of this makes the destination decision for you. It changes one input on one side of it, and it changes it in a direction that favours getting quotes early and in writing rather than assuming last year's per-host price still holds. The full destination framework — six dimensions, scored — is in our Azure versus Hyper-V decision guide; treat memory pricing as a modifier on the capex-versus-opex dimension, not as a new dimension.

Where this sits in the longer VMware timeline

Keep the two clocks separate, because conflating them is how exits get mis-sequenced. vSphere 8 End of General Support is 11 October 2027. That is the platform deadline — the one that sets the outer boundary on how long the current estate can sit still. The Azure Migrate classic appliance retirement on 30 September 2026 is a tooling deadline more than a year inside it. You are not being forced off vSphere in six weeks. You are being forced off one migration path in six weeks, and if that path was how you planned to leave, the plan needs revisiting now rather than in 2027.

What we would do this week

1. Open the classic appliance, list every active replication, and record the most recent recovery point for each.
2. Split the list into "can finish before 30 September" and "cannot", honestly, with cutover windows named.
3. Re-seed the second list onto the simplified appliance, and route all new migrations there regardless.
4. Separately, check whether Azure Site Recovery's classic VMware protection scenario is in play in your tenant.
5. If the exit is heading on-premises, get host quotes in writing now and re-run the capex line with current memory pricing rather than last year's.

Related reading

• The six-dimension destination decision, Azure IaaS versus Hyper-V: VMware to Azure vs Hyper-V: 500-VM decision guide.
• The full vendor landscape after Broadcom: VMware after Broadcom: Hyper-V, Nutanix, Azure.
• The on-premises migration timeline in practice: After Broadcom: 250-VM Hyper-V migration in 90 days.
• Where Azure Local fits as a destination: Azure Local as a VMware exit destination.
• The open-source flank: XCP-ng as a VMware alternative: what it costs.
• Service detail: VMware to Azure.
• Service detail: VMware Exit Decision Framework.

Sources and further reading

• Microsoft Learn — Migrate VMware VMs to Azure (agent-based), carrying the classic replication appliance retirement notice
• Microsoft Learn — Products and services retiring in 2026
• TrendForce (18 August 2026) — 2Q26 NAND Flash brand revenue
• TrendForce (3 July 2026) — 3Q26 DRAM and NAND contract price forecast
• TrendForce (9 July 2026) — 3Q26 server DRAM contract price forecast
• IDC (2 June 2026) — PC market volatility as the memory shortage persists through 2027

The 30-second version

Azure Migrate's classic replication appliance retires 30 September 2026. The final recovery point for existing replications through it was 31 May 2026 — already past — and support for migrating those existing replications ends at the retirement date, roughly six weeks out. All new migrations on the agent-based path must use the simplified appliance. Separately, Microsoft's lifecycle page lists Azure Site Recovery's classic VMware protection scenario at 29 March 2026, which is also past and worth checking in your own tenant. The wider VMware clock is longer: vSphere 8 End of General Support is 11 October 2027. And if the exit lands on-premises, price the hosts now — memory is the largest line on a hypervisor quote, and the buyers with contracts capping their increases are not mid-market buyers.

If you want a senior engineer to look at what is still replicating through the classic appliance and tell you whether it finishes before 30 September, the project intake form takes about three minutes. Two-business-day response with scope and a fixed-fee range.

Pro IT NW does not resell VMware, Broadcom, Microsoft Azure, or any virtualization platform, and we do not sell hardware. Senior-led, labor-only, fixed fee. Vendor dates in this post are quoted from the vendor's own published pages on the dates linked; verify them against your own tenant before acting.