Copilot Studio Agents connected to a Fabric Data Agent fails

(4) Share

Report

Posted on by donniekerr

A Copilot Studio Agent, connected to a Fabric Data Agent, fails to connect when published to m365 Copilot but they connect when opened in Teams.

Agent response with 'Sorry, I wasn't able to respond to that. Is there something else I can help with?' in m365 while same agent responds correctly when same prompt is used with same agent in Teams.

There is no error, so I cannot tell you why it fails.

Just reporting as a potential bug.

Also, there is ongoing bug with the '/' command in the instructions to select tools or agents fails and the agent cannot be published. If you remove the tag, the agent can be published and works. These are related bugs.

Categories:

Publish & channel management

I have the same question (25)

All responses (13)

Answers (0)

Sort by

Suggested answer

Robu1 1,694 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi donniekerr,

Thank your for choosing Power Platform Community.

-If Fabric Data Agent fails in M365 Copilot but works in Teams- Ensure the Fabric Agent returns valid JSON (not HTML). Enable Generative Orchestration in Copilot Studio. Try connecting the Fabric Agent directly instead of via MCP connector.

-If the agent responds with fallback message in M365 Copilot - This may be due to response formatting or authentication differences. Test the agent directly in Fabric to confirm output.

-When publishing fails when using / command in instructions Avoid using slash-prefixed tags in tool/agent instructions. Remove the / to allow publishing.

📚 Microsoft Learn & Community Resources
Microsoft Fabric: Connect Data Agents to Teams with Copilot Studio - YouTube

Consume a data agent in Microsoft Copilot Studio (preview) - Microsoft Fabric | Microsoft Learn

🏷️ Please tag me @Robu1 if you still have any queries related to the solution or issue persists.
✅ Please click Accept as solution if my post helped you solve your issue and help others who will face the similar issue in future.
❤️ Please consider giving it a Like, If the solution was useful in other ways.

If this fixes the issue, please mark as resolved to help others with find it.

Happy to help
Robu1
SuperUser|Moderator
Season 2:2025

Was this reply helpful? Yes No
GrusCanadensis 3 on at

Like (0)

Report
Copy link

Link copied!

@donniekerr does your test window work?

@Robu1 - I’m experiencing the same issue. I’ve followed your troubleshooting steps and reviewed the links you shared, but I wasn't able to resolve the problem. Here is more context about what I'm seeing from our setup.

If Fabric Data Agent fails in M365 Copilot but works in Teams- Ensure the Fabric Agent returns valid JSON (not HTML). Enable Generative Orchestration in Copilot

Studio. Try connecting the Fabric Agent directly instead of via MCP connector.

Our agent works in Teams, but not in 365. The agent also doesn’t respond in the test window. For example, in the YouTube video provided, if we set it up the same way, my question in the blue box would go to the data agent, but it never returns an answer. Here is a screenshot for context of the test pane I'm talking about:

I’ve confirmed that the data agent in Fabric is receiving the request and sending a response. I can see it in the activity log. However, no answers appear in either 365 or the test window. I do see answers in Teams.

Was this reply helpful? Yes No
donniekerr 69 on at

Like (0)

Report
Copy link

Link copied!

Yes, it works fine for me in Copilot Studio Test and in Teams. Just not via m365 Copilot UI

Was this reply helpful? Yes No
MP-18091446-0 2 on at

Like (0)

Report
Copy link

Link copied!

Robu1 I am having similar issues with connecting a Fabric Data Agent. For me the Data Agent is answering the questions but not displaying the answers in the test Window. Also, once I connected to the Data Agent, simple greeting prompts immediately get cancelled, also somtimes the activity screen will say "Waiting for User" but there is no question to follow up on.

This behavior started once I connected to the Fabric Data Agent

Output on the left is correct, but no Message is returned in the test window:

Simple prompts are immediately cancelled:

Was this reply helpful? Yes No
AM-22100906-0 5 on at

Like (0)

Report
Copy link

Link copied!

Hi @MP-18091446-0, @donniekerr did you have any progress in solving this ? We have a similar issue, but with a custom agent - https://community.powerplatform.com/forums/thread/details/?threadid=1c17df0d-9cae-f011-bbd3-7ced8d1ab86c. I was wondering if there is some common pattern here, as we exhausted all our hunches as well

Was this reply helpful? Yes No
MD-28111408-0 2 on at

Like (0)

Report
Copy link

Link copied!

Hi @MP-18091446-0, @AM-22100906-0, did you find any solution? We have started to building the Agent that connected to Fabric and almost in all cases I have the same issue - no output rendered, Even the Fabric output is simple text.

Was this reply helpful? Yes No
SR-13011756-0 Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!
I am also experiencing this issue.

I have two fabric data agents

They are child agents of a copilot studio orchestration agent

It works fine in test pane, works fine in teams

It does not work once I get to a fabric question once deployed to m365 copilot.

Error from m365: "Sorry, I wasn't able to respond to that. Is there something else I can help with?"

I wired up App Insights to track the usage. Following the custom events table, I can see that the request goes all the way through and the BotMessageSend DOES indeed have the right information as passed from the fabric agent back up.

So the error must be coming from between the fabric and copilot studio agent's response and m365 copilot somewhere. It is returning plain text in that event message in the logs, so I am not sure what would be causing the error if there's no problem hitting the back end fabric agents.

channelId: m365copilot

text: The total number of miles driven by all trucks in the available data is **5.61 miles**. If you’d like this broken down by a specific period or fleet, let me know!

Note there's double asterisks around the number of miles and unit of measure to show some formatting, so I wonder if that could be breaking things also as something else to look into? UPDATE: I added instructions to not have formatting characters included, but it did not solve the issue.

Was this reply helpful? Yes No
phoenixpub 4 on at

Like (0)

Report
Copy link

Link copied!

Hi,

We are also experiencing the same issue where on the test chatbox there was no message output but it showing on the transcript.

Microsoft already have tagged this as issue from the Known Issues on the Power Platform Admin center

6027558 | Power Platform admin center

The workaround doesnt make any sense for me.

Was this reply helpful? Yes No
donniekerr 69 on at

Like (0)

Report
Copy link

Link copied!

Many months later and this same m365 UI issue still exists and has not become a major blocker for my clients. Anyone from Microsoft Fabric on this forum? I know I can publish a FDA directly to m365 Copilot now and it works just fine. But, my use case calls for a CSA to orchestrate 2-3 specialist FDAs depending on the prompt.

To clarify one point, this fallback happens immediately, well before any response comes back from the FDA.

Secondly, the /command not working is still a big problem when an FDA is added as a connected agent. It works if another CSA is connected, but not an FDA. I feel like these two problem are related because they both are linked to FDAs only.

I really need this forum to be able to connect to the Fabric team as well since it is solely an FDA issue.

Again, this is costing my clients in a big way and seems to be ignored by Microsoft. And my company is a top Microsoft Partner.

Was this reply helpful? Yes No
AS-12050951-0 2 on at

Like (0)

Report
Copy link

Link copied!

Have the same issue

Mine is worse where only one user gets the message "Sorry, I wasn't able to respond to that. Is there something else I can help with?"

I think it comes down to the instructions - using / in the instructions causes issues - Ive removed any command references as rather copied the link to the subagents and used them in my prompts instead - this helps but again not for one user

Ive subsequently created a whole new agent with the exact same setup, same prompt, same subagents and it works for this user

Honestly this is very very frustrating - there is no way to see logs or issues - Copilot Studio just seems bug ridden and now they have introduced Workflows when the base agents dont work

Was this reply helpful? Yes No