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||1 - 3||50|
|Dedicated cores per Batch account||10 - 100||N/A1|
|Low-priority cores per Batch account||10 - 100||N/A2|
|Active jobs and job schedules3 per Batch account||100 - 300||25004|
|Pools per Batch account||20 - 100||500|
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.
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.
Cores quotas in user subscription mode
If you created a Batch account with pool allocation mode set to user subscription, quotas are applied differently. In this mode, Batch VMs and other resources are created directly in your subscription when a pool is created. The Azure Batch cores quotas do 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|
|Maximum task lifetime||7 days1|
|Compute nodes in inter-node communication enabled pool||100|
1 The maximum lifetime of a task, from when it is added to the job to when it completes, is 7 days. Completed tasks persist indefinitely; data for tasks not completed within the maximum lifetime is not accessible.
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.
Related quotas for VM pools
Batch pools in the Virtual Machine Configuration deployed in an Azure virtual network automatically allocate additional Azure networking resources. The following resources are needed for each 50 pool nodes in a virtual network:
These resources are allocated in the subscription that contains the virtual network supplied when creating the Batch pool. These resources are limited by the subscription's resource quotas. If you plan large pool deployments in a virtual network, check the subscription's quotas for these resources. If needed, request an increase in the Azure portal by selecting Help + support.