Forum Discussion
Copilot Studio agent suddenly stopped working in Teams
Hello,
I've run into a strange issue with a Copilot Studio agent and I'm trying to understand where to investigate next.
The agent is published to the "Teams and Microsoft 365 Copilot" channel and was working normally in Microsoft Teams until recently.
- The agent still works correctly in Copilot Studio.
- The agent still works correctly in Microsoft 365 Copilot / Copilot Chat.
- The issue only occurs in Microsoft Teams.
What happens in Teams:
- Messages can be sent to the agent.
- No error message is displayed.
- No response is returned.
- Most importantly, no session is created in Copilot Studio (Analytics / Observability).
Because no session is created, it looks like the message never reaches the agent runtime.
What I've already checked:
- Republished the agent.
- Reinstalled the Teams app.
- Verified the Teams and Microsoft 365 Copilot channel configuration.
- Checked permissions and sharing settings.
- Checked Teams Admin Center configuration.
- Tested in both Teams Desktop and Teams Web.
- Reviewed Microsoft 365 service health.
This same tenant has another Copilot Studio agent that works normally in Teams.
The affected agent previously worked in Teams for several weeks before the issue appeared.
The agent architecture is very simple (single MCP server, no custom connectors, no Power Automate involved in this scenario).
At this point, I'm mainly trying to understand why Teams no longer seems to create a conversation/session for this specific agent while the same agent continues to work in Copilot Studio and Microsoft 365 Copilot.
Has anyone seen similar behavior or found a way to diagnose why Teams is no longer forwarding requests to a specific agent ?
Thank you for help
1 Reply
hi CoralieSimonaire The fact that the agent works in Copilot Studio and Microsoft 365 Copilot, but Teams doesn't create any session in Analytics/Observability, is the biggest clue here. It suggests the request may not be reaching the Copilot Studio runtime at all.
Since another agent in the same tenant works normally in Teams, the next area to check would be the Teams channel/app configuration for this specific agent, rather than the MCP server or the agent itself.
A few things worth checking:
- Remove the Teams channel from the affected agent, save the changes, then add and publish the Teams channel again.
- Create a new Teams app/package for the agent instead of simply reinstalling the existing one. This can help rule out stale Teams app or bot registration information.
- Compare the affected agent's Teams channel configuration with the working agent, particularly the app/package and publishing settings.
- Test the agent from a fresh Teams chat or with another user account to rule out cached conversation or app state.
- Check whether the agent's environment, agent ID, or publishing configuration changed around the time the issue started.
At this point, the MCP server may not be the area to troubleshoot. If Teams isn't creating a session at all, it suggests the request isn't reaching the Copilot Studio runtime in the first place, so the MCP tools wouldn't have an opportunity to run.
If removing/re-adding the Teams channel and creating a fresh Teams app doesn't resolve the issue, a Microsoft support case would be the next step. Include the agent ID, environment ID, approximate failure timestamps, and the fact that Teams produces no Copilot Studio session while the other channels continue to work. Those details should give the support team a useful starting point for tracing the Teams-to-Copilot Studio handoff.
The comparison with the other working agent is particularly useful. Comparing the two configurations side by side may reveal a small Teams/channel difference that's otherwise easy to miss.
