formatting'

Author: cynthn

articles/virtual-machines/deprecated-images.yml

@@ -31,7 +31,9 @@ sections:
       - question: I received an email that my workloads are running on images that are scheduled for deprecation. What does this mean and does deprecation impact my existing workloads? 
         answer: |
           Before the scheduled deprecation date, you can continue to deploy new VM or scale set instances up until the deprecation date.
+          
           After the scheduled deprecation date, you won't be able to deploy new instances using the affected images. If the plan is scheduled for deprecation, all image versions within the plan will no longer be available and if the entire offer is scheduled for deprecation, all plans within the offer will no longer be available following deprecation.
+          
           - Active VM instances won't be impacted.  
           - New VM instances cannot be created from any of the impacted images.
           - Existing virtual machine scale sets deployments cannot be scaled out if configured with any of the impacted images. When a plan or offer is being deprecated, all existing scale sets deployments pinned to any image within the plan or offer respectively cannot be scaled out.
@@ -49,10 +51,10 @@ sections:
           If you are notified that an image is deprecated on only the Offer or plan (SKU) level, you can search for all virtual machines from the top search bar on the Azure Portal and edit the columns as seen below to include Publisher, Offer, Plan  as below. This will not give the version information, only up to the Plan information.
            
                         
-          If you are notified that an image is deprecated on the offer, plan (SKU) or version level:
-          Using Azure Resource Graph Explorer:   
-          You can use Azure Resource Graph Explorer on the Azure portal to find the specific version for images in your subscription that your VM or scale set is running on.
+          If you are notified that an image is deprecated on the offer, plan (SKU) or version level, you can use Azure Resource Graph Explorer on the Azure portal to find the specific version for images in your subscription that your VM or scale set is running on.
+          
           Run the queries below in the Azure Resource Graph explorer query window and uncomment the optional filters (delete the “//” to uncomment a line) to the Offer, Plan (SKU) or version level you are looking for.
+          
           To find the details of the image versions that are being used by VMs: 
           
           ```
@@ -117,7 +119,7 @@ sections:
           az vm list --query "[?storageProfile.imageReference.version=='14393.4402.2105052108'].{VM:id, imageOffer:storageProfile.imageReference.offer, imagePublisher:StorageProfile.imageReference.publisher, imageSku: storageProfile.imageReference.sku, imageVersion:storageProfile.imageReference.version}"
           ```
           
-          Note: When an image is deprecated, there is no impact on existing VMs and no action is required. You can choose to migrate your workloads to a new image if you have a specific concern.
+          When an image is deprecated, there is no impact on existing VMs and no action is required. You can choose to migrate your workloads to a new image if you have a specific concern.
           
       - question: How do I migrate my workloads to another image?
         answer: |
@@ -128,78 +130,83 @@ sections:
           - Modify the VM or scale set deployment you want to point to the custom image.
           - Here is how to create a custom image by capturing a VM and sharing in to Azure Compute Gallery (formerly known as Shared Image Gallery (SIG): Capture an image of a VM using the portal - Azure Virtual Machines | Microsoft Docs
           
-          Note: We recommend that you create custom images from Free Marketplace images (images that do not have Plan Info) that are scheduled for deprecation or already deprecated. 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.
+          We recommend that you create custom images from Free Marketplace images (images that do not have Plan Info) that are scheduled for deprecation or already deprecated. 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.
           
-          - You want to migrate to another Offer/Plan/Version:
+          **You want to migrate to another offer/plan/version:**
           First search for other offers, plans or versions from the same publisher with the following commands (Replace all highlighted values as needed):
           
-          - To migrate to another Offer:
+              **To migrate to another offer:**
           
-          PowerShell:
+                  PowerShell:
           
-          ```
-          Get-AzVMImage -Location "west europe" -PublisherName “MicrosoftWindowsServer” 
-          ```
+                  ```
+                  Get-AzVMImage -Location "west europe" -PublisherName “MicrosoftWindowsServer” 
+                  ```
           
-          Azure CLI:
+                  Azure CLI:
           
-          ```
-          az vm image list --location "west europe" --publisher "MicrosoftWindowsServer" 
-          ```
+                  ```
+                  az vm image list --location "west europe" --publisher "MicrosoftWindowsServer" 
+                  ```
           
-          - To migrate to another Plan: Search for other plans under the same offer and then migrate to that plan.
+              **To migrate to another Plan:** 
+                  Search for other plans under the same offer and then migrate to that plan.
           
-          PowerShell:
+                  PowerShell:
           
-          ```
-          Get-AzVMImage -Location "west europe" -PublisherName “MicrosoftWindowsServer” -Offer “WindowsServer”
-          ``` 
+                  ```
+                  Get-AzVMImage -Location "west europe" -PublisherName “MicrosoftWindowsServer” -Offer “WindowsServer”
+                  ``` 
           
-          Azure CLI:
+                  Azure CLI:
           
-          ```
-          az vm image list --location "west europe" --publisher "MicrosoftWindowsServer" --offer "WindowsServer" 
-          ```
+                  ```
+                  az vm image list --location "west europe" --publisher "MicrosoftWindowsServer" --offer "WindowsServer" 
+                  ```
           
-          - To migrate to another version: Search for another version (we suggest migrating to the latest version)  
+              **To migrate to another version:** 
+                  Search for another version (we suggest migrating to the latest version)  
           
-          PowerShell:
+                  PowerShell:
           
-          ```
-          Get-AzVMImage -Location "west europe" -PublisherName “MicrosoftWindowsServer” -Offer “WindowsServer” -Skus "2019-Datacenter-with-Containers"
-          ```
+                  ```
+                  Get-AzVMImage -Location "west europe" -PublisherName “MicrosoftWindowsServer” -Offer “WindowsServer” -Skus "2019-Datacenter-with-Containers"
+                  ```
           
-          Azure CLI:
+                  Azure CLI:
           
-          ```
-          az vm image list --location "west europe" --publisher "MicrosoftWindowsServer" --offer "WindowsServer" --sku "2019-Datacenter-with-Containers" --all"
-          ```
+                  ```
+                  az vm image list --location "west europe" --publisher "MicrosoftWindowsServer" --offer "WindowsServer" --sku "2019-Datacenter-with-Containers" --all"
+                  ```
           
         
           You need to verify that your workloads are supported and will run properly on the new image before migrating your workloads to the new image.
           
-          Scale sets, in general, support [image reference replacement](../virtual-machine-scale-sets/virtual-machine-scale-sets-upgrade-scale-set#os-updates.md) but VMs do not.
+          Scale sets, in general, support [image reference replacement](../virtual-machine-scale-sets/virtual-machine-scale-sets-upgrade-scale-set.md#os-updates) but VMs do not.
           
           
           
-          Migrating scale set workloads to newer image with minimal downtime:  
+          **Migrating scale set workloads to newer image with minimal downtime**
           
           Scale set, suggestions for updating the version should include:
-          1.	To avoid downtime, ensure the upgrade policy is set to manual or rolling. 
-          a.	If set to manual, existing instances won’t be reimaged until it’s manually upgraded.
-          b.	If set to rolling, existing instances will be automatically upgraded and reimaged by batch. 	
-          2.	Update image reference using steps in Modify an Azure virtual machine scale set: Modify an Azure virtual machine scale set - Azure Virtual Machine Scale Sets | Microsoft Docs
-          3.	Ensure that all existing instances are upgraded and on the latest model. You can also scale out and migrate workload to the new instances then delete the old instances, instead of upgrading the existing instances. 
-          4.	Once the existing instances are all upgraded to the new image, change the upgrade policy back to what it was if needed. 
+          - To avoid downtime, ensure the upgrade policy is set to manual or rolling. 
+               If set to manual, existing instances won’t be reimaged until it’s manually upgraded.
+               If set to rolling, existing instances will be automatically upgraded and reimaged by batch. 	
+          - Update image reference using steps in Modify an Azure virtual machine scale set: Modify an Azure virtual machine scale set - Azure Virtual Machine Scale Sets | Microsoft Docs
+          - Ensure that all existing instances are upgraded and on the latest model. You can also scale out and migrate workload to the new instances then delete the old instances, instead of upgrading the existing instances. 
+          - Once the existing instances are all upgraded to the new image, change the upgrade policy back to what it was if needed. 
            
            
           
       - question: Are all image versions lower than the indicated version also deprecated? 
         answer: |
           Generally, yes. However, it is recommended to  confirm against the list of valid versions in a Plan using Virtual Machine Images - List - REST API (Azure Compute) | Microsoft Docs 
            
-          How can I check if a specific image is deprecated or scheduled for deprecation:  
+      - question: How can I check if a specific image is deprecated or scheduled for deprecation?
+        answer: |
           You can check if an image is deprecated or scheduled for deprecation using the [REST API](/rest/api/compute/virtual-machine-images/get?tabs=HTTP). 
+          
+          
           If the image is deprecated, you will get a **VM Image is Deprecated** response. If the image is scheduled for deprecation, the response would show the date of the scheduled deprecation.