Batch service quotas and limits
As with other Azure services, there are limits on certain resources associated with the Batch service. Many of these limits are default quotas applied by Azure at the subscription or account level. This article discusses those defaults, and how you can request quota increases.
Keep these quotas in mind as you design and scale up your Batch workloads. For example, if your pool doesn't reach the target number of compute nodes you specified, you might have reached the core quota limit for your Batch account.
You can run multiple Batch workloads in a single Batch account, or distribute your workloads among Batch accounts that are in the same subscription, but in different Azure regions.
If you plan to run production workloads in Batch, you may need to increase one or more of the quotas above the default. If you want to raise a quota, you can open an online customer support request at no charge.
A quota is a credit limit, not a capacity guarantee. If you have large-scale capacity needs, please contact Azure support.
|Resource||Default Limit||Maximum Limit|
|Batch accounts per region per subscription||3||50|
|Dedicated cores per Batch account||20||N/A1|
|Low-priority cores per Batch account||20||N/A2|
|Active jobs and job schedules3 per Batch account||20||50004|
|Pools per Batch account||20||2500|
1 The number of dedicated cores per Batch account can be increased, but the maximum number is unspecified. Contact Azure support to discuss increase options.
2 The number of low-priority cores per Batch account can be increased, but the maximum number is unspecified. Contact Azure support to discuss increase options.
3 Completed jobs and job schedules are not limited.
4 Contact Azure support if you want to request an increase beyond this limit.
Quotas in user subscription mode
If you used an earlier version of the Batch API to create a Batch account with pool allocation mode set to user subscription, quotas are applied differently. In this mode, which is no longer recommended, Batch VMs and other resources are created directly in your subscription when a pool is created. The Azure Batch cores quota does not apply to an account created in this mode. Instead, the quotas in your subscription for regional compute cores and other resources are applied. Learn more about these quotas in Azure subscription and service limits, quotas, and constraints.
|Concurrent tasks per compute node||4 x number of node cores|
|Applications per Batch account||20|
|Application packages per application||40|
|Application package size (each)||Approx. 195GB1|
|Maximum start task size||32768 characters2|
1 Azure Storage limit for maximum block blob size
2 Includes resource files and environment variables
View Batch quotas
View your Batch account quotas in the Azure portal.
- Select Batch accounts in the portal, then select the Batch account you're interested in.
- Select Quotas on the Batch account's menu.
View the quotas currently applied to the Batch account
Increase a quota
Follow these steps to request a quota increase for your Batch account or your subscription using the Azure portal. The type of quota increase depends on the pool allocation mode of your Batch account.
Increase a Batch cores quota
- Select the Help + support tile on your portal dashboard, or the question mark (?) in the upper-right corner of the portal.
- Select New support request > Basics.
a. Issue Type > Quota
b. Select your subscription.
c. Quota type > Batch
d. Support plan > Quota support - Included
a. Select a Severity according to your business impact.
b. In Details, specify each quota you want to change, the Batch account name, and the new limit.
In Contact information:
a. Select a Preferred contact method.
b. Verify and enter the required contact details.
Click Create to submit the support request.
Once you've submitted your support request, Azure support will contact you. Note that completing the request can take up to 2 business days.