Data agent and copilot studio agent not answering in test pane

(2) Share

Report

Posted on by YS-12050929-0

Hi everyone,

I have a Copilot Studio agent using generative agent orchestration connected to a Fabric Data Agent.

Problem:

In the Copilot Studio test pane, the final answer from the Fabric Data Agent does not appear in the chat window at all.

All internal activities (DynamicPlanReceived, DynamicPlanStepFinished, final message activity, etc.) are visible in the Activity map.

After publishing to Teams, the agent works perfectly and the response is shown correctly.

I understand that generative orchestration + Fabric Data Agents are still in preview, but not seeing the actual response in the test pane makes debugging extremely difficult, especially when building multi-agent setups.

Has anyone else faced the same issue recently?
Any workarounds, settings, or updates from Microsoft on when this will be fixed?

Thanks in advance!

Categories:

General topics

All responses (3)

Answers (0)

Sort by

MichaelFP 2,008 Moderator on at

Like
a
(1)

Report
Copy link

Link copied!

Can you provide some screenshot that what is happening and what show in the network trace on browser?
Romain The Low-Code... 2,898 Super User 2026 Season 2 on at

Like
a
(1)

Report
Copy link

Link copied!

interested to folow, it's not often when "it work in team but not in copilot studio". I think this is the kind of moment where it's good idea to create a ticket to the official MS support in your tenant :)
YS-12050929-0 9 on at

Like
a
(0)

Report
Copy link

Link copied!

i have uploaded the screenshot also i checked the link for the network issue but it seems the network settings are fine untouched. i think its a copilot studio internal issue for not rendering the response. also the response for hi hello do come and work normally as expected. i have checked on diffrent browser and incognito windows aswell. its leads to same issue.

ref -https://learn.microsoft.com/en-us/troubleshoot/power-platform/copilot-studio/authoring/agent-test-no-response