web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

Welcome to the Power Platform Communities
News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Copilot Studio / Copilot agents cannot ...
Copilot Studio
Unanswered

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

(0) ShareShare
ReportReport
Posted on by MM-17042105-0 2
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)
  • Vish WR Profile Picture
    Vish WR 3,748 on at
     
     

    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
     
    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 ♥
  • MM-17042105-0 Profile Picture
    MM-17042105-0 2 on at
    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.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

News and Announcements

Welcome to the Power Platform Communities

Quick Links

Season of Sharing Community Challenge Launch!

Jump in, show your community spirit, and win prizes!

Kudos to our 2025 Community Spotlight Honorees

Expanding mentorship, skilling, and AI innovation

Congratulations to the May Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Copilot Studio

#1
Valantis Profile Picture

Valantis 277

#2
11manish Profile Picture

11manish 206

#3
sannavajjala87 Profile Picture

sannavajjala87 156 Super User 2026 Season 1

Last 30 days Overall leaderboard

Featured topics

Announcing the "Microsoft Copilot Studio ❤️ MCP" lab
Block PII/PCI in Copilot Studio agent user prompt

Product updates

Microsoft Power Platform Community release plans