Which license is recommended for a flow that may receive 700+ triggers in a short time?

(0) Share

Report

Posted on by CU03040547-0

Hello,
I am planning to run an emergency safety‑check flow with the following structure:

Trigger: Microsoft Forms response
Search SharePoint List twice
Update one List item

This results in about 4 requests per execution.

During annual drills or real emergencies, 700 or more users may submit responses within a short time, resulting in:

~2,800 requests per drill
Potentially more during real emergencies

My questions:

Is the Microsoft 365 license sufficient for this scenario,
or is it likely to hit request limits or throttling?
If a paid plan is recommended, which one is more appropriate:
- Power Automate Premium (per user)
- Power Automate per flow
Could you explain the reasoning based on request limits and throttling behavior?

Thank you very much.

Categories:

General topics

I have the same question (0)

All responses (2)

Answers (0)

Sort by

Suggested answer

Sam_Fawzi 917 Super User 2026 Season 1 on at

Like
a
(1)

Report
Copy link

Link copied!

Hi @ CU03040547-0

Power Automate per‑flow plan is the safest choice.
Why:

Your scenario (~700 runs × ~4 actions ≈ 2,800 requests in a short burst) is fine on total volume, but the risk is throttling during spikes, not daily limits.
Microsoft 365–included Power Automate uses the flow owner’s license and has lower request quotas, making it more prone to throttling during bursts. Understand platform limits and avoid throttling - Power Automate | Microsoft Learn

Per‑flow plan gives a much higher daily request allocation (≈15,000+/day per flow) and is designed for shared, high‑volume, event‑driven flows like emergency drills. Understanding Rate Limits in Power Automate and How to Handle Them – Rishan Solutions

Per‑user Premium scales per licensed user, not per flow—inefficient when hundreds of users trigger the same flow.

Important note:
Even with the right license, SharePoint has per‑minute connector limits (~600 calls/min per connection), so enable trigger concurrency control or add slight buffering if needed. API Rate Limits and Throttling in Power Automate - Manuel T Gomes
Bottom line:
Use Power Automate per‑flow for predictable scenarios like safety checks.

Was this reply helpful? Yes No
CU03040547-0 19 on at

Like
a
(0)

Report
Copy link

Link copied!

Thank you very much for your detailed explanation.
Your clarification about the behavior of high‑burst scenarios and the advantages of the per‑flow plan was very helpful.
I now have a much clearer understanding of why the per‑flow plan is more reliable for this type of emergency‑response flow.
I appreciate your support.

Was this reply helpful? Yes No