MicrosoftDocs
Clarity needed around paid custom images deprecation
This section is tough to interpret. Will my VMs that I created from a paid custom image in my compute gallery stop working after the deprecation date in the marketplace? Need clarity here, please.
""" We recommend that you create custom images from free Marketplace images, that don't have Plan Info, that are scheduled for deprecation. For Paid Marketplace images, we suggest you create custom images from the latest version of the image. Workloads running on custom images created from a deprecated paid image will no longer work after the paid image is deprecated. """
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.
- ID: 1ae5bf9f-47d8-ad01-af78-ddd78604301f
- Version Independent ID: 7979d401-a6f0-6cfd-1497-300a6a1d988e
- Content: Deprecated Azure Marketplace images - Azure Virtual Machines
- Content Source: articles/virtual-machines/deprecated-images.yml
- Service: virtual-machines
- Sub-service: imaging
- GitHub Login: @ju-shim
- Microsoft Alias: jushiman
@stevenoneill Thanks for your feedback! We will investigate and update as appropriate.
HI @stevenoneill If you have created custom images from paid Marketplace images that are scheduled for deprecation, we recommend that you create new custom images from the latest version of the image before the deprecation date. If you do not create new custom images, workloads running on custom images created from a deprecated paid image will no longer work after the paid image is deprecated.
In other words, if you have created custom images from a paid Marketplace image that is scheduled for deprecation, you should create new custom images from the latest version of the image before the deprecation date to ensure that your workloads continue to function properly. If you do not create new custom images, your workloads may stop working after the deprecation date.
I hope this helps clarify the statement. Let me know if you have any other questions or concerns.
Guess it depends on the workload, right? For VMSS, you can swap out the the image id to an updated image id and have replacement VMs created.
My main focus in this inquiry is on just plain old VMs. Our observation is: if a VM is already running, and the underlying Paid marketplace image (has purchasePlan defined) is removed, the VM will continue to run. You can DeAllocate and Start the VM, no issues.
However, no new VMs can be spun up that reference the marketplace image's purchasePlan (the 'plan' object on a VM, Disk, or snapshot, if i recall).
For example, if I needed to restore a VM from an OsDisk snapshot, I can create a new OsDisk from the snapshot, but I am unable to create a VM with that OsDisk since it references a non-existing marketplace image.
As a result, it appears that when a Marketplace image is removed, there is no way to restore/recover plain old VMs. If that is the correct interpretation, then that is the clarity that would be helpful to more explicity call out in the docs.
Is that accurate and make sense @ManoharLakkoju-MSFT ?
@stevenoneill I'm going to assign this to the document author so they can take a look at it accordingly
@ju-shim Can you please check and add your comments on this doc update request as applicable.
@ManoharLakkoju-MSFT @stevenoneill public documentation has been updated https://learn.microsoft.com/en-us/azure/virtual-machines/deprecated-images#what-happens-when-a-paid-marketplace-image-with-the-purchase-plan-information-is-deprecated. Let me know if this addresses your question and if the issue can be closed,
@ebolton-cyber thank you. That makes it clear that there is no path forward for VMs, only VMSSs.
Can one item be added to the FAQ about how to ensure the correct email is configured for notifications about the alerts? That's only gap I am still seeing.
@stevenoneill , thanks for the feedback, I would look into this and get it added on the documentation page