When using the Microsoft Teams integration / MCP to reply to messages, the agent reports that it calls the tool with a root message ID provided, which should result in a reply to said root message in Teams. However, in Teams what should be a reply in thread appears as a new message not linked to any previous messages.
Steps to Reproduce
Have an agent attempt to send a reply to a teams message.
A loosely related item as well - replies in thread from people don’t seem to trigger the “new message in channel” trigger or reply to the agent that posted the original message the thread forks off of.
Where you saw it: was this an Automation (for example, one triggered by a Teams message), or a cloud agent you started yourself with the Microsoft Teams MCP connected?
An ID for an affected run: the agent or run ID (from the cloud agent URL or the Automations run history), or a request ID.
Where the original message was: a channel post, or a 1:1 or group chat? Teams chats don’t support threaded replies, so this changes what we’d expect to see.
A screenshot showing the original message and the agent’s unthreaded reply would help too, if you can share one.
Part of this is current behavior
A “new message in channel” trigger only fires on thread replies if the trigger has a “message contains” filter set. Top-level posts fire it either way. This matches how our Slack triggers work.
To send a thread reply to the agent, @mention Cursor in the reply. Replies without a mention aren’t passed to the agent.
The other part is probably caused by the first issue. The agent is linked to the thread it meant to reply in. If its reply landed as a new top-level post instead, replies under that post aren’t linked to the agent, even with an @mention.
Yes, this was an automation triggered by a teams message. The use case is to have an internal feature request workflow where someone can send a message to a shared teams channel and Cursor receives that, reviews minimum standards for requests, and checks/creates an item in Linear.
Here’s the Agent ID: bc-2a98c3a8-fb11-4aec-a5e6-8d68dd5a6f42
The original message is in a Teams channel (not an individual or group chat) set up with the Thread UI (not sure if this makes a difference, I tested both thread and post options and neither worked). Here’s an example:
The other thing I noticed is that the Cursor app doesn’t seem to ask for access to the list channel messages permission, so the agent can’t see additional context without specific message IDs. I’m not sure if this is a configuration issue on our end or if the app isn’t requesting the permission at all, but it would be a helpful workaround as at a minimum the agent would be able to see the chat history and use that for context.
This looks like an issue on our side. Automation replies to Teams are supposed to go into the thread of the message that triggered them. In your case they were posted as new top-level messages, while the agent was told they had gone into the thread. That would explain why it kept saying it had replied in the thread when it hadn’t. Whether the channel uses the Threads or Posts layout doesn’t seem to matter here. I’ve passed this to the team with your agent ID.
The Cursor Teams app does ask for permission to read channel messages when it’s installed. The limit is in the tools we give automation agents: the Teams read tool can only open a specific thread by its message ID, and there’s currently no tool for browsing recent messages in a channel.
