Azure Repos · Rate Limits

Microsoft Azure Repo Rate Limits

Azure Repos REST APIs are rate-limited via Azure DevOps Services' shared TSTU (Throughput Service Threshold Unit) sliding-window model — 200 TSTUs per 5 minutes per user/identity. Each REST or Git operation costs a variable number of TSTUs. Throttled requests return HTTP 429 with Retry-After. Git push/pull operations also have additional per-repository protections against abuse. Per-user TSTU limits cannot be raised by support.

Microsoft Azure Repo Rate Limits is the machine-readable rate-limit profile for Azure Repos on the APIs.io network, in the API Commons Rate Limits shape.

It captures 3 rate-limit definitions, measuring tstu_per_5_minutes, bytes_per_push, and concurrent_builds.

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, delayedNotBlocked, and serviceUnavailable.

Tagged areas include DevOps, Git, Repositories, Source Control, and TFVC.

3 Limits Exhausted: HTTP 429 retryAfterdelaylimitremaining
Method: generated, dated 2026-05-05.
Written by API Evangelist on 2026-05-05 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
DevOpsGitRepositoriesSource ControlTFVCVersion ControlRate Limiting

Limits

Per-user TSTU sliding window user
tstu_per_5_minutes · minute
200
REST API and Git operation throughput; light reads <1 TSTU, heavy listings 5+ TSTUs.
Git push payload repository
bytes_per_push
see vendor docs
Pushes >1 GB or with very large blobs may be throttled or rejected. Use Git LFS.
Branch policy build queue repository
concurrent_builds
see vendor docs
Concurrent CI builds triggered by PR policies are bounded by purchased Azure Pipelines parallel jobs.

Policies

TSTU cost weighting
Each REST call costs differing TSTUs by database/CPU expense. Plan large backfills with backoff between batches.
Delay before block
Persistent abuse first triggers X-RateLimit-Delay (slowed responses), then 429.
Spread across identities
To scale automation, fan out work across multiple service principals or PATs; each gets its own 200-TSTU window.
Use Git LFS for large binaries
Files >100 MB should be stored in Git LFS to avoid repository bloat and push throttling.
Honor Retry-After
Implement exponential backoff with jitter on 429 responses.

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/microsoft-azure-repo-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.