Blog Post

Azure Compute Blog
6 MIN READ

Incoming Changes for Window Server 2022 Marketplace Image Users

Ning_Kuang's avatar
Ning_Kuang
Icon for Microsoft rankMicrosoft
Oct 07, 2024

New Windows Server 2022 Images are available to support .NET 6 deprecation 

Starting March 9th 2025, a new offer of Windows Server 2022 images (windowsserver2022) is available in Azure Marketplace. These refreshed images exclude .NET 6 packages that have reached end of support, to help organizations stay aligned with Microsoft’s security and lifecycle standards.  

With .NET 6 reaching End of Life (EOL) in November 2024, users are advised to migrate off .NET 6 versions. The new image offer is built on the latest Windows Server 2022 SKU and will no longer include deprecated .NET 6 packages, simplifying the deployment.  

Users should complete migrating to new images before June 2026. After June 9th 2026, there will be no .NET 6 support for these legacy Windows Server 2022 images that have .NET 6 preinstalled.  In addition, these legacy images will be out of compliance policies and will be deprecated. 

Actions Required: 

  • Migrate to the new Windows Server 2022 images(details in FAQ section below). These images will not automatically replace existing legacy images —you must explicitly reference the new image in your deployment process or re-image workflows.  
  • If you have applications depending on .NET 6, upgrade your applications to the latest .NET version as soon as possible. See .NET and .NET Core official support policy | .NET for the latest .NET version.  Note that future versions like .NET 8/.NET 10 are no longer included in Windows Server media and must be installed separately if needed.     

Deprecation legacy Windows Server 2022 images 

The legacy Windows Server 2022 images that pre-installed .NET 6 will begin deprecation after June 9th 2026.  

  • .NET 6 in these legacy images won't be patched after the depreciation starts.
  • No new versions for these legacy Windows Server 2022 images will be released once the deprecation begins. Virtual machine scale sets won't get new OS patch updates via images; standalone VMs will still get them via Windows Update.
  • These legacy images will follow the Azure Marketplace Image Graceful Deprecation process. The image deprecation will enter the enforcement stage at the end of 2026.
  • For details on how image deprecation enforcement impacts your workload, see Deprecated Azure Marketplace images - Azure Virtual Machines | Microsoft Learn  

Who are impacted

This change impacts all users of the following Windows Server 2022 Marketplace media images, with the offer name “Windows Server”, these legacy images will be deprecated, regardless of whether .NET 6 is actively used or not: 

  • PublisherID== microsoftwindowsserver
  • OfferID== windowsserver
  • For SKU, refer to the table below: 

2022-DATACENTER 

2022-DATACENTER-AZURE-EDITION 

2022-DATACENTER-AZURE-EDITION-CORE  

2022-DATACENTER-AZURE-EDITION-CORE-SMALLDISK  

2022-DATACENTER-AZURE-EDITION-HOTPATCH  

2022-DATACENTER-AZURE-EDITION-HOTPATCH-SMALLDISK  

2022-DATACENTER-AZURE-EDITION-SMALLDISK  

2022-DATACENTER-CORE  

2022-DATACENTER-CORE-G2  

2022-DATACENTER-CORE-SMALLDISK  

2022-DATACENTER-CORE-SMALLDISK-G2  

2022-DATACENTER-G2  

2022-DATACENTER-SMALLDISK  

2022-DATACENTER-SMALLDISK-G2  

 

Frequently Asked Questions 

How can I identify the impacted VM/VMSS in my subscription?

  • To identify the Virtual Machines created from the impacted images, use the offer ID, SKU and publisher ID as filter when setting “imageReference" properties.  Refer to the sample code for Virtual Machines and Virtual Machine Scale Sets. The offer ID distinguishes legacy from new images, so ensure it is included.

Where can I find the new offer for Marketplace Windows Server 2022 images? 

  • For each impacted image SKU, you can find the correspondent new image SKU (with the same SKU name) in the new offer. 
  • The new Offer with Offer Name “Windows Server 2022” is published with .Net 6 excluded; you can find the new offer in Azure Marketplace, or from Azure portal. To reference the new offer programmatically, use following image information: 
    • PublisherID== microsoftwindowsserver
    • OfferID== windowsserver2022
    • For SKU, refer to the table below: 

2022-DATACENTER 

2022-DATACENTER-AZURE-EDITION  

2022-DATACENTER-AZURE-EDITION-CORE  

2022-DATACENTER-AZURE-EDITION-CORE-SMALLDISK  

2022-DATACENTER-AZURE-EDITION-HOTPATCH  

2022-DATACENTER-AZURE-EDITION-HOTPATCH-SMALLDISK  

2022-DATACENTER-AZURE-EDITION-SMALLDISK  

2022-DATACENTER-CORE  

2022-DATACENTER-CORE-G2  

2022-DATACENTER-CORE-SMALLDISK  

2022-DATACENTER-CORE-SMALLDISK-G2  

2022-DATACENTER-G2  

2022-DATACENTER-SMALLDISK  

2022-DATACENTER-SMALLDISK-G2  

Note the new offer has the same Windows Server 2022 SKU name as the legacy image offer. 

Will the legacy Windows Server 2022 images still receive .NET 6 patches before deprecation? 

  • For existing legacy images with .NET 6 preinstalled, patching support for .NET 6 will continue until June 2026 before deprecation starts. These images will contain the latest security patch for .NET 6 during this time.  
  • However, .NET 6 has officially reached end of support; it is no longer serviced via any other means outside of the Azure marketplace images. Applications still depending on .NET6 should migrate to .NET 8/.NET10 as soon as possible.  

