Power Automate can monitor a Microsoft 365 shared mailbox and move a message into one of that mailbox’s folders.
The confusing part is context. The flow connection belongs to a user, so an action can show that user’s personal folders unless you explicitly tell it which shared mailbox contains the original message.
The fix: use When a new email arrives in a shared mailbox (V2), then set Original Mailbox Address on mailbox actions such as Move email or Export email.
Fact-checked against Microsoft Learn on 24 August 2026.
What you need first
The account behind the Office 365 Outlook connection needs access to the shared mailbox.
Microsoft documents an important distinction: the shared-mailbox trigger does not work for user-to-user shared mailboxes unless the connecting user has Full Access. Permission to send as the mailbox is not the same as permission to read and move its contents. Check Microsoft’s mailbox-permission guidance and the Office 365 Outlook connector limitations.
You also need:
- A Microsoft 365 mailbox supported by the connector.
- A target folder inside the shared mailbox.
- A clear trigger condition, such as sender or subject.
- An owner for the flow and its connection.
Move matching messages into a shared-mailbox folder
1. Create the shared-mailbox trigger
Create an Automated cloud flow and choose:
Office 365 Outlook : When a new email arrives in a shared mailbox (V2)
Enter the full shared-mailbox address, for example support@contoso.com, and choose the folder to monitor.
The current trigger is labelled V2. Do not replace it with the personal-mailbox V3 trigger merely because the number looks newer.
2. Filter before the flow runs
Use the trigger’s advanced parameters for stable conditions such as:
- From.
- Subject Filter.
- Has Attachment.
- Importance.
Microsoft recommends filtering at the trigger where possible because a later Condition still consumes a flow run. See Trigger a cloud flow based on email properties.
Avoid broad automations that inspect every message in a busy support or finance mailbox unless that is genuinely required.
3. Add the Move email action
Add the current Move email action from the Office 365 Outlook connector.
Set Message Id to the message ID supplied by the trigger.
Then expand the advanced parameters and enter the shared mailbox address in Original Mailbox Address.
Do this before choosing the destination folder. It tells the connector to load the shared mailbox’s folder tree rather than the connection owner’s personal folders.
Choose the target folder and save the flow.
4. Test with a new message
Send a new message that matches the trigger.
Check all three places:
- The flow run history shows a successful trigger and move action.
- The message has left the monitored folder.
- The message appears in the intended shared-mailbox folder.
Do not test only by dragging an old message into the monitored folder. Microsoft explains that mail triggers use the message’s received time and can skip older messages moved after a later message has already advanced the trigger’s checkpoint.
Save a clean body into Microsoft Lists
If the same flow creates a Microsoft Lists item, the email body arrives as HTML.
Add Content Conversion : Html to text and pass it the message body. Use the output in Create item.
The Content Conversion connector is classed as standard, but it is still marked Preview. Microsoft also documents that it removes formatting and hyperlinks, inserts line breaks at 80 characters and is unavailable for new implementations in GCC and GCC High.
That makes it useful for readable notes, not for preserving the original record. Keep the exported EML message if fidelity matters.
Save the shared-mailbox message or its attachments to SharePoint
The same mailbox context rule applies to Export email (V2): supply the message ID and set Original Mailbox Address to the shared address.
You can then create the EML file in SharePoint and loop through attachments. Our companion guide explains the full pattern for saving Outlook email attachments to SharePoint.
For the wider buying decision, see Microsoft 365 versus specialist Outlook filing add-ins.
Common failures
The folder picker shows my personal mailbox
Populate Original Mailbox Address with the shared mailbox’s full email address, then reopen the folder picker.
“Specified object was not found in the store”
Microsoft lists several likely causes:
- The connection owner lacks the required permission.
- The account is not a member of the shared mailbox.
- Original Mailbox Address is missing or wrong.
- Another person or process already moved or deleted the message.
- The Outlook connection needs to be recreated.
Check those before replacing the flow with a more complicated one.
The trigger misses an older message moved into the folder
The connector’s trigger checkpoint is based on received time. A message received earlier can be skipped when it is moved into the monitored folder after a newer message has already been processed.
If moving old messages is part of the business process, do not rely on the new-email trigger as a backlog processor. Build a deliberate reconciliation or batch process.
Attachments time out
For higher-volume mailboxes, set Include Attachments to No on the trigger and use Get Attachment (V2) later. Microsoft warns that waiting for every attachment in the trigger can time out when several messages arrive together.
The email body is unavailable
Encrypted messages are a documented connector limitation. The trigger can return a note saying the content is secured instead of the actual body.
A message is processed twice
Do not assume the trigger is exactly-once. Safe Attachments with Dynamic Delivery can cause a run before and after attachment scanning. Add a duplicate check when creating a SharePoint record or Microsoft Lists item.
Outlook rules or Power Automate?
Use an Outlook or Exchange rule when the requirement is simply “move messages matching this condition into that mail folder”. It is easier to understand and has fewer moving parts.
Use Power Automate when the process must continue beyond the mailbox, for example:
- Create a Microsoft Lists item.
- Save the message or attachments to SharePoint.
- Start an approval.
- Notify a Teams channel.
- Apply multi-step business logic.
- Record and handle failures.
Power Automate is not automatically more reliable because it has more boxes on the screen. The useful option is the smallest design that meets the process and can still be supported six months later.
Final checklist
- The connection owner has Full Access.
- The dedicated shared-mailbox trigger is used.
- Trigger filters are narrow enough.
- Original Mailbox Address is set on later mailbox actions.
- The target folder is selected after setting the mailbox address.
- Duplicate behaviour is defined.
- Attachment volume and encrypted mail have been tested.
- Failures notify somebody who can act.
- Ownership is not tied to an employee likely to disappear from the process.
For practical flow patterns, failure checks and current Microsoft changes, join the Power Automate Builders Space.