Power Automate limit for Free license user

A Power Automate Free user does not have a fixed “employees per day” allowance; the flow has a 6,000-action entitlement per rolling 24 hours, so the practical recipient count depends on how many flow actions each individual message consumes.^1^

Estimate the employee count

Power Automate counts the trigger, connector actions, built-in actions, failed actions, retries, pagination, and each execution inside an Apply to each loop. A simple flow containing one trigger and one action consumes two requests per run.^2^

Use:

Maximum employees ≈ (daily allowance − fixed actions) ÷ actions executed per employee

Examples:

• One flow run, one Teams posting action per employee: approximately 6,000 employees at the theoretical maximum, minus the trigger, employee-list lookup, loop overhead, retries, and any other actions.
• Two actions per employee: approximately 3,000 employees.
• Three actions per employee: approximately 2,000 employees.

For example, if one run uses:

• 1 trigger
• 1 action to retrieve employees
• 1 Teams posting action for each employee

then a rough estimate is:

(6,000 − 2) ÷ 1 = 5,998 recipients

This is an estimate, not a guaranteed delivery limit. Failed postings and retries also consume requests.

During the current transition period, the published Free-license allowance can be 10,000 requests per cloud flow per 24 hours, rather than the official 6,000-per-user entitlement. Microsoft is phasing in the per-user limits starting April 2027, so design against 6,000 rather than relying on the temporary allowance.^3^

Teams messaging constraints

The Microsoft Teams connector is a standard connector, so it can be used with Power Automate Free. The Free license supports cloud flows without sharing and standard connectors only.^4^

To send an individual Teams message, configure Post a message in a chat or channel with:

1. Post as: Flow bot
2. Post in: Chat with Flow bot
3. Recipient: the employee’s user principal name or email
4. Message: the required individual message

Microsoft documents this direct-to-user configuration here.^5^

The Teams connector has separate throttling and service-protection limits. Those limits can stop or delay messages before the daily Power Automate allowance is exhausted; an HTTP 429 indicates connector throttling. The available Teams connector documentation also specifies constraints such as approximately 28 KB per posted message, but the supplied limits section does not publish an exact numeric per-connection rate for the posting action.^6^

For a large employee list:

• Avoid high concurrency initially.
• Send messages sequentially or use low Apply to each → Settings → Concurrency control.
• If HTTP 429 errors occur, reduce parallelism or divide recipients into smaller scheduled batches.
• Check actual consumption at Flow details → Analytics → Actions.^2^

Also verify the assigned plan under Power Automate → Settings → View My Licenses, because a Microsoft 365 seeded license and Power Automate Free can expose similar capabilities.^2^

For sustained delivery approaching several thousand individual messages daily, use a Power Automate Process license or another appropriately licensed messaging design rather than sizing production delivery against the Free entitlement.

References

1. Deep dive on specific licenses
2. Understand platform limits and avoid throttling
3. Requests limits and allocations
4. Types of Power Automate licenses
5. Send a message in Teams using Power Automate
6. Microsoft Teams