Update Batch articles with retirements

- Improve scores on some docs

Author: alfpark

articles/batch/TOC.yml

@@ -175,7 +175,7 @@
     - name: Configure access to compute nodes
       displayName: rdp, ssh, network, remote
       href: pool-endpoint-configuration.md
-    - name: Create a pool with the Shared Image Gallery
+    - name: Create a pool with Azure Compute Gallery
       displayName: managed image, sig
       href: batch-sig-images.md
     - name: Create a pool with a managed image resource

articles/batch/batch-automatic-scaling.md

@@ -2,16 +2,18 @@
 title: Use a managed image to create a custom image pool
 description: Create a Batch custom image pool from a managed image to provision compute nodes with the software and data for your application.
 ms.topic: conceptual
-ms.date: 11/18/2020
+ms.date: 04/06/2023
 ms.devlang: csharp
 ---
 
 # Use a managed image to create a custom image pool
 
 To create a custom image pool for your Batch pool's virtual machines (VMs), you can use a managed image to create an [Azure Compute Gallery image](batch-sig-images.md). Using just a managed image is also supported, but only for API versions up to and including 2019-08-01.
 
-> [!IMPORTANT]
-> In most cases, you should create custom images using the Azure Compute Gallery. By using the Azure Compute Gallery, you can provision pools faster, scale larger quantities of VMs, and have improved reliability when provisioning VMs. To learn more, see [Use the Azure Compute Gallery to create a custom pool](batch-sig-images.md).
+> [!WARNING]
+> Support for creating a Batch pool using a managed image is being retired after **31 March 2026**. Please migrate to
+> hosting custom images in Azure Compute Gallery to use for creating a [custom image pool in Batch](batch-sig-images.md).
+> For more information, see the [migration guide](batch-custom-image-pools-to-azure-compute-gallery-migration-guide.md).
 
 This topic explains how to create a custom image pool using only a managed image.
 
@@ -36,17 +38,17 @@ To scale Batch pools reliably with a managed image, we recommend creating the ma
 
 ### Prepare a VM
 
-If you are creating a new VM for the image, use a first party Azure Marketplace image supported by Batch as the base image for your managed image. Only first party images can be used as a base image. To get a full list of Azure Marketplace image references supported by Azure Batch, see the [List node agent SKUs](/java/api/com.microsoft.azure.batch.protocol.accounts.listnodeagentskus) operation.
+If you're creating a new VM for the image, use a first party Azure Marketplace image supported by Batch as the base image for your managed image. Only first party images can be used as a base image. To get a full list of Azure Marketplace image references supported by Azure Batch, see the [List node agent SKUs](/java/api/com.microsoft.azure.batch.protocol.accounts.listnodeagentskus) operation.
 
 > [!NOTE]
 > You can't use a third-party image that has additional license and purchase terms as your base image. For information about these Marketplace images, see the guidance for [Linux](../virtual-machines/linux/cli-ps-findimage.md#check-the-purchase-plan-information) or [Windows](../virtual-machines/windows/cli-ps-findimage.md#view-purchase-plan-properties)VMs.
 
 - Ensure the VM is created with a managed disk. This is the default storage setting when you create a VM.
-- Do not install Azure extensions, such as the Custom Script extension, on the VM. If the image contains a pre-installed extension, Azure may encounter problems when deploying the Batch pool.
+- Don't install Azure extensions, such as the Custom Script extension, on the VM. If the image contains a preinstalled extension, Azure may encounter problems when deploying the Batch pool.
 - When using attached data disks, you need to mount and format the disks from within a VM to use them.
 - Ensure that the base OS image you provide uses the default temp drive. The Batch node agent currently expects the default temp drive.
-- Ensure that the OS disk is not encrypted.
-- Once the VM is running, connect to it via RDP (for Windows) or SSH (for Linux). Install any necessary software or copy desired data.  
+- Ensure that the OS disk isn't encrypted.
+- Once the VM is running, connect to it via RDP (for Windows) or SSH (for Linux). Install any necessary software or copy desired data.
 
 ### Create a VM snapshot
 
@@ -123,7 +125,7 @@ Request Body
 
 ## Considerations for large pools
 
