Yes, Power Automate can assign shared mailbox emails round robin, but only as a flow you build, store state for and maintain yourself. It can rotate new email between people by forwarding it, moving it to their folder or tagging it with a category. What it can't do is give the email a real owner, skip people who are away without extra work, or tell you how fast anyone replied. This guide shows how the flow works, where it breaks and when a dedicated tool is the simpler answer.
How a round robin flow works
A typical build has four parts:
- Trigger. The Office 365 Outlook connector's "When a new email arrives in a shared mailbox (V2)" trigger watches the shared mailbox, for example support@.
- State. A SharePoint list holds the team members in order and the position of the last person who received an email. Flow variables reset on every run, so the rotation can't live inside the flow.
- Pick and act. The flow reads the position, picks the next person, then forwards the email to them, moves it to a folder with their name or applies a category such as "Chris".
- Save. The flow writes the new position back to the list for the next email.
For a small team with steady volume, this works. The trouble starts with the details.
Where the flow breaks down
Two emails at once. Power Automate can run several copies of a flow at the same time. If two emails arrive together, both runs can read the same position and send both emails to the same person. The fix is to set the trigger's concurrency control to one run at a time, which also means a busy mailbox queues up behind a single run.
People who are out. The flow doesn't know who's on vacation, at lunch or at their limit. Skipping them means keeping an availability column up to date by hand or building another flow to do it.
No real owner. Outlook has no assignment field. A forwarded copy, a folder or a category tells the team who should act, but nothing stops two people replying, and nothing records who actually did.
No response times. A flow can route email but can't tell you how long customers waited, which messages are aging or whether you're meeting your targets.
Upkeep. Flows run under someone's connection. When that person changes role or leaves, or the team changes, someone has to update the flow and the list. Each new mailbox usually means another flow.
When Power Automate is enough
Power Automate is a good fit when:
- One or two people work the mailbox and volume is low.
- You only need to send certain senders or subjects to a fixed person.
- You have someone who is comfortable building and maintaining flows.
- Nobody needs response-time reporting or SLA alerts.
When a dedicated tool is simpler
Once several people share a mailbox and response times matter, the workarounds pile up. A shared mailbox tool does the same job without a flow:
| Power Automate flow | Emailgistics | |
|---|---|---|
| Round robin | You build it, with state in SharePoint | Built in |
| Load balancing by current workload | You build it | Built in, with a per-person limit (Max Messages) |
| Skip people who are unavailable | You maintain an availability list | One-click availability for each user |
| One owner per email | No, only a forward, folder or category | Yes, two people can't reply to the same email |
| Response-time targets and alerts | No | Reply and close targets by mailbox or tag, with alerts |
| Reporting | No | Real-time dashboard and user and mailbox reports |
| Where the team works | Outlook | Outlook |
Emailgistics assigns each new email to one owner by round robin, load balancing or rules, keeps follow-ups with the person who handled the first message and works inside Outlook on the shared mailboxes you already have. Basic round robin and rules are included on every plan, from $11 per user per month. See Emailgistics vs Power Automate for a fuller comparison, or how load balancing works.
The bottom line
Power Automate can rotate email between people, and for a small, quiet mailbox that may be all you need. As soon as you need email to have a real owner, skip people who are out and show response times, you're rebuilding a shared inbox tool one flow at a time.
