There is no verified no-code Power Automate trigger that lets a user select an arbitrary existing message in an Outlook on the web shared mailbox and then process that original message while retaining its metadata.
Recommended design: a small Outlook add-in plus a reusable flow
For a truly user-initiated workflow, use an Outlook add-in command such as Save attachments to SharePoint. The add-in should identify the currently selected message and mailbox, then pass that context to a flow or intermediary service.
The design is:
- User opens the original message in Outlook on the web.
- User selects the add-in command.
- The add-in obtains:
- The selected message identifier.
- The mailbox/shared-mailbox context.
- The add-in sends those values to an authenticated HTTP endpoint—typically an HTTP-triggered flow or a small service that invokes the processing flow.
- The backend retrieves the original message and attachments, rather than forwarding it.
- Reuse the attachment-to-SharePoint portion of your existing flows:
- Iterate through the attachments.
- Create each SharePoint file.
- Write the original sender, sent date, subject, recipients, and other metadata to the library columns.
Treat this as a custom-development option, not a built-in Power Automate feature. Outlook add-ins can access shared-item properties, but shared-mailbox support depends on how the mailbox is opened:
- In Outlook on the web, the documented supported shared context is when the mailbox is opened in a separate window through Open another mailbox.
- A mailbox hidden from the Global Address List can cause the current Outlook item to be unavailable to the add-in.
^1^
The HTTP endpoint must require organizational authentication and validate that the caller is authorized for the requested mailbox; do not accept an arbitrary mailbox address and message ID anonymously.
Why the simpler Outlook actions do not meet the requirement
- Category change: There is no documented Outlook connector trigger for a category change.
- Flagging: Although the Office 365 Outlook connector includes When an email is flagged (V3), this has already failed in your scenario, and the available Microsoft documentation does not establish it as a supported selected-message mechanism for shared mailboxes in Outlook on the web. ^2^
- Moving a message into a watched folder: This does not retrigger an email-arrival flow. Microsoft explicitly states that a flow triggered by email arrival runs only when a new email arrives, not when an existing email is moved between folders. ^3^
- For a selected message: The available Microsoft documentation does not confirm that this trigger works for shared-mailbox messages in Outlook on the web. It should therefore not be the basis of a production design without first proving it in your tenant and client.
- Forwarding: This creates a new message envelope, so it cannot serve as the authoritative source for the original sender and sent timestamp.
Lower-development compromise: a selective arrival flow
If add-in development is disproportionate, the supported compromise is an arrival-triggered flow that preserves the original message data but decides whether to archive it using criteria available at arrival time—for example sender, subject, recipient address, or attachment presence. Microsoft documents those trigger filters for When a new email arrives (V3). ^4^
This is not equivalent to manually choosing an old message: it handles only future incoming messages. It can, however, reduce clutter if reliable trigger-time filters exist.
For attachment processing, set these advanced trigger options:
- Only with Attachments:
Yes
- Include Attachments:
Yes
The second setting is necessary for attachment content bytes to be available to SharePoint Create file; otherwise, the content can be null. ^5^
A separate flow is required for each mailbox being monitored; the Outlook connector does not monitor multiple mailboxes with one trigger. ^6^
Shared-mailbox troubleshooting boundary
Full Access, opening the shared mailbox once, or recreating the Outlook connection should be investigated only if a shared-mailbox trigger reports that the Inbox/default folder cannot be found. Those steps address mailbox-resolution or stale-connection failures, not the absence of a category-change or selected-message trigger. ^7^
References
- Implement shared folders and shared mailbox scenarios in an Outlook add-in
- Overview of using Outlook and Power Automate
- Troubleshoot common issues with email in flows
- Trigger a cloud flow based on email properties
- Issues triggering emails with attachments from shared mailbox
- Office 365 Outlook
- Power Automate Flow: Email Attachment to SharePoint Folder - Microsoft Q&A