SystemError when using MCP-based Agent in Microsoft Teams

(1) Share

Report

Posted on by Giridhar_B

Hi everyone,

I’m encountering an unexpected error while using an agent integrated with MCP (Model Context Protocol) in Microsoft Teams.

Error Message:

Sorry, something unexpected happened. We’re looking into it.
Error code: SystemError
ConversationID :
Time(UTC):

Context:
The error occurs when interacting with an agent that uses MCP within Microsoft Teams.
The issue appears intermittently and does not seem tied to a specific input.

Looking for help with:

Possible causes for this SystemError in MCP-based agents
Whether this is a known issue with Teams or MCP integration
Recommended troubleshooting steps (logs, configs, permissions, etc.)
Any fixes or workarounds others have found

Has anyone faced a similar issue while working with MCP agents in Teams?

Any insights or suggestions would be really helpful.

Thanks in advance! 🙏

Categories:

Dynamics 365 general

I have the same question (0)

All responses (2)

Answers (1)

Suggested answer

Anthony Blake 3,092 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi @Giridhar_B

I have encountered similar issues, and found they are usually due to limitations with the current version of the MCP (depending on the product, this was in F&O).

Try to replicate using the test suite inside Copilot studio, there you will be able to see from the logs which step failed, and possibly use prompt modifications to have your agent avoid the same scenario in the future. I have had mixed results prompting to avoid the scenarios, but more successes that not.

Thanks.

Anthony

Was this reply helpful? Yes No
Verified answer

Giridhar_B 31 on at

Like (2)

Report
Copy link

Link copied!

Hi @Anthony Blake,
Thanks for your suggestion. I tried to replicate the issue in Copilot Studio, and everything works correctly within the studio environment. However, after publishing the agent and integrating it with Teams, it functions properly for a few days with all prompts. After that, when we send prompts in Teams, the same type of issue occurs again, but with a different conversation ID.

I came across some online discussions where many people suggested that, to identify the root cause, we need to raise a support ticket with Microsoft and provide the conversation ID. This would allow them to investigate the issue on their backend and provide more details about what went wrong.

Thanks,
Giridhar B

Was this reply helpful? Yes No