Copilot Studio agent works in M365 Copilot but silent in Teams personal chat

Question

Copilot Studio agent works in M365 Copilot but silent in Teams personal chat

Miroslav Pištěk 0

Environment

Microsoft 365 tenant with Copilot Studio agent "Caflou Asistent"
Agent version: 1.0.8
Channels: Microsoft 365 Copilot + Microsoft Teams (both synchronized / published)
Agent Registry: Available
Entra / bot registration appId: 7e4a53cc-f51c-4772-ad93-e3f1e8060f35

What works

Microsoft 365 Copilot agent chat / shareLink:
- Routing PASS
- Agent replies (including OnUnknownIntent / Fallback text)
- Studio sessions appear with channel = "Microsoft 365 Copilot"
Copilot Studio test pane:
- Agent responds
MCP / tools path used by the agent (Maker-provided connection):
- Studio can invoke tools successfully in test scenarios
- Example: getTasks returned HTTP 200 with real data

What fails

Microsoft Teams personal chat (desktop AND web):
- User message is visible in the correct chat titled "Caflou Asistent"
- No agent reply (silence for 1h+ on probes)
Copilot Studio Monitor / sessions:
- Teams channel sessions = 0 for the probe window
- Last 7 days: only sessions with channel "Microsoft 365 Copilot" (e.g. 2 sessions)
- Probes at ~07:16 UTC and ~10:02 UTC (2026-07-23) produced NO Studio session row
Teams Admin Center → Manage apps:
- Search by name "Caflou" = 0 results
- Search by full appId 7e4a53cc-… = 0 results
- Control search (other app) returns results
- Unified App Management banner is present
- Agent Registry still shows Available + Teams channel

Classification so far

FAIL: Teams inbound activity not reaching Copilot Studio agent runtime
NOT OAuth / NOT MCP host / NOT publish button alone (publish succeeded; M365 path proves agent runtime is alive)
Secondary: Registry Available ≠ TAC Manage apps listing (catalog/UAM sync gap?)

Already tried / ruled out (high level)

Confirmed M365 path with TEAMS_ROUTING_OK-style ping → agent replied (Fallback)
Confirmed published bot channels include MsTeams + Microsoft365Copilot
Confirmed Studio tools + Maker connection can work in Studio test
Empty "Instructions" UI field was misleading; SystemPrompt exists in bot configuration
Meta prompts intentionally hit Fallback topic text (by design for unknown intents)

Open questions for the community

Why would Teams personal 1:1 messages never create a Studio conversation while M365 Copilot does?
Is a missing TAC Manage apps row expected under Unified App Management when Registry shows Available?
Any known gap: Agent Registry Available + channel Synchronized, but Teams client chat bound to a non-runtime endpoint?
Best next diagnostic if Monitor shows 0 Teams sessions after a confirmed client send?

Constraints

We do not have a Microsoft Copilot Studio paid support plan (Support Agent cannot open a formal ticket).
Looking for field experience / known product issues / TAC+UAM troubleshooting steps.

0 comments

1 answer

Your answer

Answer 1

Hi @Miroslav Pištěk

Thank you for reaching out.

Based on your description, I agree with several observations that suggest the agent itself is functioning correctly. The agent appears to work as expected in both the Copilot Studio test experience and Microsoft 365 Copilot, including successful tool executions. This indicates that the agent runtime is operational and capable of processing requests successfully.

I also agree that the issue does not currently appear to be related to MCP tool connectivity, authentication, or a failed publish operation, as those scenarios have effectively been validated through successful Microsoft 365 Copilot conversations and tool invocations.

Another important observation is that Teams personal chat messages do not appear to generate corresponding Teams-channel sessions in Copilot Studio Monitor, whereas Microsoft 365 Copilot conversations do. Based on the evidence you've shared, this could suggest that the issue is occurring before the activity reaches the agent runtime.

Regarding the discrepancy between the Agent Registry showing Available and the inability to locate the app under Teams Admin Center > Manage apps, I have not yet found any related documentation that clearly confirms whether this behavior is expected. At this point, the observed behavior appears more consistent with a Teams channel provisioning, registration, synchronization, or routing issue rather than a problem with the agent's prompts, topics, tools, or runtime logic.

As a troubleshooting step, you could consider removing and re-adding the Teams channel, republishing the agent, uninstalling and reinstalling the Teams app, then testing with a new conversation and checking whether a Teams-channel session is created in Monitor.

To help you reach your goal more effectively, I recommend engaging with [GitHub Community Forum] for a deeper technical dive or to connect with individuals who have relevant experience and expertise. Some approaches may behave differently or be restricted depending on your specific environment and configuration. These forums include many experienced developers and Microsoft specialists who can assist with troubleshooting and guidance.

I apologize for redirecting you to a development-focused support channel. As community moderator, I do not have access to your tenant configuration, backend telemetry, or Microsoft internal diagnostic tools. Given these limitations, I cannot definitively determine whether this is a tenant-specific provisioning issue, an app registration matter, or a product-side issue within the Copilot Studio and Microsoft Teams integration layer. My recommendations are therefore based on the available documentation, observed behavior, and publicly accessible resources. That said, I’ll do my best to provide additional insight where possible.

I hope this helps.

If you have any additional concerns, feel free to comment below. I would be more than happy to assist.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.