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:
- 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; 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.