Azure DevOps · Rate Limits

Microsoft Azure Devops Rate Limits

Azure DevOps Services rate-limits API consumers via Throughput Service Tokens (TSTUs). TSTUs blend SQL DTU, compute, and storage usage. Each user has a sliding 5-minute window; sustained high consumption triggers delays first (X-RateLimit-Delay), then 429 responses.

3 Limits Throttle: 429
Rate LimitingDevOpsMicrosoft Azure

Limits

Global per-user TSTU window user
TSTU_per_5_minutes · minute
200
200 TSTUs in any sliding 5-minute window. 1 TSTU ~= average load of one typical user over 5 minutes. Spikes up to 100 TSTUs are tolerated.
Typical user spike user
TSTU_per_5_minutes · minute
10
Normal user activity generates spikes of 10 TSTUs or fewer per 5 minutes.
Tolerated burst user
TSTU_per_5_minutes · minute
100
Larger but less frequent spikes can reach up to 100 TSTUs before delay/throttle kicks in.

Policies

Honor Retry-After
When the API returns Retry-After (with HTTP 200 in delayed mode or 429 in blocked mode), wait the specified seconds before sending another request.
Monitor X-RateLimit headers
Track X-RateLimit-Remaining and X-RateLimit-Limit to smooth out request bursts proactively before delays start (Remaining = 0 indicates active delay).
Use bulk and webhook patterns
Use service hooks, batch APIs, and OData reports instead of polling individual work items to reduce TSTU consumption.
Personal access token attribution
Use distinct PATs / app identities per integration so a single misbehaving integration does not consume a user's full quota.

Sources