Domain 2 of 3 · Chapter 11 of 15

Integrate a Fabric data agent

Unlock the complete study guide + 1,040 practice questions across 16 full exams.

Bundled into the existing Designing and Building Integrated AI Agent Solutions in Copilot Studio premium course — no separate purchase.

14-day money-back guarantee — no questions asked.

Included in this chapter:

  • A specialist someone else published, over data you never touch
  • What must be true in Fabric before Copilot Studio sees it
  • What the data team built, and why it bounds your answers
  • Adding the connected agent, screen by screen
  • Generative orchestration is the only way to call it
  • Writing the description the orchestrator can act on
  • Whose permissions the query actually runs under
  • What a Fabric data agent will refuse to do
  • Channels, and the Microsoft 365 Copilot gap
  • How this shows up in questions

Three documented surfaces that put a Fabric data agent in front of users

What you compareCopilot Studio connected agentMicrosoft 365 Copilot Agent StoreCopilot in Power BI
Who builds the consuming experienceA maker, in a Copilot Studio main agentNobody; publishing from Fabric is the whole setupNobody; the user picks the agent inside Copilot
What the user actually talks toYour main agent, which delegates analytical questionsThe Fabric data agent itself, in chat or by @mentionCopilot in Power BI, with the data agent attached
What you configureA Microsoft Fabric connection, the agent selection, and a descriptionPublish to Agent Store, plus the publishing descriptionNothing; Copilot search ranks items the user can access
Reaches Microsoft 365 CopilotNot currently supported through a Copilot Studio agentYes; that surface is the point of this routeNo; the surface is Power BI
Can be combined with your own tools and topicsYes, alongside the main agent's other tools and knowledgeNo; the data agent answers on its ownNo; the data agent answers on its own

Decision tree

Is the request a read overgoverned Fabric tables?NoNot a Fabric data agentwrites, documents and fullexports need another mechanismYesMust the call happen at afixed step in an authored topic?YesNot a connected agentno redirect, no instruction referenceuse an agent flow or REST API toolNoWhich surface must users work in?Microsoft 365 CopilotPublish to Agent Storefrom Fabricno Copilot Studio agent in the pathPower BIAttach it in Copilotin Power BInothing for a maker to buildTeams or a websiteDoes the answer need your topics,tools and knowledge around it?NoPoint users at thepublished data agentone agent, several front doorsYesConnect it as a connected agentTeams is the validated channelorchestration routes on the description
Cheat sheet

Cheat sheet

  • Add a Fabric data agent as an external agent
  • Reuse a published Fabric specialist for analytics
  • Disambiguate the Fabric agent with a contextual description
  • Do not redirect to Fabric from a topic
  • Do not explicitly reference Fabric agents in instructions
  • Account for the Microsoft 365 Copilot channel limitation
  • Validate permissions and governed data boundaries
  • Reserve Fabric data agents for read-only structured analysis

Unlock with Premium — includes all practice exams and the complete study guide.

Also tested in

References

  1. Connect a Microsoft Fabric Data agent (Build multi-agent solutions using connected agents in Copilot Studio, training unit)
  2. Fabric data agent creation
  3. Add other agents overview
  4. Consume a data agent in Microsoft Copilot Studio (preview)
  5. Configure Fabric data agent tenant settings
  6. Create a Fabric data agent
  7. Fabric data agent sharing and permission management
  8. Connect to a Microsoft Fabric Data agent (preview)
  9. Consume a data agent from Microsoft 365 Copilot (preview)
  10. Consume a data agent from Copilot in Power BI (preview)