Forum Discussion
CS agent OK in M365 Copilot; Teams chat silent / no Studio session
We are troubleshooting a Copilot Studio agent that works correctly in Microsoft 365 Copilot and in the Copilot Studio test surface, but does not receive inbound activities from Microsoft Teams personal chat.
Environment and evidence:
- Agent: Copilot Studio agent (custom business assistant)
- Copilot Studio agent ID: 88901b10-… (truncated)
- Teams/Entra app ID: 7e4a53cc-… (truncated)
- Manifest version: 1.0.8
- Channel configuration: Microsoft 365 Copilot + Microsoft Teams
- Publish: Succeeded / Channel state: Synchronized
- Agent Registry: Available
- Authentication: Integrated / Tool credentials: Maker-provided
- MCP/custom connector runtime: working (Studio tool test HTTP 200)
- Microsoft 365 Copilot routing: working
Failure specific to Teams:
- Messages in Teams web and desktop appear delivered in the agent personal chat
- Agent never replies
- Studio monitor has M365 Copilot sessions, but no Teams session for those timestamps
- Teams Admin Center Manage apps returns 0 results by name or exact app ID despite Agent Registry Available
- Intentionally not republishing / reconnecting OAuth / rewiring connectors because M365 Copilot path proves the same agent+connection works
Classification: FAIL — Teams inbound activity is not reaching the Copilot Studio agent.
Questions focused on Teams delivery:
1. Why would Teams personal 1:1 messages never create a Studio conversation while M365 Copilot does?
2. Is a missing TAC Manage apps row expected under Unified App Management when Registry shows Available?
3. Known gaps: Agent Registry Available + channel Synchronized, but Teams client chat bound to a non-runtime endpoint?
4. Best diagnostic if Monitor shows 0 Teams sessions after a confirmed client send?
Looking for production experience / documented workaround. Redacted evidence available; no tokens/secrets.
1 Reply
The agent working in Microsoft 365 Copilot but remaining silent in a personal Teams chat indicates that the published agent is healthy while the Teams channel or app route is not reaching Copilot Studio. Republish the latest version, then verify that Microsoft Teams and Microsoft 365 Copilot is connected under Channels. Use the channel’s availability options to confirm the agent is shared with the affected user or group and that the Teams app was added from the current published package. In the Teams admin center, confirm the app is allowed by the organization’s app permission and setup policies. Remove the personal-chat installation, sign out of Teams, reset or reinstall Teams, and add the agent again. Test in Teams on the web to separate client caching from policy. Because no Copilot Studio session is created, focus on channel publication, app availability, and Teams policy before debugging topics or orchestration.
