Unanswered

Copilot agents cannot mutate triggering Outlook email due to missing MessageId exposure

(0) Share

Report

Posted on by MM-17042105-0

Copilot Studio agents can be triggered by incoming Outlook email and can call Outlook actions (Move, Assign Category, Update Email), but the agent runtime does not expose the MessageId of the triggering email. Since all Outlook mutation actions require MessageId, these tools silently no-op. This makes it impossible for agents to manage the lifecycle of the email that triggered them and forces split architectures with Power Automate. This appears to be a missing trigger context feature rather than a configuration issue.

Categories:

Autonomous agents

Bot extensibility

Calling actions from Copilot Studio

I have the same question (0)

All responses (2)

Answers (0)

Sort by

Vish WR 1,021 on at

Like (0)

Report
Copy link

Link copied!

@MM-17042105-0

When an agent receives an Outlook triggered event in Microsoft Copilot Studio it may not get the MessageId this could be by design, since the trigger context exposed to the agent is limited.

Because of that, Outlook actions won’t work as expected. I’d suggest using Power Automate to first capture the email (including MessageId) and then pass it along for further processing or handle the actions directly there.

Vishnu WR

LinkedIn - My Tech Space

Please ✅ Does this answer your question if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider answering Yes to Was this reply helpful? or give it a Like ♥

Was this reply helpful? Yes No
MM-17042105-0 2 on at

Like (0)

Report
Copy link

Link copied!

Thanks for the confirmation — this aligns with what I’ve observed.

Because the agent trigger context doesn’t expose MessageId, all Outlook mutation actions (Move, Assign Category, Update Email, Flag) silently fail when called from an autonomous agent. This makes it impossible to manage the lifecycle of the triggering email inside Copilot Studio alone and forces Power Automate to remain in the loop. Exposing MessageId (read‑only) in the agent trigger context would unlock a large class of valid automation scenarios.

Was this reply helpful? Yes No