Power Platform Community Forum Thread Details

Issue description

I have built a custom agent called Inventory Eureka Sentinel using Microsoft Copilot Studio. The agent works correctly when accessed through the Microsoft Teams channel — it answers questions like "how many opportunities were created in 2026?" with accurate data and formatted tables.

However, when I try the same question in M365 Copilot (BizChat / Microsoft 365 Copilot interface), the agent responds with: "Sorry, I wasn't able to respond to that. Is there something else I can help with?"

The agent is connected to a data source and uses Topics/Actions to query it. It works perfectly in Teams but fails silently in M365 Copilot.

What I have verified

✓ Agent is published and active in Copilot Studio
✓ Teams channel is connected and working correctly
✓ M365 Copilot channel appears to be enabled in channel settings
✗ M365 Copilot / BizChat does not respond with data — only generic fallback message

Categories:

Building Copilot Studio chatbots in Microsoft Teams

General topics

Copilot Studio skills development

Publish & channel management

Hello SV-27040147-0,

Your issue is most likely due to a mismatch between how your Copilot Studio agent is configured and how Microsoft 365 Copilot (BizChat) executes agents compared to Teams. Even though the agent works correctly in Teams, BizChat is falling back because it either cannot access the agent properly, cannot invoke its topics/actions, or is blocked by authentication/permissions or availability settings. In Microsoft 365 Copilot, simply enabling the channel is not enough—you must ensure the agent is fully published, properly distributed (for example, available to users or approved by an admin), and accessible in a new session after publishing.

Additionally, authentication and tool execution behave differently in BizChat: if your agent uses actions that require user or maker credentials, incorrect authentication settings (such as “No authentication” or missing consent) can prevent those actions from running, leading to a silent fallback. Another common cause is that the user query does not correctly trigger a topic or is not recognized as a “handled” response, which causes the system to default to the fallback message instead of returning your formatted output.

In short, this is typically not a bug in your logic but a deployment/context issue in Microsoft 365 Copilot—most often related to agent availability, authentication, or action execution differences between Teams and BizChat.

Reference Document-
1.Key concepts - Publish and deploy your agent - Microsoft Copilot Studio | Microsoft Learn
2.Publish Agents for Microsoft 365 Copilot | Microsoft Learn
3.Copilot Studio Agent keeps going to fallback message