Fabric Data Agent in Foundry: Move to Fabric IQ by Nov 6

Does a Foundry agent of yours still call a Fabric data agent as a custom tool? Then it must move to the Fabric IQ tool before November 6, 2026. Microsoft announced on the Fabric blog that the earlier integration is no longer supported from that date. The replacement is in preview, and it changes how an agent finds and connects to data agents. So when do you act? Now, if any Foundry agent uses a Fabric data agent as a custom tool. Add the new tool, rewrite the instructions, save, and test each data agent with a question. Test one that needs two of them, too. When don't you need this? If no Foundry agent of yours calls a Fabric data agent, there's nothing to move. And check the blockers early: cross-geo processing and storing for AI must be turned on, and your workspace must be in a region with the full Fabric stack. If either is a policy problem, that's a conversation to start before the date, not after. ■ Chapters: 0:00 The announcement 0:26 How it was done before 1:05 How it works 3:00 When to use it, and when not 3:41 Status, licensing and links ■ Status: ▸ Public preview at the time of publishing; details can change before general availability. ■ Sources: ▸ Announced on the Microsoft Fabric Blog: Retiring the Fabric data agent custom tool in Microsoft Foundry: move to Fabric IQ https://community.fabric.microsoft.com/t5/Fabric-Updates-Blog/Retiring-the-Fabric-data-agent-custom-tool-in-Microsoft-Foundry/ba-p/5374418 ▸ Microsoft Learn: https://learn.microsoft.com/fabric/data-science/data-agent-foundry-fabric-iq ■ Go deeper: ▸ Fabric Periodic Table, Data Agent: https://www.fabricperiodictable.com/#element-data-agent ■ About the series: What It Means for Your Architecture. One Microsoft Fabric announcement per film: what it changes in an architecture decision, when to use it, when not, and what it costs. → Questions, or an announcement you want explained next? Send me a direct message on LinkedIn. Parts of this recording were voiced by a machine.