Throttling
Rate-limiting of API calls in Dataverse, Power Platform, and Microsoft services — protects platform capacity; integrations must respect 429 responses with backoff.
Throttling is the rate-limiting mechanism Microsoft services apply to API calls — protecting platform capacity from runaway consumers. Dataverse, Business Central, Finance and SCM, Power Automate connectors, and Microsoft Graph all enforce throttling. When a consumer exceeds the configured rate, the service responds with HTTP 429 (Too Many Requests) plus a Retry-After header indicating how long to wait. Well-behaved integrations honour the Retry-After value with exponential backoff; chatty integrations that ignore throttling degrade everyone's experience and risk being further rate-limited. Throttling limits include per-user-per-minute, per-tenant aggregate, and per-connector-specific limits. Batch operations, filtering at the source, and caching reduce API call volume; capacity add-ons can raise the ceiling at scale.