This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(76.8, 18%, 17%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESK%3C/text%3E%3C/svg%3E)
My question is regarding the virtual machine: the OS Service Pack is showing as Windows 11 Version 25H2 (x64). Can we ignore this notification?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(291.2, 38%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMP%3C/text%3E%3C/svg%3E)
That depends on the version of the image used to provision the VM
If the above response helps answer your question, remember to "Accept Answer" so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.
hth
Marcin
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(51.2, 6%, 14%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJH%3C/text%3E%3C/svg%3E)
Hi Shivaji Kaleru,
Thank you for your question regarding the Azure notification and for sharing that the virtual machine OS currently shows Windows 11 Version 25H2 (x64).
To address your query and proceed correctly, we would like to clarify a few points and request some confirmation from your side.
Although the operating system inside the VM has been updated to Windows 11 Version 25H2 via Windows Update, Azure sends deprecation notifications based on the Marketplace image plan used at the time the VM was originally deployed, not the current OS version.
In this case, the notification indicates that the VM was deployed using the Marketplace image plan:
To confirm the correct remediation approach, could you please help us with the following:
At the time of deployment, was this VM created using the Azure Marketplace image plan win11-23h2-pron?
Is the OS version 25H2 achieved through Windows Update after deployment, or was the VM originally deployed using a 25H2 Marketplace image?
This information will help us determine whether a planned migration is required or if the impact is limited.
At the time of deployment, was this VM created using the Azure Marketplace image plan win11-23h2-pron? - Yes
Is the OS version 25H2 achieved through Windows Update after deployment - Yes.
Please suggest on this.
You should consider implications of running deprecated images: as per https://learn.microsoft.com/en-us/azure/virtual-machines/deprecated-images
| Action | Before enforcement date | After enforcement date |
|---|---|---|
| Existing VMs | Continue running normally | Continue running normally |
| Existing VMs | Continue running normally | Continue running normally |
| Existing virtual machine scale set instances | Continue running normally | Continue running normally |
| New VM deployments | Allowed with deprecation warnings | Blocked |
| New virtual machine scale set deployments | Allowed with deprecation warnings | Blocked |
| Virtual machine scale set scale-out | Allowed | Blocked |
| VM redeployment | Allowed | Blocked |
If the above response helps answer your question, remember to "Accept Answer" so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.
hth
Marcin