Azure DevOps · Rate Limits

Azure Devops Rate Limits

Azure DevOps Services enforces a global consumption limit measured in Azure DevOps Throughput Units (TSTUs) - an abstract unit blending database (Azure SQL DTUs), compute, and storage cost. The limit is 200 TSTUs in any sliding five-minute window per user (or pipeline). Normal user activity generates fewer than 10 TSTUs per five minutes; bursts can reach 100. Throttled requests are first delayed (response still returns HTTP 200) and ultimately blocked with HTTP 429.

Azure Devops Rate Limits is the machine-readable rate-limit profile for Azure DevOps on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 4 rate-limit definitions, measuring TSTU_per_5min.

The profile also includes 6 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include DevOps, CI/CD, and Rate Limiting.

4 Limits Throttle: 429
DevOpsCI/CDRate Limiting

Limits

Per-user TSTU consumption user
TSTU_per_5min · minute
200
Sliding 5-minute window. Delays start before block; block returns 429.
Per-pipeline TSTU consumption pipeline
TSTU_per_5min · minute
200
Each pipeline tracked independently; matches user limit.
Typical user usage user
TSTU_per_5min · minute
10
Reference baseline; not a hard cap.
Burst usage user
TSTU_per_5min · minute
100
Reference burst threshold; sustained spikes above 200 are throttled.

Policies

Honor Retry-After
When delays are imposed, response includes Retry-After. Wait before sending the next request. HTTP 200 is still returned during delay phase.
Backoff for 429
When blocked (HTTP 429), apply exponential backoff. Retry-After indicates seconds to wait.
Monitor X-RateLimit headers
Track X-RateLimit-Remaining and X-RateLimit-Limit to proactively slow down before delays begin.
Raise via Basic + Test Plans
Identities used by tools/integrations can get higher rate limits by being assigned the Basic + Test Plans access level.
Per-namespace tracking
Limits are tracked per shared resource; X-RateLimit-Resource indicates which threshold was reached.
Wiki, repo, work tracking limits
Separate limits exist for Wiki files (25 MB), repo size, work items, queries, dashboards - see service-specific docs.

Sources

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/azure-devops-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

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.