Microsoft Azure Batch · Rate Limits

Microsoft Azure Batch Rate Limits

Published Azure Batch service quotas and limits, transcribed from Microsoft's own "Batch service quotas and limits" reference and the azure-batch-limits include it renders (ms.date 2026-01-05 / 2026-06-16). REPLACES a 2026-05-04 scaffold that carried invented free/professional/enterprise request-per-minute tiers; Azure Batch publishes no such tiers. Batch meters RESOURCES (accounts, cores, jobs, pools), not requests per minute, so there is no published per-key request rate limit and no documented X-RateLimit-* response header set for the data plane.

Microsoft Azure Batch Rate Limits is the rate-limit profile for Microsoft Azure Batch on the APIs.io network — every limit transcribed verbatim from the provider’s own documentation on 2026-09-17.

It captures 11 rate-limit definitions, including Batch accounts per region per subscription — Azure Batch accounts per region per subscription 1-3 50; Dedicated cores per Batch account — Dedicated cores per Batch account 0-900; Low-priority (Spot) cores per Batch account — Low-priority cores per Batch account 0-100.

Limit state is signalled in the note, limit, remaining, and reset response headers, and an exhausted limit returns HTTP 503.

The profile also includes 3 backoff/retry policies defined and response codes documented for throttled, throttledCode, quotaExceeded, quotaExceededCodes, and serviceUnavailable.

Tagged areas include Quotas, Service Limits, and Throttling.

11 Limits Exhausted: HTTP 503 Quota: 400 notelimitremainingreset
Transcribed from the provider's documentation on 2026-09-17 — learn.microsoft.com/en-us/azure/batch/batch-quota-limit.
View Source
QuotasService LimitsThrottling

Limits

Batch accounts per region per subscription subscription
Azure Batch accounts per region per subscription 1-3 50
batch_accounts
3
Dedicated cores per Batch account account
Dedicated cores per Batch account 0-900
dedicated_cores
900
Default quotas for new accounts in some regions and subscription types have been reduced, in some cases to zero. Applies to Batch service pool allocation mode only.
Low-priority (Spot) cores per Batch account account
Low-priority cores per Batch account 0-100
low_priority_cores
100
Active jobs and job schedules per Batch account account
Active jobs and job schedules per Batch account ( completed jobs have no limit) 100-300 1,000
active_jobs_and_job_schedules
300
Completed jobs have no limit.
Pools per Batch account account
Pools per Batch account 0-100
pools
100
Private endpoint connections per Batch account account
Private endpoint connections per Batch account 100 100
private_endpoint_connections
100
Compute nodes in an inter-node communication enabled pool pool
Compute nodes in inter-node communication enabled pool Batch service pool allocation mode 100
compute_nodes
100
100 in Batch service pool allocation mode; 80 in user subscription mode.
Concurrent tasks per compute node node
Concurrent tasks per compute node 4 x number of node cores
concurrent_tasks
Applications per Batch account account
Applications per Batch account 200
applications
200
Application packages per application application
Application packages per application 40
application_packages
40
10 application packages per pool.
Maximum task lifetime task
The maximum lifetime of a task, from when it's added to the job to when it completes, is 180 days.
task_lifetime_days · day
180
Measured from when the task is added to the job to when it completes. Completed task data is retained for seven days by default if the node it ran on still exists; retention is configurable per task.

Policies

Quota increase
Quota increases are requested at no charge through an Azure support request (Issue type "Service and subscription limits (quotas)", Quota type "Batch") or through the Azure Quota REST API. Requests complete within a few minutes to two business days.
User subscription pool allocation mode
Batch accounts created with pool allocation mode "user subscription" do not use Batch core quotas at all. VMs are created directly in the subscription and the subscription's own regional and per-series compute core quotas apply instead.
Quotas are limits, not capacity guarantees
Microsoft states explicitly that a quota is a limit and not a capacity guarantee, and that quota values can change from either side.

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/microsoft-azure-batch-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.