Batch custom image pools using VHD or managed images will be retired on 31 March 2026
Microsoft retired this Batch feature in April 2026.
Retirement1 version
Facts
- Microsoft id
batch-custom-image-pools-using-vhd-or-managed-images-will-be-retired-on-31-march-2024- Products
- Batch
- Update type
- Features, Retirements
- Product categories
- Compute
- Retirement
- April 2026
- Status pages
- Azure Batch status
- First captured by us
- (from our first import of this list)
- Microsoft last modified
- Source
- Azure Updates · open the original at Microsoft
Microsoft says
To align with modern Azure offerings and improve reliability and scale, Azure Batch will retire support for custom image pools using VHD blobs in Azure…
What Microsoft changed
One version so far. If Microsoft edits it, each change shows here with what was removed and added.
First version we captured ·
The text as we first saw it
Seen by us · Microsoft's timestamp · Microsoft's page
Related changes
Other changes for Azure Batch
- Announcing General Availability of Azure Monitor Metrics Data Plane API · Launched
- Azure Batch vCPU quota checks are being updated · Launched
- Batch Service in select regions will be retired on 31 March 2026
- Azure Private Link for Azure Batch is now generally available in select regions · Launched
- Azure Batch Certificates will be retired on 29 February 2024
- Azure Batch classic compute node communication model will be retired on 31 March 2026
- Azure Batch CLI extensions will be retired on 30 September 2024
- Azure Batch ‘CloudServiceConfiguration’ pools will be retired on 29 February 2024