Skip to content

Latest commit

 

History

History
33 lines (28 loc) · 1.88 KB

File metadata and controls

33 lines (28 loc) · 1.88 KB
title include file
description include file
services batch
ms.service azure-batch
ms.topic include
ms.date 01/05/2026
ms.custom include file
Resource Default limit Maximum limit
Azure Batch accounts per region per subscription 1-3 50
Dedicated cores per Batch account 0-9001 Contact support
Low-priority cores per Batch account 0-1001 Contact support
Active jobs and job schedules per Batch account (completed jobs have no limit) 100-300 1,0002
Pools per Batch account 0-1001 5002
Private endpoint connections per Batch account 100 100

1 For capacity management purposes, the default quotas for new Batch accounts in some regions and for some subscription types have been reduced from the above range of values. In some cases, these limits have been reduced to zero. When you create a new Batch account, check your quotas and request an appropriate core or service quota increase, if necessary. Alternatively, consider reusing Batch accounts that already have sufficient quota or user subscription pool allocation Batch accounts to maintain core and VM family quota across all Batch accounts on the subscription. Service quotas like active jobs or pools apply to each distinct Batch account even for user subscription pool allocation Batch accounts.

2 To request an increase beyond this limit, contact Azure Support.

Note

Default limits vary depending on the type of subscription you use to create a Batch account. Cores quotas shown are for Batch accounts in Batch service mode. View the quotas in your Batch account.