Co Pilot Studio Agent Integration with Teams and Channels, 1:1 Chat with Agent

Sneha Subramanyan 0 Reputation points
2026-08-25T16:53:19.1533333+00:00

Copilot Studio Agent: Works in 1:1 Chat and M365 Copilot but Not in Teams Channels

Environment:

  • Copilot Studio (latest version, August 2026)
  • Microsoft Teams (desktop and web)
  • Power BI Pro license
  • Dataverse sandbox environment
  • Authentication: Authenticate with Microsoft
  • Knowledge sources: .docx files uploaded directly (Dataverse-backed)
  • Agent has generative orchestration enabled

Issue 1: Agent does not respond in Teams channels

The agent works correctly in:

  • Copilot Studio test panel
  • Teams 1:1 chat (personal scope)
  • M365 Copilot

The agent does NOT respond in Teams channels. Specifically:

  • Agent is added to the channel successfully
  • Greeting message ("Hello! I'm Health KB Assistant. How can I help you today?") appears when the bot is first added
  • When a user @mentions the bot with a query, no response is returned — no error message, no timeout, just silence
  • The greeting is a system topic (no knowledge search). Any query that triggers the knowledge base or generative AI gets no response in the channel
  • Both Teams settings are checked: "Users can add this agent to a team" and "Use this agent for group and meeting chats"
  • Agent has been republished multiple times
  • Bot has been uninstalled, reinstalled, removed from channel, re-added — same behavior
  • No older sideloaded versions exist
  • Authentication is set to "Authenticate with Microsoft" this is required because the agent uses Dataverse-backed knowledge files that need user authentication to access

Question: Is authenticated knowledge search supported in Teams channels? The Microsoft documentation states SSO is available for 1:1 chats but does not clearly confirm channel support. If channel support is not available with "Authenticate with Microsoft," is there a workaround that preserves knowledge base access?

Microsoft Teams | Microsoft Teams for business | Teams and channels | Manage a team or channel
0 comments

3 answers

Sort by: Newest
Most helpful Newest Oldest
  1. Helen Luu 2,785 Reputation points Independent Advisor
    2026-08-25T18:11:59.5233333+00:00

    Hello @Sneha Subramanyan

    Based on the information you provided, it appears that you are experiencing issues while using Copilot Studio. The AI assistance has correctly indicated that knowledge sources requiring end-user authentication are currently not supported in group chats and channel conversations. Connect and configure an agent for Teams and Microsoft 365 Copilot

    However, to ensure you receive the most accurate and professional assistance, I recommend posting your query on the Microsoft Power Platform Community Forum Thread. This platform is specifically dedicated to Copilot Studio and is supported by a knowledgeable group of experts and partners who regularly contribute and share insights. 

    User's image

    I suggest creating a new topic in the Power Platform Community rather than posting in the Microsoft Answers forum. The Answers forum primarily focuses on Microsoft 365-related concerns and has limited resources and expertise in Copilot Studio. By posting in the correct community, you’ll likely receive quicker and more precise guidance. 

    I apologize for redirecting you, but this approach will help ensure that your query is reviewed by the most qualified Copilot Studio specialists and community members.

    Was this answer helpful?

    0 comments
  2. Sneha Subramanyan 0 Reputation points
    2026-08-25T16:59:33.35+00:00

    Issue 2: Power BI connector returns BadGateway / FlowActionBadGateway in Copilot Studio

    When using the "Run a query against a dataset" Power BI connector action in a Copilot Studio topic:

    • The same DAX query works 100% of the time when run directly in Power Automate
    • In Copilot Studio (both test panel and Teams), the connector intermittently returns: Error code: FlowActionBadGateway Error details: The server did not receive a response from an upstream server
    • The failures are inconsistent — sometimes the query succeeds, sometimes it fails with the same query and dataset
    • Power BI workspace is on Pro capacity (not trial)
    • Dataset is small (50 rows, well under any payload limits)
    • Dataverse environment is sandbox type

    Suspected contributing factors:

    • Sandbox environment has a 10 RPM / 200 RPH limit on generative AI messages. Failed attempts may be consuming quota and triggering CooldownActive errors on subsequent attempts
    • The Copilot Studio test panel uses a different invocation path than the published agent, which may explain inconsistency between test and production behavior

    Additional context:

    • Connector payload is well under the 500KB limit
    • No complex variable passing just a hardcoded DAX query string
    • Power BI Pro license is active, workspace confirmed on Pro capacity (not Fabric trial)
    • Dataset refresh is not running during test periods

    Was this answer helpful?

    0 comments

  3. AI answer

    2026-08-25T16:53:37.32+00:00

    Yes. In Teams channels and group chats, authenticated knowledge access is limited.

    For Copilot Studio agents in Teams:

    1. 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.
    2. For agents using manual authentication with Teams SSO, group chats and meeting chats are also not supported.
    3. 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:

    1. Use the agent in Teams 1:1 chat for authenticated knowledge scenarios.
      • This is the supported Teams path for authenticated knowledge access.
    2. Continue using Microsoft 365 Copilot if that surface already works for the same agent.
    3. 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.
    4. 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.

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.