Fabric Data Agent Integration with Copilot Studio Reaches General Availability as a Tool-Based Experience

Microsoft has made its Fabric data agent integration with Copilot Studio generally available. The integration turns Fabric Data Agents into a selectable tool inside Copilot Studio, rather than a separately connected agent, and lets a Copilot Studio agent call enterprise data through the same mechanism it uses for other tools.

The integration works through a new tool-based experience. Developers can select “Add a tool,” search for Fabric, and choose “Fabric IQ Data MCP.” From there, the Copilot Studio orchestrator decides when to invoke the Fabric data agent and when to rely on other knowledge sources or tools. Microsoft says the data agent still executes inside Fabric, respects permissions on underlying data sources, and returns answers grounded in governed enterprise data.

The architectural change is significant: the Fabric data agent becomes one capability among connectors, workflows, and other tools, and multiple Fabric data agents can be combined with other business systems. That is a more composable setup than the earlier preview approach, where a Fabric data agent was added from the Agents category as a connected agent. Microsoft says the change reflects the fact that both Fabric and Copilot Studio have evolved significantly since the integration was first previewed.

The update also ties into the broader Copilot Studio platform changes. Microsoft says Copilot Studio now has a redesigned authoring surface and runtime powered by the GitHub Copilot harness. In that environment, agents can be built, tested, evaluated, published, and monitored from a unified interface, with natural language used to describe agent behavior. For Fabric customers, Microsoft identifies improved orchestration as the main benefit: the harness determines when an agent should reach for enterprise data instead of relying on other tools or knowledge sources.

The announcement does not include independent benchmarks, customer case studies, or details on how the orchestrator decides between Fabric and non-Fabric tools in ambiguous cases. What is clear is the direction: Microsoft is standardizing on a tool-calling model for data access and positioning Fabric as one governed option inside an agent’s broader toolkit.

The new tool-based experience supersedes the earlier connected-agent method, so teams that built agents against the preview integration will need to adjust their approach. Microsoft positions the general availability release as a stronger foundation for deploying data-powered agents across its ecosystem. For production users, the concrete change is a supported, tool-based path from Copilot Studio to Fabric data, with permission checks and execution staying inside Fabric.

No pricing changes, performance characteristics, or limits on the Fabric IQ Data MCP tool are stated. The integration has moved from preview to general availability and changed its integration model in the process.