Power BI · Rate Limits

Power Bi Rate Limits

Power BI REST APIs apply per-user throttling to prevent overuse, returning HTTP 429 with a Retry-After header when a calling identity exceeds the documented per-time-window threshold. Numeric per-second/minute ceilings are not exhaustively published; specific operation groups (admin, embed-token, capacity, dataset refresh) carry their own published per-hour and per-day caps in the relevant operation reference. For Power BI Embedded and Fabric F-SKU capacity, throughput is governed by the v-core capacity rather than by API quota: utilization is evaluated every 30 seconds and capacities exceeding 100% enter "interactive request delay" mode.

Power Bi Rate Limits is the rate-limit profile for Power BI on the APIs.io network — every limit transcribed verbatim from the provider’s own documentation on 2026-11-05.

It captures 5 rate-limit definitions, including POST rows requests per minute — 120 POST rows requests per minute per semantic model; Rows added per hour — 1,000,000 rows added per hour per semantic model; Rows per POST — 10,000 max rows per single POST rows request.

Limit state is signalled in the retryAfter and requestId 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 capacityOverload.

Tagged areas include Analytics, Business Intelligence, Microsoft, and Rate Limiting.

5 Limits Exhausted: HTTP 429 retryAfterrequestId
Transcribed from the provider's documentation on 2026-11-05 — learn.microsoft.com/en-us/power-bi/developer/embedded/pus....
View Source
AnalyticsBusiness IntelligenceMicrosoftRate Limiting

Limits

POST rows requests per minute semantic model
120 POST rows requests per minute per semantic model
Push Datasets - PostRows
· per 1 minute
Rows added per hour semantic model
1,000,000 rows added per hour per semantic model
Push Datasets - PostRows
· per 1 hour
Rows per POST request
10,000 max rows per single POST rows request
Push Datasets - PostRows
Pending POST rows requests semantic model
5 max pending POST rows requests per semantic model
Push Datasets - PostRows
POST rows per hour on large tables semantic model
120 POST rows requests per hour per semantic model
Push Datasets - PostRows
· per 1 hour

Policies

Honor Retry-After
On 429, clients must wait the number of seconds indicated in Retry-After before retrying.
Capacity-bound throttling
For Embedded and Fabric workloads, scale up the v-core capacity (or use autoscale where supported) rather than retrying through 429 storms.
Cross-region operations
Operations that download files from a different region than the call origin may take longer; treat regional differences as latency, not throttling.
Operation-level limits
Specific operations (admin scans, dataset refresh, embed-token generation) have their own caps documented in the per-operation reference; consult the operation page rather than assuming a uniform global limit.
Development vs production embedding
Trial embed tokens with Pro/PPU are for development testing only; production embedding must run on purchased capacity.

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/power-bi-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

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.