Blog Post
Incoming Changes for Window Server 2022 Marketplace Image Users
We are using a standalone VM on the below config:
Publisher: MicrosoftWindowsServer, Offer: WindowsServer, SKU: 2022-datacenter-azure-edition, Version: latest.
We have few queries regarding the migration path:
1 Existing VM Operations
- Will existing VMs continue to receive Windows Updates, Security Updates, Monthly CUs, and Hotfixes from Windows Update/Microsoft Update after 9 June 2026?
- Is there any impact to Windows Server 2022 OS patching?
- Is the deprecation only related to the Marketplace image or also to OS servicing?
- Will existing VMs remain fully supported by Microsoft if they continue running on the deprecated image after 9 June 2026?
- Any limitations on Azure VM support cases?
- Can we continue to use Azure VM Redeploy and Reapply operations on these VMs after the image is deprecated?
- Any known restrictions?
- Can we continue to resize the VM (change SKU) after the image is deprecated?
2 Backup & Recovery
- Can Azure Backup recovery points created before and after 9 June 2026 still be used to restore the VM successfully?
- Restore as VM
- Restore disks
- Cross-region restore (if enabled)
- Will Azure Site Recovery failover/failback continue to work for VMs created from deprecated images?
- If the VM is deleted accidentally, can it be restored from Azure Backup without requiring access to the original Marketplace image?
3 Snapshot & Disk-Based Recovery
- Can we continue creating snapshots of the OS disk and data disks after image deprecation?
- Can a new VM be created from an existing managed disk or snapshot taken from the deprecated image after 9 June 2026?
- Will there be any restrictions when creating a managed image from an existing VM based on the deprecated offer?
- Can we continue using Azure Compute Gallery images that were created from these VMs before deprecation?
4 RDS/Application Workloads
- For existing workloads such as RDS Licensing, Session Hosts, SQL, IIS, and File Servers, is there any functional impact if the VM remains on the deprecated image?
- Is there any dependency on .NET 6 only for the Marketplace image, or can installed applications continue using their existing runtimes without impact?
5 VM Scale Sets (Important)
- Will VMSS scale-out, reimage, repair, and instance replacement operations continue to work after 9 June 2026?
- If not, what exact operations will be blocked?
6 Supportability & Compliance
- If we choose not to migrate, will the VM be considered unsupported by Azure Support?
- Will Azure Advisor, Service Health, or Defender continue generating alerts for these VMs?
- Is there a final retirement date beyond which existing VMs will be affected, or is the deprecation only for image publishing?
7 Migration Clarification
- Does Microsoft officially require rebuilding the VM from the new windowsserver2022 offer, or is there a supported in-place conversion method planned?
- For VMs with Plan = null (standard MicrosoftWindowsServer images), is migration recommended or mandatory?
- ISites_SystemsSupportJun 04, 2026Copper Contributor
Full disclaimer, I don't work for Microsoft. Just an Azure Admin here. I had a long discussion with Copilot about this, and the best path forward for us. I was assured this won't affect running standalone images. Which includes those in availability sets. It said Azure Backup with continue to work. You can still restore VMs from those backups for recovery scenarios. You just won't be able to use those images in scale-out situations (VMSS) unless you create managed images in your environment.
If you create managed images or Azure Compute gallery images you will still be able to create VMs using the pre-deprecation images you have. But keep in mind you'll need to "Generalize" your VM first, which basically means running sysprep on it which resets everything. You'd have to sysprep it, deallocate it, create the managed image, and then you'll have it in your Custom Images blade. BUT, and it's a big BUT, your original VM is now basically reset, or set back to a fresh VM from an OOBE standpoint (SID, Username/Password, etc...). Anything you've configured (e.g. IIS, installed apps, etc.) will be there on your C drive, but your original source is now defunct for all intents and purposes. So you'd never want to do that on a production VM.
You could alternatively create a "Specialized" managed image that retains everything, basically like a snapshot (like one of your Azure Backup restore points). Then you could restart your VM as is, AND have your specialized image. It would allow you to restore that VM for disaster recovery purposes, but wouldn't work for scaling out as the machine would have the same SID, domain membership, etc. as your current prod VM.
For us, what that means is it's not really worth creating the images at all. We'll just continue to rely on Azure Backup if we need to restore a VM. And then, through attrition we'll move to the new Images (offerID: windowsserver2022 or windowsserver2025) as we expand or replace VMs for other reasons.
From what it told me, yes, you can still restore as VM, restore from disks, and do cross-region restores from Azure backup. BUT if you're using VMSS you won't be able to scale-out. Since we're not using VMSS and only using Availability Sets it's not an issue. I can't speak to what they officially support post-deprecation, but you'll still be able to install Windows Updates manually. But for security I'd remove .NET 6 if it's installed on any of your VMs (unless it's needed by you, and if so, you may just have to run a little insecure).
Regarding in-place image upgrades, I don't know a lot about it....heard it's possible, but sometimes risky. If I were you, I'd talk to Copilot about your environment and it will help you make a plan on what you need to do now, what can wait, and give you a path forward.