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 are designing and scaling up your Batch workloads. For example, if your pool isn't reaching the target number of compute nodes you've specified, you might have reached the core quota limit for your Batch account, or a regional VM cores quota for your subscription.
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 (Batch service mode)1||20||N/A2|
|Low-priority cores per Batch account (Batch service mode)3||50||N/A4|
|Active jobs and job schedules5 per Batch account||20||50006|
|Pools per Batch account||20||2500|
1 Dedicated core quotas shown are only for accounts with pool allocation mode set to Batch service. For accounts with the mode set to user subscription, core quotas are based on the VM cores quota at a regional level or per VM family in your subscription.
2 The number of dedicated cores per Batch account can be increased, but the maximum number is unspecified. Contact Azure support to discuss increase options.
3 Low-priority core quotas shown are only for accounts with pool allocation mode set to Batch service. Low-priority cores are not available for accounts with pool allocation mode set to user subscription.
4 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.
5 Completed jobs and job schedules are not limited.
6 Contact Azure support if you want to request an increase beyond this limit.
Quotas in user subscription mode
For a Batch account with pool allocation mode set to user subscription, Batch VMs and other resources, such as storage accounts, 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.
When planning resource usage for an account created in user subscription mode, note the following Batch resources (in addition to compute cores) are required for every 40 Linux VMs, or 20 Windows VMs:
|One storage account||Storage Accounts||Microsoft.Storage|
|One public IP address||Public IP Addresses||Microsoft.Network|
|One virtual network||Virtual Networks||Microsoft.Network|
|One network security group||Network Security Groups||Microsoft.Network|
|One virtual machine scale set||Virtual Machine Scale Sets||Microsoft.Compute|
|One load balancer||Load Balancers||Microsoft.Network|
The cores quota at a regional level or per VM family should be set according to the VM size required for your Batch pool or pools:
|Total Regional Cores||Microsoft.Compute|
|… Family Cores||Microsoft.Compute|
|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 Properties on the Batch account's menu blade.
The Properties blade displays the quotas currently applied to the Batch account
For a Batch account created in user subscription mode, view the related subscription quotas in the Azure Portal.
Select Subscriptions, and select the subscription you are using for the Batch account.
On the Subscription blade, select Usage + quotas.
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
If your Batch account was created in Batch service mode, follow these steps to request a Batch cores quota increase:
- 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.
On the Basics blade:
a. Issue Type > Quota
b. Select your subscription.
c. Quota type > Batch
d. Support plan > Quota support - Included
On the Problem blade:
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.
On the Contact information blade:
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.
Increase a subscription cores quota
If your Batch account was created in user subscription mode and you need additional regional or VM family cores, request a quota increase in your subscription. For steps, see Resource Manager core quota increase requests.