I cannot create a group of resources in a batch account despite I have sufficient quota

Question

I have a batch account in Azure. The quota in this batch account of several flavours of vCPUs (Av2 or Dv3 Series for example), that I know are different from the quotas of general vCPUs. When I try to create a group, even with 0 resources, I get a "Pool quota reached" error.

I asked several times to the support and I wasn't able to get either a solution or the proper increase in quota for the culprit service.

I am desperate, since I need to solve this next week (It is more than two months with this issue).

Many thanks

Answer 1

It sounds like you are encountering a "Pool quota reached" error when trying to create a group of resources in your Azure Batch account. This issue can occur even if you believe you have sufficient quota due to several factors:

1. Core Quotas: Azure Batch accounts have different core limits and quotas for various types of vCPUs, including dedicated and low-priority vCPUs. Even if you have enough quota for one type, you might be hitting a limit for another type or series.
2. Quota Limits: The default limits for dedicated cores per Batch account can vary, and in some cases, they may be set to zero for new accounts in certain regions. You can check your current core quotas in the Azure portal to confirm this.
3. User Subscription Mode: If your Batch account is set to use user subscription pool allocation, the quotas from your subscription for regional compute cores and per-series compute cores apply instead of the Azure Batch core quotas. This could lead to unexpected quota issues.
4. Support Requests: If you have already contacted support multiple times without resolution, it may be beneficial to escalate the issue or provide them with detailed information about your current quotas and the specific error messages you are encountering.

To resolve this issue, consider checking your quotas again in the Azure portal and potentially requesting a quota increase if you find that you are indeed limited. You can do this by navigating to your subscription settings and selecting "Usage + quotas" to submit a request for an increase.

---

References:

• Azure Batch accounts per region per subscription
• Batch service quotas and limits
• Resolve errors for resource quotas

Answer 2

Hello @Ignacio Blanquer

Azure Batch has Batch-managed core limits at the Batch account level, which are separate from:

• Subscription Compute (vCPU) quota
• Regional VM family quota

In multiple past cases, the issue was caused by one or more of the following:

1. Batch account Pool quota is exhausted
   • Default limits can be very low (for example: max pools, max cores per pool, or total Batch cores).
2. Dedicated vs Low‑Priority core limits
   • Dedicated cores might be exhausted while low‑priority cores remain (or vice versa).
3. Hidden per‑VM‑family Batch limits
   • Even though the subscription allows Av2/Dv3, the Batch account itself is blocked for that VM family.
4. Stale or orphaned pools
   • Deleted pools that were not fully deallocated still consume Batch quota (seen in long‑running accounts).

Steps to perform

**1.Verify Azure Batch quotas :
**Azure Portal → Batch Accounts → <Your Batch Account> → Quotas

Validate:

• Total cores (Dedicated / Low‑priority)
• Maximum pools
• Maximum cores per pool
• VM family availability

2.Explicitly request Azure Batch quota increase

Support request path :
Azure Portal → Help + support → Create a support request → Service: Azure Batch → Problem type: Quota / Core limit

Clearly specify:

• VM family (Av2 / Dv3)
• Dedicated vs Low‑priority cores
• Required number of pools
• Required cores per pool

3.Clean up orphaned pools:

az batch pool list --account-name <account> --account-key <key> 

Delete unused pools and ensure nodes show as idle/deallocated.

If pool deletion was incomplete earlier, Batch still counts those cores.

4.Validate SKU availability through Batch :

az batch location list-skus --location <region>

Links :
https://learn.microsoft.com/en-us/azure/batch/batch-quota-limit

https://learn.microsoft.com/en-us/azure/batch/batch-pool-vm-sizes

Thanks,

Manish Deshpande.