Power Platform Community Forum Thread Details

Hi all,

I’m currently designing a Power Automate solution that is triggered directly from a Power App. The architecture consists of about 20 flows, which are started by app users and often result in sending emails via a shared child flow.

At the moment, we are still in the testing phase with a small pilot group, but we are preparing to roll this out to over 1,000 users. One concern we want to proactively address is Outlook connector throttling.

Current setup:

Each main flow is triggered from a Power App.
These flows may call a child flow that handles sending emails.
The child flow uses an embedded connection, so emails are always sent from a single system account (the owner of the child flow).
Once scaled, we expect this account to hit throttling limits due to high email volume.

Goals:

Ensure all emails are sent from a single, consistent system account.
Avoid throttling on the Outlook connector as the number of users grows.
Ideally, leverage the user’s connection to call the child flow (to distribute load), but still have the email sent from the system account.

Question:

Has anyone implemented a similar model at scale? Is there a recommended approach to:

Run the child flow (or part of it) using the caller’s connection?
Still send the email from a system account, without triggering throttling?
Or use an alternative pattern (e.g., queue-based, Graph API, multiple accounts) to handle scalable email sending?