Azure Batch typically follows standard end of life timelines set by publishers for supported images from the Azure Marketplace. Ubuntu 20.04 LTS is reaching the end of standard support life. Batch pools with Ubuntu 20.04 LTS VM images and the Batch node agent SKU batch.node.ubuntu 20.04 will no longer be supported in Batch after 23 April 2025.
The following Marketplace images will no longer be supported in Batch after 23 April 2025:
-
Canonical: 0001-com-ubuntu-server-focal (SKU(s): 20_04-lts, 20_04-lts-gen2)
-
microsoft-dsvm: ubuntu-2004 (SKU(s): 2004, 2004-gen2), ubuntu-hpc (SKU(s): 2004)
-
microsoft-azure-batch: ubuntu-server-container (SKU(s): 20-04-lts), ubuntu-server-container-rdma (SKU(s): 20-04-lts)
-
xilinx: xilinx_alveo_u250_deployment_vm_ubuntu2004_062421 (SKU(s): xilinx_alveo_u250_deployment_vm_ubuntu_2004_062421)
Additionally, any Batch pool using a custom image, for example, through the Azure Compute Image Gallery, based on Ubuntu 20.04 LTS will no longer be supported in Batch after 23 April 2025.
From now until 23 April 2025, you can continue to use these images and the batch.node.ubuntu 20.04 node agent SKU without disruption. After that date, no new Batch pools can be created with the batch.node.ubuntu 20.04 node agent SKU referencing relevant Marketplace and Compute Image Gallery images. In addition, existing pools with applicable configurations may experience failure in scale out operations and may be subject to forced resize to zero nodes.
As a reminder, we recommend reviewing the Batch best practices guide which outlines support expectations, recommendations on Batch pool image freshness, and how to query for Batch image support end of life dates.
Required action
Stop using Ubuntu 20.04 LTS based VM images for Batch pools before 23 April 2025. Please migrate your Batch pools to a VM image based on Ubuntu 22.04 or later, or the microsoft-dsvm ubuntu-hpc 2204 (or later) image for container and/or workloads requiring Infiniband/GPU support. You can also migrate to any other Batch-supported VM image, if amenable for your workload. Existing Batch pools cannot be updated with a new VM image reference and creating a new Batch pool is required for migration.
Help and support
If you have questions, get answers from community experts in Microsoft Q&A. If you have a support plan and you need technical help, create a support request.
