The three Power Automate request caps are the baseline entitlement from your Microsoft 365 license, the stackable add-on of 50,000 requests every 24 hours, and the Process license giving one flow its own 250,000 requests every 24 hours. Read them before you trigger a quarter-end run.
- The baseline entitlement, documented in Appendix B of the Power Platform Licensing Guide — read it for specifics.
- Each add-on adds 50,000 requests every 24 hours and stacks; multiple add-ons can be assigned.
- A Process license gives one flow an independent 250,000 requests every 24 hours, with up to 10 Process licenses stacked on a single flow as the published ceiling.
- Measure your flow first: count actions from four weekly run histories, then apply the quarter-end multiplier before choosing capacity.
What a request cap actually is
Power Automate charges itself against a request ceiling.
You need to know three things before a quarter-end run. First, which license tier sets your baseline. Second, what an add-on buys. Third, when a single flow gets its own pool rather than sharing the environment's.
Microsoft updated and substantially increased these limits in late 2021. Microsoft said plainly that the numbers were raised far above typical usage for most customers (Microsoft Learn). Treat that as comfort, not headroom. A quarter-end run is not typical usage.
Three things you must read first:
- The baseline entitlement your Microsoft 365 license grants for Power Automate.
- The add-on increment of 50,000 requests every 24 hours, and how many stack.
- The Process license, and its independent 250,000 requests every 24 hours for one flow.
If your weekly flow touches a CRM, a forecast workbook, and a notification step, you are already close to a real number. Measure it before you commit to a quarter-end refresh.
Baseline: where your license entitlement is documented
Your Microsoft 365 licenses that include Power Apps and Power Automate carry a baseline entitlement. Microsoft points to Appendix B in the Power Platform Licensing Guide for the specifics of that entitlement. Read Appendix B yourself (Microsoft Learn).
If two teams run weekly flows in the same environment, they draw from the same pool. A heavy run by one team can starve the other. Map who else is scheduled in your environment before you lock a quarter-end window.
It holds for a quiet pipeline sync. It strains when quarter-end pulls in every opportunity record, every stage change, and a full re-forecast — if that re-forecast covers the prior twelve weeks, check that assumption against your own records.
The add-on: 50,000 requests every 24 hours
When baseline is not enough, Microsoft offers an add-on. Each add-on raises the limit by another 50,000 requests every 24 hours, and you can assign multiple add-ons to increase it further (Microsoft Learn).
This is the elastic path. Each additional add-on stacks another 50,000 requests onto the same ceiling, and multiple add-ons can be assigned.
Add-ons are the right move for a predictable, known burst. They are the wrong move if only one flow is the problem. A quarter-end refresh that spikes for two hours, while the rest of the environment runs quiet, is better served by a flow-level entitlement than by loading the whole environment.
Here is how the three options compare side by side:
| Option | Entitlement | Scope |
|---|---|---|
| Add-on | +50,000 requests every 24 hours, stackable | Stackable, multiple can be assigned |
| Process license | 250,000 requests every 24 hours | One flow, independent of user licenses |
| Process licenses stacked | Up to 10 Process licenses on one flow | Up to ten times the base entitlement |
Do not read the table and stop. Read the next section on where the Process license actually fits, then measure your own flow.
The Process license: 250,000 requests every 24 hours for one flow
A Process license gives the flow its own entitlement of 250,000 Power Platform requests every 24 hours, independent of the licenses held by the people who use it (Microsoft Learn).
That word "independent" is the whole value. The flow does not care how many makers touch it. It does not care what baseline the environment holds. It holds its own 250,000.
If one flow needs more than 250,000 requests every 24 hours, stack up to 10 Process licenses on it (Microsoft Learn). Ten is the ceiling Microsoft publishes for one flow. Plan a run that stays inside it.
When to choose a Process license
Choose the Process license when one flow is the bottleneck. The quarter-end forecast refresh is the typical case. It pulls every open opportunity, re-ranks every stage, and writes the result back. The rest of the environment keeps running on baseline.
The Power Automate flow-level plan allows capacity to be specifically reserved for a single flow, irrespective of the owner of the flow (Microsoft Learn). That matters when ownership changes. A flow owned by a departing analyst keeps its reserved capacity when you planned for it this way.
Confirm with your licensing team which mechanism your agreement actually carries.
When add-ons still win
Add-ons win when the whole environment is under pressure. Quarter-end does not only spike one flow. Approvals stack up. Auditors run exports. Finance runs a parallel reconciliation. When everything in the environment lifts, load the environment.
Add-ons also win when the spike is short and the pattern repeats. A weekly close that always runs Tuesday morning does not need permanent flow-level capacity. A stack of add-ons gives the same headroom for a fraction of the structural change.
Reading your own flow before quarter-end
Open the flow run history for the last four weekly cycles. Count the actions in each run. Look for loops over list items — each iteration may add requests. Look for approvals, which may add requests to the step and the response.
Then write down the sum. Compare it against your baseline entitlement from Appendix B of the Power Platform Licensing Guide. If a normal week already sits near baseline, a quarter-end run that pulls three times the records will not fit.
Now apply the quarter-end multiplier honestly. If your quarter-end re-forecast revisits the prior twelve weeks, count that window explicitly. Every touched record, every re-ranking, every write-back is a request. A flow that runs quiet in week three of the quarter can multiply several times over in week thirteen.
Here is a practical shape for that check. Take your weekly action count. Multiply by the number of record loops you expect at quarter-end. Add the write-back cost. Compare the result against 250,000, and then against whatever add-on stack you already hold. If the answer exceeds ten stacked Process licenses on one flow, you need a design change or more capacity.
The design change is usually one of three things. Cache a read instead of re-reading each record. Batch the write-back into fewer calls. Or split the run across two flows with separate windows so neither one alone approaches the ceiling.
What to do in the run itself
Schedule the quarter-end flow when the environment is quiet. A flow that starts before the morning rush gives the 24-hour window a clean beginning.
Turn off anything optional for that run. Debug steps, test notifications, and preview branches may add requests. Strip them for the quarter-end pass and restore them after.
Watch the run as it executes. Open your run history to review each action's outcome. If an action retries, each retry may add requests.
If you run into throttling mid-run, stop and read the error. Do not restart blind. Restarting without a change restarts the same burn. The fix is either more capacity for the next window or fewer requests in the flow itself.
The quarter-end checklist
Use this before your first quarter-end run under the current limits.
- Baseline — read Appendix B of the Power Platform Licensing Guide and note your entitlement.
- Environment load — map every other scheduled flow sharing that pool.
- Run cost — count actions from four weekly run histories, then apply the quarter-end multiplier.
- Capacity choice — decide between add-on stack and a Process license on the single flow.
- Ceiling — hold the total below ten stacked Process licenses on any one flow.
- Quiet window — schedule the run before business hours in the environment's timezone.
- Trim — remove debug steps, test notifications, and preview branches for this run.
- Monitor — watch each action's detail during the run and stop on the first throttle error.
Run the checklist the week before, not the morning of. The capacity decision usually needs a licensing conversation, and that takes longer than the flow takes to run.
Common quarter-end mistakes
Treating the baseline as flow-specific. Check Appendix B for how your entitlement is scoped. Every other flow in the environment draws from it.
Your run history shows the true count.
Buying add-ons for a single hot flow. Add-ons load the whole environment. If only one flow is the problem, isolate it with a Process license instead.
Ignoring owner changes. A flow-level reservation is independent of the owner. Confirm your setup before you rely on that behavior.
Restarting a throttled run unchanged. The same flow will hit the same wall. Change the design or add capacity first.
Waiting for the error. Throttling appears at the worst moment — during the close. Measure on a normal week so the quarter-end run holds no surprises.
Related guides
FAQ
Does a Process license replace my environment's baseline? No. It gives one flow its own independent 250,000 requests every 24 hours. The environment baseline continues to serve every other flow in the environment.
How many add-ons can I stack? Microsoft publishes that each add-on adds 50,000 requests every 24 hours and that multiple add-ons can be assigned. Ask your licensing team for the ceiling that applies to your agreement.
What happens when one flow exceeds ten stacked Process licenses? The flow will not get more from that route. The published ceiling is ten Process licenses on a single flow. Past that, split the workload into separate flows with separate windows, or reduce the request count inside the flow.
Is 250,000 requests every 24 hours enough for a quarter-end forecast run? It depends on your record volume and loop design. Apply your quarter-end multiplier to that cost. If the result sits well under 250,000, the Process license holds. If it approaches or exceeds it, trim the flow or plan for the stacked ceiling.
Do the people using the flow need their own capacity? No. The Process license entitlement is independent of the licenses held by the people who use the flow. That separation is what makes it safe to plan a quarter-end run around a named flow rather than around a named user.