Controlling settings, permissions, and membership within Teams and channels
Yes. In Teams channels and group chats, authenticated knowledge access is limited.
For Copilot Studio agents in Teams:
- Knowledge sources that require end-user authentication are not supported in group chats and channels.
- This includes sources such as SharePoint.
- The documented reason is to prevent unintended data exposure.
- These agents are supported only in 1:1 chats.
- For agents using manual authentication with Teams SSO, group chats and meeting chats are also not supported.
- For SharePoint-based generative answers, Authenticate with Microsoft works in Teams 1:1 chats and does not require manual authentication, but this support is explicitly stated as not yet available for group chats or channel messages.
Applied to the described setup:
- The behavior matches the documented Teams limitation pattern: the agent can work in the test pane, Teams 1:1, and Microsoft 365 Copilot, but not return knowledge-based answers in Teams channels.
- The greeting appearing when the agent is added, followed by silence for knowledge or generative queries in the channel, is consistent with channel limitations around authenticated knowledge access.
Workarounds that preserve knowledge access:
- Use the agent in Teams 1:1 chat for authenticated knowledge scenarios.
- This is the supported Teams path for authenticated knowledge access.
- Continue using Microsoft 365 Copilot if that surface already works for the same agent.
- If channel use is required, redesign the channel experience so it does not depend on knowledge sources that require end-user authentication.
- The context does not provide a supported channel workaround that preserves authenticated knowledge access in Teams channels.
- If the knowledge source is SharePoint and the agent was previously published with a different auth mode, reconfigure to Authenticate with Microsoft and republish.
- This improves Teams 1:1 behavior, not channel behavior.
- It can take a few hours to take effect, and users can type "start over" in the chat to force a fresh conversation with the latest version.
For the second issue mentioned in the title, Power BI connector timeouts, the provided context does not contain supported troubleshooting details.