Unanswered

Fabric Data Agent Connector Not Working

(3) Share

Report

Posted on by jamesalthoff

I am trying to connect a Fabric Data Agent to a Copilot Agent in Copilot Studio to publish to Teams. I was able to connect the data agent in the Tools > Model Context Protocol section of Copilot Studio using the workspace and artifact IDs. The Fabric Data Agent has been published and I am an admin in the workspace. I have also verified that I am able to ask questions about my data in the Fabric Data Agent and get good responses. When I try to ask that same question to the Copilot agent, I am getting a "Feature not enabled" error. I have attached a screenshot of the error.

Has anyone else had this issue? How do I get it working?

Categories:

Model context protocol

I have the same question (0)

All responses (3)

Answers (0)

Sort by

RA-02071759-0 2 on at

Like (0)

Report
Copy link

Link copied!

Same issue here... it works in the fabric environment... Feature is not enabled.

Was this reply helpful? Yes No
MF-11071941-0 12 on at

Like (0)

Report
Copy link

Link copied!

SOLVED - see latest post

I had a different issue, I get a 400 error and while I'm sure you are correct that this is not enabled, could you verify where you got the "workspace id" and "artifact id" from? I created an workspace identity to get something to reference, then when I published the fabric data agent, I used the "published url" to derive what appeared to be the artifact ID. E.g. https://api.fabric.microsoft.com/v1/workspaces/329fe518-e9d8-4924-baa0-obfuscated/aiskills/ec725dff-22b0-4922-8489-a8bobfuscated/aiassistant/openai. Notably the workspaces id in the url above is not the same as the workspace identity I created. So could you clarify where you found the values you used for "workspace id" and "artifact id"? I tried using the "dynamically fill with ai" option, but it just prompts you for the "workspace id" and "artifact id".

UPDATED 8/5/2025

This is working if I do not try to connect the co-pilot studio agent to a "tool" called "data agent mcp server", but instead connect to an "agent" select "Fabric" select your already created Fabric data agent connection from there. It seems I attempted this before Microsoft aligned their feature deployments, since I tried this very thing in troubleshooting of my original post, but now it all works. The funny thing, you won't see this error I mention because you cannot directly connect to the "data agent mcp server", you must go through the Fabric agent. Gotta love a preview. See this days old post that helped: https://learn.microsoft.com/en-us/fabric/data-science/data-agent-microsoft-copilot-studio

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

Like (0)

Report
Copy link

Link copied!

Did you get any solution for this issue? I'm also facing the same issue.

Was this reply helpful? Yes No