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:

1. Anyone seen agents that work in M365 Copilot but receive no personal-chat activities from Teams?

2. Can Agent Registry show Available while TAC Manage apps has no matching row?

3. Known Unified App Management sync issues for Copilot Studio agents?

4. Separate Teams app catalog deployment/approval required when Teams channel shows Synchronized?

5. Which logs prove whether Teams attempted to route the inbound activity?

6. Known manifest / personal scope / app-centric management / conversation-binding issues with this split?

Looking for confirmed production experience or documented workaround. Redacted screenshots available; no tokens/secrets.