Microsoft Power Apps · Rate Limits

Microsoft Power Apps Rate Limits

Microsoft Power Apps enforces two distinct limit models. Power Platform request (PPR) entitlements are 24-hour daily quotas tied to the assigned user license (e.g. 40,000/24hr for Premium, 6,000/24hr for Power Apps per-app or pay-as-you-go). Dataverse service-protection limits are per-user per-web-server sliding 5-minute windows that cap raw API velocity. Limits are enforced per-user; raise via the PPR capacity add-on (50,000 requests per pack) or via custom enterprise arrangement with Microsoft.

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

It captures 9 rate-limit definitions, measuring requests_per_day, requests_per_5min, varies, concurrent_requests, and requests_per_second.

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

Tagged areas include Rate Limiting, Business Applications, Microsoft, Power Platform, and Dataverse.

9 Limits Throttle: 429 Quota: 429
Rate LimitingBusiness ApplicationsMicrosoftPower PlatformDataverse

Limits

Power Platform requests (Power Apps Premium / Per-user) account
requests_per_day · day
40000
Sliding 24-hour window per licensed user. Includes Dataverse and connector calls from Power Apps and Power Automate.
Power Platform requests (Power Apps per-app / pay-as-you-go / Microsoft 365 seeded) account
requests_per_day · day
6000
Sliding 24-hour window per licensed user.
Power Platform requests (Power Automate per-flow / Copilot Studio) account
requests_per_day · day
250000
Per-flow license; flow-level rather than user-level.
Power Apps Portals (paid login) account
requests_per_day · day
200
Non-licensed user pool (Power Apps tenant) account
requests_per_day · day
25000
Tenant-pooled requests for application/service-principal/system users.
Dataverse number-of-requests (service protection) account/region/service
requests_per_5min · minute
6000
Per-user per-web-server sliding 5-minute window (default 6,000). Returns 429 with Retry-After.
Dataverse execution-time (service protection) account/region/service
varies
1,200,000 ms combined execution time per 300-second sliding window per user per web server
Dataverse concurrent-requests (service protection) account/region/service
concurrent_requests
52
Default; can be higher in some environments. Returns 429 immediately on excess.
Dataverse Search API account
requests_per_second · second
1
One request/second per user against api/search.

Policies

Retry-After honoring
All 429 responses carry a Retry-After header (seconds). Clients must pause for that duration before retrying. Microsoft.PowerPlatform.Dataverse.Client.ServiceClient handles this automatically.
Sliding 24-hour PPR window
Power Platform request entitlement is a sliding 24-hour window per user; any request looks back 24h to compute remaining capacity. Limits do not roll over day-to-day.
Stackable PPR licenses
Multiple paid licenses on the same user stack additively (e.g. 40k + 40k = 80k/24hr). During the transition period, license stacking is not honored — the higher of assigned plans is used.
Capacity add-on
Power Platform Request capacity add-on adds 50,000 requests per pack per 24 hours; multiple packs stack. Used to raise limits without re-licensing.
Plug-in / sandbox exemption
Operations originating from plug-ins and custom workflow activities run in the sandbox and do not count against service-protection limits, but their execution time accrues to the triggering request.
High-usage enforcement transition
Microsoft is in a transition period; strict PPR enforcement begins six months after Power Platform admin center reporting reaches GA. During transition, generous interim caps apply (e.g. 200k/cloud-flow for Premium).

Sources