Microsoft Azure Pipelines Rate Limits
Azure DevOps Services (which hosts Azure Pipelines) applies a per-user / per-identity Throughput Service Threshold (TSTU / RCU) sliding-window rate limit. Each REST API call consumes a number of TSTUs based on cost; each user has 200 TSTUs per 5-minute sliding window. Throttled requests return HTTP 429 with Retry-After. Concurrency is capped not by API rate but by purchased parallel jobs (default 25 for Microsoft-hosted on new orgs, raise via support). Per-user TSTU limits cannot be raised — clients must throttle.
Microsoft Azure Pipelines Rate Limits is the machine-readable rate-limit profile for Azure Pipelines on the APIs.io network, in the API Commons Rate Limits shape.
It captures 5 rate-limit definitions, measuring tstu_per_5_minutes, concurrent_jobs, and minutes_per_run.
Limit state is signalled in the retryAfter, delay, limit, and remaining response headers, and an exhausted limit returns HTTP 429.
This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.
The profile also includes 5 backoff/retry policies defined and response codes documented for throttled and delayedNotBlocked.
Tagged areas include Automation, Build, CI/CD, Deployment, and DevOps.
retryAfterdelaylimitremaining
generated, dated 2026-05-05.
Limits
Policies
Sources
- https://learn.microsoft.com/en-us/azure/devops/integrate/concepts/rate-limits
- https://learn.microsoft.com/en-us/azure/devops/pipelines/licensing/concurrent-jobs
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.