Microsoft Purview · Rate Limits

Microsoft Purview Rate Limits

Microsoft Purview APIs sit on the Azure Resource Manager and Microsoft Graph control planes, inheriting their throttling models. ARM control-plane requests are subject to subscription-level read / write limits (12,000 reads, 1,200 writes per hour per subscription per region); Graph compliance endpoints follow Graph throttling. Purview-specific data-plane limits are not separately published per-tier — they degrade based on Data Map capacity-unit allocation. Limits are enforced via 429 with Retry-After.

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

It captures 4 rate-limit definitions, measuring requests_per_hour and varies.

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

Tagged areas include Rate Limiting, Compliance, Data Governance, and Microsoft.

4 Limits Throttle: 429
Rate LimitingComplianceData GovernanceMicrosoft

Limits

Azure Resource Manager reads (subscription / region) account/region
requests_per_hour · hour
12000
Default ARM control-plane read budget per subscription per region.
Azure Resource Manager writes (subscription / region) account/region
requests_per_hour · hour
1200
Default ARM control-plane write budget per subscription per region.
Microsoft Graph (Purview compliance endpoints) account
varies
See Microsoft Graph throttling guidance — service- and tenant-specific
Purview Data Map / scanning account
varies
Capacity bound by allocated Data Map capacity units; degrades when capacity is exhausted

Policies

Honor Retry-After
All 429 responses include Retry-After. Implement exponential backoff with jitter on top of the header value.
Use ARM rate-limit headers
Inspect x-ms-ratelimit-remaining-subscription-reads / -writes to back off proactively before hitting the cap.
Capacity scaling
Increase allocated Data Map capacity units to raise effective Purview data-plane throughput.
Service principal scoping
Use a dedicated service principal per ETL pipeline to isolate throttling impact and improve diagnosability.

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-purview-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.