How to trigger a Power Automate flow to copy Outlook email attachments based on a category change

Robert Knudson 0 Reputation points
2026-11-19T20:28:40.8+00:00

My goal is to manually trigger a Power Automate flow based on some user action. We have a number of shared email boxes. We have written several flows that will copy attachments from all new emails in a designated shared mailbox into SharePoint, and then apply metadata, including email header info. However, we have several email accounts (shared and private) for which we don't run a flow, partly because there is too much clutter. When we find an email with an attachment that we would like to preserve and share, we would like a way to trigger a flow that would capture the same metadata that our Power Automate flows capture.

Microsoft, in this Learn site, clearly states that "category change triggers are not natively supported" in Power Automate. Some other user-initiated trigger may be acceptable. We pursued setting the flag in Outlook, without success.

Forwarding the email to an account which is monitored by one of our working flows would work in some respects, but now the metadata has changed, rewriting over and losing valuable information such as the date sent, and the sender's email address.

Helpful people have suggested commercial solutions such as Colligo or Harmon IE, but these seem like overkill for such a simple problem.

Your suggestions will be appreciated!

Outlook | Web | Outlook on the web for business | Email
0 comments No comments

2 answers

Sort by: Most helpful
  1. Lin V 2,135 Reputation points Independent Advisor
    2026-11-19T20:58:40.6233333+00:00

    Hi Robert,

    I understand that you're trying to find a practical way to manually trigger the process for selected emails while keeping the original message metadata intact.

    At this time, I'm not aware of any official Microsoft documentation that prescribes a straightforward, built-in Power Automate solution for this exact scenario.

    I also looked through the AI-generated answer, and it raises a few alternatives that you may want to review, particularly if a custom solution is an option in your environment.

    Additionally, since the question now comes down largely to Power Automate flow design and how the Outlook connector can be used in this scenario, it may be outside the experience normally covered in this Outlook-focused category. You could also post the scenario in the Power Platform Community, where contributors with more Power Automate experience may be able to explore the available options with you.

    I hope you don't mind the referral to a different community. I believe a Power Automate-focused discussion would be more helpful for this particular scenario and may give you more specific guidance on the available approaches.

    Hopefully, this gives you a useful next step.

    Was this answer helpful?

    0 comments No comments

  2. AI answer

    2026-11-19T20:31:09.8066667+00:00

    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.

    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:

    1. User opens the original message in Outlook on the web.
    2. User selects the add-in command.
    3. The add-in obtains:
      • The selected message identifier.
      • The mailbox/shared-mailbox context.
    4. 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.
    5. The backend retrieves the original message and attachments, rather than forwarding it.
    6. 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

    1. Implement shared folders and shared mailbox scenarios in an Outlook add-in
    2. Overview of using Outlook and Power Automate
    3. Troubleshoot common issues with email in flows
    4. Trigger a cloud flow based on email properties
    5. Issues triggering emails with attachments from shared mailbox
    6. Office 365 Outlook
    7. Power Automate Flow: Email Attachment to SharePoint Folder - Microsoft Q&A
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.