Power Query · Rate Limits

Power Query Rate Limits

Rate limits for the Power Query programmatic surface (the Fabric Dataflow REST API). Fabric enforces a Unified Quota model: quota is tracked per IDENTITY — a user, service principal or managed identity — not per API key, not per capacity, and never shared between identities. Three independent quota buckets cover Platform APIs, Job Scheduler APIs and Long-Running Operation APIs, each at 200 calls per minute, in a fixed 60-second window that replenishes all at once rather than sliding. Individual endpoints may impose additional limits on top of the shared quota; both are evaluated and the most restrictive wins.

Power Query Rate Limits is the machine-readable rate-limit profile for Power Query on the APIs.io network, in the API Commons Rate Limits shape.

It captures 3 rate-limit definitions, measuring requests_per_minute.

Limit state is signalled in the retryAfter, limit, remaining, and reset response headers, and an exhausted limit returns HTTP 429.

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

Tagged areas include Business Intelligence, Data Integration, Microsoft Fabric, Rate Limiting, and Quotas.

3 Limits Exhausted: HTTP 429 Quota: 429 retryAfterlimitremainingreset
Transcribed from the provider's documentation on 2026-08-29 — learn.microsoft.com/en-us/rest/api/fabric/articles/thrott....
View Source
Business IntelligenceData IntegrationMicrosoft FabricRate LimitingQuotasThrottling

Limits

Unified Quota for Platform APIs identity
requests_per_minute · minute
200
Unified Quota for Job Scheduler APIs identity
requests_per_minute · minute
200
Unified Quota for Long-Running Operations APIs identity
requests_per_minute · minute
200

Policies

Dual enforcement
Every request is evaluated against BOTH the identity-level Unified Quota and any endpoint-specific limit. The most restrictive wins.
Independent buckets
Consuming the Job Scheduler quota does not consume Platform quota. A high-volume job workload cannot starve general item operations.
Identity isolation
Quotas are never shared between identities. One throttled service principal does not affect any other caller.
Honor Retry-After
Microsoft's stated guidance: honor Retry-After, apply bounded retries, and avoid bursts. Distributing requests evenly across the 60-second window is the documented way to avoid throttling.
Quota is not capacity
Microsoft states explicitly that APIs Quota governs request rate only. It does not represent Fabric compute, storage or billing capacity and has no effect on cost.

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/power-query-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.