Power Platform request limit calculator
Every paid licence carries 40,000 Power Platform requests a day, and every action in every flow spends them. This works out whether a user, a service account or a Process-licensed flow fits inside its allocation — before throttling tells you it does not.
What are you checking?
The three allocations work completely differently, and mixing them up is the usual reason an estimate is wrong. Licensed users get a personal limit that cannot be pooled. Service accounts share one tenant-wide pool. A Process licence belongs to the flow, not to a person.
What this person is licensed for
Multiple paid licences stack: a user with Dynamics 365 Customer Service Enterprise and Power Apps Premium has 80,000. Dynamics 365 attach licences add nothing — only the base licence carries an allocation.
What they consume in a day
Background and scheduled flows always charge the owner, whoever triggered them. Instant flows charge whoever pressed the button. So a single automation owner can quietly carry the whole department's usage.
Every action counts, including a Compose, an Initialize variable and a failed step. Retries and pagination count too, and a loop multiplies its contents.
App usage against Dataverse and connectors, plus anything their plug-ins and classic workflows generate.
Where these numbers come from
Allocations, the non-licensed pool formula and the five-minute ceiling come from Requests limits and allocations on Microsoft Learn.
This calculator uses the official limits. Every tenant is currently in a transition period with more generous limits applied at the flow level rather than the user level, and Microsoft has said enforcement will not begin until at least six months after usage reporting reaches general availability. Build against the official numbers, because the transition ends on Microsoft’s schedule, not yours.
Desktop flow executions do not consume Power Platform requests. Requests do not roll over between days.
Rates checked August 2026. Microsoft changes prices and entitlements; treat this as an estimate and confirm against your own agreement before you commit budget.
Common questions
- Whose limit does a flow actually use?
- Automated and scheduled flows always charge the owner of the flow, no matter who or what triggered them. Instant flows charge the person who ran them. This is why a single automation-minded person quietly ends up carrying an entire department's request usage on their personal allocation.
- What counts as a request?
- In Power Automate, every action — including Compose, Initialize variable, failed actions, retries and pagination. In Dataverse, every create, read, update, delete, assign and share, including the ones your plug-ins and classic workflows fire. In Power Apps, every connector and Dataverse call. Loops multiply their contents.
- Can I pool request limits across users?
- No. Licensed user limits are strictly per user and cannot be pooled at environment or tenant level. The only pooled allocation is the one for application, non-interactive, administrative and SYSTEM users, and licensed users can never draw on it.
- Will switching to a third-party integration tool avoid the limits?
- No. Microsoft is explicit that external data integration tools hit exactly the same Dataverse limits. The requests are counted at Dataverse, not at Power Automate, so moving the orchestration elsewhere changes nothing.
- How do I stop a heavy flow from throttling?
- Give the flow its own Process licence, which moves it to a 250,000 allocation attached to the flow rather than to a person, and stack more licences if it needs them. Otherwise move the environment to pay-as-you-go so overage is billed rather than throttled, or reduce actions: filter at the source rather than in a loop, batch Dataverse writes, and stop initialising variables you never read.
Most request problems are one flow nobody owns
The flows that blow a request budget are usually the ones inherited from someone who left, running hourly against a table nobody reads. Cartographer inventories every flow, app and plug-in across every environment so you can find them.
Keep going
Which licence do I need?
Your licence mix sets your request allocation as well as your bill.
Dataverse capacity calculator
The other entitlement that quietly stops a tenant working: storage.
Copilot credit estimator
Agent flows bill in credits, not requests. Price them separately.
Cost review workbook
Walk a full Power Platform cost review, requests and capacity included.