Skip to content

Commit 94feefe

Browse files
author
Edewe Bolton
committed
Updated the deprecated Images doc to include information about impacts of using deprecated images with Plan Information
1 parent 3c0ed8d commit 94feefe

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/virtual-machines/deprecated-images.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ metadata:
77
ms.topic: faq
88
ms.subservice: imaging
99
ms.custom: devx-track-azurepowershell, devx-track-azurecli
10-
ms.date: 09/27/2022
10+
ms.date: 06/26/2024
1111
ms.author: jushiman
1212
ms.reviewer: edewe
1313
title: Deprecated images FAQ
@@ -124,7 +124,7 @@ sections:
124124
125125
If you want to keep using an image that is scheduled for deprecation, generalize the VM, deallocate the VM, then create a custom image for your VM or scale set. Then change the VM or scale set deployment to point to the custom image. For more information, see [Capture an image of a VM in the portal](capture-image-portal.md).
126126
127-
**Note: If you are using a deprecated paid Marketplace image that has the Purchase Plan Information defined (the 'plan' object on the Image), when this image gets deprecated you cannot create new Virtual Machines workloads or perform Azure Site Recovery (ASR) or Backup operations with this image due to the missing Plan Information.**
127+
**Note**: If you are using a deprecated paid Marketplace image that has the Purchase Plan Information defined (the 'plan' object on the Image), when this image gets deprecated you cannot create new Virtual Machines workloads or perform Azure Site Recovery (ASR) or Backup operations with this image due to the missing Plan Information.
128128
129129
**You want to migrate to another offer/plan/version:**
130130

0 commit comments

Comments
 (0)