Maintained with ☕️ by
IcePanel logo

General availability: New Azure Batch capabilities



Use Azure Batch to run large-scale parallel and high-performance computing (HPC) batch jobs in Azure. The following new Batch features are now available. **Pool Managed Identities** User-assigned managed identities [can be associated with Batch pools]( so the pool nodes can then use the identity to access Azure resources. The managed identity can also be used to access Azure resources specifically supported by Batch, such as resource files. **Pool Virtual Machine Extensions** Specific [virtual machine extensions]( can be [associated with Batch pools](, with the specified extensions being installed on each pool node. **Pool Availability Zone Support** [A pool can now be configured]( to allocate pool nodes across all the availability zones where the pool VM size is available and in a region that supports availability zones. **Pool Node Ephemeral OS Disk Support** Some VM series support [ephemeral OS disk]( where the OS disk is created on local VM storage instead of remote Azure Storage. For supported VM sizes, [Batch pools can now specify ephemeral OS disk is used]( for the pool nodes. **Exact Marketplace VM Image Version** The specific version of the platform image or marketplace image used to create the node [is now available for a pool]( **List Supported VM Sizes** It is now possible to list (via API, CLI and Powershell) the VM sizes supported by Batch for both [Cloud Service]( and [Virtual Machine]( pools. **Account Authentication Control** The service API authentication mechanism for a Batch account can be restricted to only Azure Active Directory using the ‘[allowedAuthenticationModes](’ property; API calls using access key authentication will be rejected. **Application Limit** The maximum number of applications for a Batch account has been increased from 20 to 200. For information about all Batch updates see the [service REST API]( and [management REST API versioning]( documentation. * Batch * Features * [ Batch](