Will Microsoft remove .NET 6 from the Windows Server 2022 marketplace images? 

  • Based on customer feedback, .NET 6 will not be automatically removed from the legacy Windows Server 2022 images; these legacy images will be deprecated instead. This gives organizations the flexibility to plan and execute their own migration strategy before deprecation begins. 
  • To ensure .NET 6 is not installed by default on Virtual Machine Scale Sets, run an OS image upgrade to the new image. For standalone VMs, either reimage the VM or remove .NET 6 from existing machines. 
  • To remove .NET 6 from your virtual machines, follow below steps:  
  1. Identify Installed Versions
    • Run the following command to list all installed .NET versions: dotnet –info
  2. Uninstall .NET 6
    • Use the appropriate uninstall command for each .NET 6 version you find; be sure to specify the exact version number to ensure complete removal: dotnet-hosting-<6.0.37 or your current .NET version>-win.exe  /uninstall 

 

Can I mitigate the .NET 6 risk without re-image the VM or re-create the VMSS?

Yes.

Standalone VM:

For existing standalone VMs, once the VM is created, there is no immediate dependency on the original image, so your VM will continue to function and receive OS patches via Windows Update after the image deprecation starts from June 9th 2026.

To address the .NET 6 EOL risk without re-image, you can remove .NET 6 packages from the VM following below steps:

  • Identify Installed Versions - run the following command to list all installed .NET versions: dotnet –info
  • Uninstall .NET 6 - use the appropriate uninstall command for each .NET 6 version you find: dotnet-hosting-<6.0.37 or your current .NET version>-win.exe  /uninstall

Be sure to specify the exact version number to ensure complete removal.

Note whenever you create new VM, or re-image the existing VM in the future, you must use a supported image, as any new VM creation using deprecated .NET 6 images will fail once enforcement begins in early 2027.

VMSS VM:

For VMSS, especially those using AutoOSUpgrade, switching to new image is required because patching depends on the source image. Simply removing .NET 6 is not sufficient, as new updates will continue to include it. However when switching to a new image for VMSS, you still do not need to re-create the VMSS, you can update the VMSS model, see  Modify an Azure Virtual Machine Scale Set - Azure Virtual Machine Scale Sets | Microsoft Learn for details.

If you are using custom images for VMSS, a temporary workaround without switching the image may be possible by updating your custom image each cycle—downloading latest OS patches from Windows Update and removing .NET 6 before rollout—but this approach requires ongoing maintenance and does not replace the need for eventual migration to supported images.

 

Help and support 

  • If you have questions, get answers from  Community Experts in Microsoft Q&A. 
  • If you have a support plan and you need technical help, go to the Services Hub and create a support request. Select the product family : Developer Tools, the product:  .NET, and the version .NET 8.0 or .NET 10. 
  • If you are considering alternative solutions for supporting .NET 6 beyond its end-of-support date, further information can be found here: Dot NET Security Group.

 

 

 

Updated Jun 25, 2026
Version 16.0

4 Comments

  • Madhanraj's avatar
    Madhanraj
    Copper Contributor

    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

    1. 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?
    2. 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?
    3. Can we continue to use Azure VM Redeploy and Reapply operations on these VMs after the image is deprecated?
      • Any known restrictions?
    4. Can we continue to resize the VM (change SKU) after the image is deprecated?

    2     Backup & Recovery

    1. 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)
    2. Will Azure Site Recovery failover/failback continue to work for VMs created from deprecated images?
    3. 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

    1. Can we continue creating snapshots of the OS disk and data disks after image deprecation?
    2. Can a new VM be created from an existing managed disk or snapshot taken from the deprecated image after 9 June 2026?
    3. Will there be any restrictions when creating a managed image from an existing VM based on the deprecated offer?
    4. Can we continue using Azure Compute Gallery images that were created from these VMs before deprecation?

    4     RDS/Application Workloads

    1. 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?
    2. 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)

    1. Will VMSS scale-out, reimage, repair, and instance replacement operations continue to work after 9 June 2026?
    2. If not, what exact operations will be blocked?

    6     Supportability & Compliance

    1. If we choose not to migrate, will the VM be considered unsupported by Azure Support?
    2. Will Azure Advisor, Service Health, or Defender continue generating alerts for these VMs?
    3. Is there a final retirement date beyond which existing VMs will be affected, or is the deprecation only for image publishing?

    7     Migration Clarification

    1. Does Microsoft officially require rebuilding the VM from the new windowsserver2022 offer, or is there a supported in-place conversion method planned?
    2. For VMs with Plan = null (standard MicrosoftWindowsServer images), is migration recommended or mandatory?

     

    • ISites_SystemsSupport's avatar
      ISites_SystemsSupport
      Copper 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.

  • This depends on whether you are using stand alone VM or Virtual Machine Scale Set. IF you are using stand alone VM, yes, you can uninstall .NET 6 on existing VM, then the VM will not be impacted by the source image deprecation. However when creating new VM, or whenever you need to re-image the existing VM, you need to use the new supported image offer.    IF you are using Virtual Machine Scale Set, then the existing VM will still depend on the source image for image update. You need to switch to the new image offer. Note this does not mean you need to re-create the VMSS.  You can update the VMSS model with the new image offer:  Modify an Azure Virtual Machine Scale Set - Azure Virtual Machine Scale Sets.

  • nmbrphi's avatar
    nmbrphi
    Tin Contributor

    I have a question regarding the migration path: is moving existing VMs to the new Windows Server 2022 image strictly required for production scenarios, or is it still supported to keep VMs running on the current image as long as .NET 6 is manually uninstalled (given that it’s out of support)?

    In other words, is the breaking change tied specifically to the presence of .NET 6, or to the underlying image itself?
    Understanding this would help in planning whether a full image migration is mandatory or if maintaining the existing VMs remains a viable option.