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.
4 Limits
Throttle: 429
DevOpsCI/CDRate Limiting
Limits
Per-user TSTU consumption user
200
Sliding 5-minute window. Delays start before block; block returns 429.
Per-pipeline TSTU consumption pipeline
200
Each pipeline tracked independently; matches user limit.
Typical user usage user
10
Reference baseline; not a hard cap.
Burst usage user
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.