-If you plan to create a pool with hundreds of VMs or more using a custom image, it is important to follow the preceding guidance to use an image created from a VM snapshot.
+If you plan to create a pool with hundreds of VMs or more using a custom image, it's important to follow the preceding guidance to use an image created from a VM snapshot.
 
 Also note the following considerations:
 
@@ -136,16 +138,17 @@ Also note the following considerations:
 - **Resize timeout** - If your pool contains a fixed number of nodes (doesn't autoscale), increase the resizeTimeout property of the pool to a value such as 20-30 minutes. If your pool doesn't reach its target size within the timeout period, perform another [resize operation](/rest/api/batchservice/pool/resize).
 
   If you plan a pool with more than 300 compute nodes, you might need to resize the pool multiple times to reach the target size.
-  
-By using the [Azure Compute Gallery](batch-sig-images.md), you can create larger pools with your customized images along with more Shared Image replicas. Using Shared Images, the time it takes for the pool to reach the steady state is up to 25% faster, and the VM idle latency is up to 30% shorter.
+
+By using the [Azure Compute Gallery](batch-sig-images.md), you can create larger pools with your customized images along
+with more Shared Image replicas along with improved performance benefits such as decreased time for nodes to become ready.
 
 ## Considerations for using Packer
 
-Creating a managed image resource directly with Packer can only be done with user subscription mode Batch accounts. For Batch service mode accounts, you need to create a VHD first, then import the VHD to a managed image resource. Depending on your pool allocation mode (user subscription, or Batch service), your steps to create a managed image resource will vary.
+Creating a managed image resource directly with Packer can only be done with user subscription mode Batch accounts. For Batch service mode accounts, you need to create a VHD first, then import the VHD to a managed image resource. Depending on your pool allocation mode (user subscription, or Batch service), your steps to create a managed image resource varies.
 
 Ensure that the resource used to create the managed image exists for the lifetimes of any pool referencing the custom image. Failure to do so can result in pool allocation failures and/or resize failures.
 
-If the image or the underlying resource is removed, you may get an error similar to: `There was an error encountered while performing the last resize on the pool. Please try resizing the pool again. Code: AllocationFailed`. If you get this error, ensure that the underlying resource has not been removed.
+If the image or the underlying resource is removed, you may get an error similar to: `There was an error encountered while performing the last resize on the pool. Please try resizing the pool again. Code: AllocationFailed`. If you get this error, ensure that the underlying resource hasn't been removed.
 
 For more information on using Packer to create a VM, see [Build a Linux image with Packer](../virtual-machines/linux/build-image-with-packer.md) or [Build a Windows image with Packer](../virtual-machines/windows/build-image-with-packer.md).
 

articles/batch/batch-custom-images.md

@@ -13,7 +13,7 @@ Where applicable, pay-for-use licensing is available for the pre-installed rende
 
 Some applications only support Windows, but most are supported on both Windows and Linux.
 
-> [!IMPORTANT]
+> [!WARNING]
 > The rendering VM images and pay-for-use licensing have been [deprecated and will be retired on February 29, 2024](https://azure.microsoft.com/updates/azure-batch-rendering-vm-images-licensing-will-be-retired-on-29-february-2024/). To use Batch for rendering, [a custom VM image and standard application licensing should be used.](batch-rendering-functionality.md#batch-pools-using-custom-vm-images-and-standard-application-licensing)
 
 ## Applications on latest CentOS 7 rendering image

articles/batch/batch-rendering-applications.md

@@ -21,7 +21,7 @@ Most rendering applications will require licenses obtained from a license server
 
 ## Batch pools using rendering VM images
 
-> [!IMPORTANT]
+> [!WARNING]
 > The rendering VM images and pay-for-use licensing have been [deprecated and will be retired on February 29, 2024](https://azure.microsoft.com/updates/azure-batch-rendering-vm-images-licensing-will-be-retired-on-29-february-2024/). To use Batch for rendering, [a custom VM image and standard application licensing should be used.](batch-rendering-functionality.md#batch-pools-using-custom-vm-images-and-standard-application-licensing)
 
 ### Rendering application installation

articles/batch/batch-rendering-functionality.md

@@ -7,7 +7,7 @@ ms.topic: how-to
 
 # Using Azure Batch rendering
 
-> [!IMPORTANT]
+> [!WARNING]
 > The rendering VM images and pay-for-use licensing have been [deprecated and will be retired on February 29, 2024](https://azure.microsoft.com/updates/azure-batch-rendering-vm-images-licensing-will-be-retired-on-29-february-2024/). To use Batch for rendering, [a custom VM image and standard application licensing should be used.](batch-rendering-functionality.md#batch-pools-using-custom-vm-images-and-standard-application-licensing)
 
 There are several ways to use Azure Batch rendering:

articles/batch/batch-rendering-using.md

@@ -2,7 +2,7 @@
 title: Run workloads on cost-effective Spot VMs
 description: Learn how to provision Spot VMs to reduce the cost of Azure Batch workloads.
 ms.topic: how-to
-ms.date: 03/15/2023
+ms.date: 04/06/2023
 ms.custom: seodec18
 ---
 
@@ -25,6 +25,10 @@ Batch offers two types of low-cost pre-emptible VMs:
 
 The type of node you get depends on your Batch account's pool allocation mode, which is settable during account creation. Batch accounts that use the **user subscription** pool allocation mode always get Spot VMs. Batch accounts that use the **Batch managed** pool allocation mode always get low-priority VMs.
 
+> [!WARNING]
+> Support for low-priority VMs will be retired after **30 September 2025**. Please
+> [migrate to using Spot VMs in Batch](low-priority-vms-retirement-migration-guide.md) before then.
+
 Azure Spot VMs and Batch low-priority VMs are similar but have a few differences in behavior.
 
 | | Spot VMs | Low-priority VMs |
@@ -42,7 +46,7 @@ Azure Spot VMs and Batch low-priority VMs are similar but have a few differences
 
 Azure Batch provides several capabilities that make it easy to consume and benefit from Spot VMs:
 
-- Batch pools can contain both dedicated VMs and Spot VMs. The number of each type of VM can be specified when a pool is created, or changed at any time for an existing pool, using the explicit resize operation or using auto-scale. Job and task submission can remain unchanged, regardless of the VM types in the pool. You can also configure a pool to completely use Spot VMs to run jobs as cheaply as possible, but spin up dedicated VMs if the capacity drops below a minimum threshold, to keep jobs running.
+- Batch pools can contain both dedicated VMs and Spot VMs. The number of each type of VM can be specified when a pool is created, or changed at any time for an existing pool, using the explicit resize operation or using autoscale. Job and task submission can remain unchanged, regardless of the VM types in the pool. You can also configure a pool to completely use Spot VMs to run jobs as cheaply as possible, but spin up dedicated VMs if the capacity drops below a minimum threshold, to keep jobs running.
 - Batch pools automatically seek the target number of Spot VMs. If VMs are preempted or unavailable, Batch attempts to replace the lost capacity and return to the target.
 - When tasks are interrupted, Batch detects and automatically requeues tasks to run again.
 - Spot VMs have a separate vCPU quota that differs from the one for dedicated VMs. The quota for Spot VMs is higher than the quota for dedicated VMs, because Spot VMs cost less. For more information, see [Batch service quotas and limits](batch-quota-limit.md#resource-quotas).
@@ -162,7 +166,7 @@ To view these metrics in the Azure portal
 - Spot VMs in Batch don't support setting a max price and don't support price-based evictions. They can only be evicted for capacity reasons.
 - Spot VMs are only available for Virtual Machine Configuration pools and not for Cloud Service Configuration pools, which are [deprecated](https://azure.microsoft.com/updates/azure-batch-cloudserviceconfiguration-pools-will-be-retired-on-29-february-2024/).
 - Spot VMs aren't available for some clouds, VM sizes, and subscription offer types. See more about [Spot limitations](../virtual-machines/spot-vms.md#limitations).
-- Currently, [Ephemeral OS disks](create-pool-ephemeral-os-disk.md) are not supported with Spot VMs due to the service managed
+- Currently, [Ephemeral OS disks](create-pool-ephemeral-os-disk.md) aren't supported with Spot VMs due to the service managed
 eviction policy of Stop-Deallocate.
 
 ## Next steps