What two Fabric data agent dates mean for a plant reporting workflow.
Fabric Lab · Issue 10 · By Dave Goyal
Most of you can skip the November 6 date.
Then the one that reaches you anyway: November 2, if your agents run on the standard runtime.
I judge changes like this with a lens I call The Agent Change Runway. Five moves, in date order. Facts first, lens after.
What changed
- Nov 6, 2026: the earlier integration, where a Fabric data agent is added to a Foundry agent as a custom tool (the Microsoft Fabric tool), is no longer supported. Foundry agents using it must move to the Fabric IQ (OneLake Catalog) tool before that date.
- Not on that clock: data agents used in Fabric, Copilot Studio, Microsoft 365 Copilot, or through MCP.
- Nov 2, 2026: Microsoft begins rolling the Advanced NL2SQL and advanced DAX generation improvements to the standard runtime. Microsoft expects the rollout to finish by Nov 10.
- By default: standard-runtime agents get the changes and a model upgrade with no opt-in. Microsoft’s post names the model GPT-5.6 Terra.
- What moves to standard: better example-query following, filter-value substitution, and data exploration (NL2SQL), plus an agentic tool-calling loop and instance value indexing (DAX). Schema descriptions and topics for SQL sources stay in preview.
- Microsoft’s internal benchmark, NL2SQL: smart-answer accuracy goes from 78.8% to 90.9%, and P95 latency from 46.8s to 32.9s. The benchmark ran on the preview runtime, which includes schema descriptions and topics. Those stay in preview, so 90.9% is not a promise for standard.
- Microsoft’s internal benchmark, DAX: accuracy goes from 89.15% to 91.86%, and P50 latency from 39.1s to 20.4s.
- Microsoft’s own caveat: actual results vary.
Nov 6 falls inside the Nov 2 to Nov 10 rollout window, four days after it starts.
What this looks like from here
This is interpretation. The rollout has not started, so I have no field data. Treat it as early signal.
Microsoft frames Nov 2 as an upgrade. NL2SQL accuracy rising 12.1 points is a real gain, if it holds on your data. That is the strongest objection to everything below. Re-testing is insurance, not repair.
I would buy the insurance anyway.
Microsoft says a single-pass generator that guesses wrong still runs the query, and the wrong answer looks like a right one. Microsoft also warns that moving from one-shot generation to an exploring agent “can change how existing instructions and examples are interpreted,” and tells teams to re-run their existing question sets between Nov 2 and Nov 10.
A better average still moves individual answers. Your plant manager cares about the one number on the screen at 6 a.m.
Nov 6 has its own wrinkle. The replacement tool is in preview. Microsoft’s Foundry article says preview items carry no service-level agreement and are not recommended for production workloads. One Learn page also labels the retiring integration preview. So for the teams it hits, this is a preview-to-preview move with a deadline.
The lens
The Agent Change Runway: five moves that get a data agent through Nov 2 to Nov 10 without a surprise.
What to do
1. Inventory every path (this week).
List every way a data agent is reached: Fabric, Microsoft 365 Copilot, Copilot Studio, a Foundry custom tool, a Python app, MCP. Mark which date touches each.
Include the ones that already broke. Copilot in Power BI stopped connecting to data agents on Aug 26, 2026. So did custom apps on Microsoft’s Python sample, which used the OpenAI Assistants API, sunset that day.
2. Baseline before Nov 2.
Run a ground-truth question set through the SDK’s evaluate_data_agent on the current standard runtime and save the results. The evaluation feature is in preview, so read the output, not just the score. Without a baseline you cannot tell drift from noise on Nov 5.
3. Migrate before Nov 6, only if you are on the old Foundry tool.
Microsoft’s portal steps: publish the data agent with a rich description, add the Fabric IQ tool, select the agent, update the Foundry agent’s instructions to name each data agent and its question types, remove the old tool, test. One upside: a Foundry agent can call several data agents, where the old path allowed one.
Check before you start:
- Region. Fabric IQ is not available where Power BI is the only Fabric workload.
- Roles. Foundry User to build and test; Foundry Project Manager to create the connection.
- SDK. Python, C#, JavaScript, and REST work. Java does not. In Python, you need azure-ai-projects 2.2.0 or later.
- Compliance. Responses can leave the Fabric compliance boundary and fall under Foundry’s data terms.
4. Re-test Nov 2 to Nov 10.
Rerun the same set. Compare to baseline. Read the generated SQL and DAX, not just the answer. Tune your examples and the semantic model’s metadata and Prep for AI, because per one Learn page the DAX tool ignores agent-level instructions.
5. Calendar the next dates (this quarter).
Foundry Agents (classic) retire March 31, 2027, per one Learn page. Power BI Q&A is messier. Microsoft Learn says December 2026. The Power BI blog says February 2027. Plan for the earlier date until Microsoft reconciles them.
What we are still watching
Microsoft does not document what a Foundry agent does after Nov 6: hard error, empty answer, or removed tool. I also found no documented way to opt out of, or delay, the Nov 2 to Nov 10 change. The preview runtime lets you try the changes early. It does not hold them back, and one Learn page says model upgrades reach both runtimes.
I will update this when either answer shows up.
What this means for you
If you are not on Foundry: Nov 6 is not yours. Nov 2 is. Run moves 1, 2, and 4.
If you are on the old Foundry tool: you have until Nov 6, and you are moving between two preview tools. Run all five.
For the Nov 2 change, the risk is not an outage. An outage you notice. The risk is an answer that looks right.
So here is my question for you. Which path into your data agents is the one nobody wrote down?
I read every reply.
Dave Goyal
Founder, Think AI Consulting Corporation
Host, The Think AI Podcast
Sources
- Microsoft Fabric Updates Blog, “Retiring the Fabric data agent custom tool in Microsoft Foundry,” October 2026. https://community.fabric.microsoft.com/blog/fbc_fabricupdatesblogs/retiring-the-fabric-data-agent-custom-tool-in-microsoft-foundry-move-to-fabric-i/5374418. Also Microsoft Learn, “Fabric data agent in Foundry,” 2026-10-14. https://learn.microsoft.com/en-us/fabric/data-science/data-agent-foundry
- Microsoft Learn, “Connect agents to Microsoft Fabric with Fabric IQ (preview),” 2026-08-05, updated 2026-10-21. https://learn.microsoft.com/en-us/azure/foundry/agents/how-to/tools/fabric-iq
- Microsoft Learn, “Consume a data agent in Microsoft Foundry (preview),” 2026-10-14. https://learn.microsoft.com/en-us/fabric/data-science/data-agent-foundry
- Microsoft Learn, “Consume Fabric data agent from Microsoft Foundry via Fabric IQ (preview),” 2026-08-26. https://learn.microsoft.com/en-us/fabric/data-science/data-agent-foundry-fabric-iq
- Microsoft Fabric Updates Blog, “Advanced NL2SQL and advanced DAX generation in Fabric data agents,” October 2026. https://community.fabric.microsoft.com/blog/fbc_fabricupdatesblogs/advanced-nl2sql-and-advanced-dax-generation-in-fabric-data-agents-generally-avai/5374654
- Microsoft Learn, “Evaluate your data agent,” 2026-09-01. https://learn.microsoft.com/en-us/fabric/data-science/evaluate-data-agent
- Microsoft Learn, “Fabric data agent runtime,” 2026-10-13. https://learn.microsoft.com/en-us/fabric/data-science/data-agent-runtime
- Microsoft Learn, “Semantic model best practices for data agents,” updated 2026-09-01. https://learn.microsoft.com/en-us/fabric/data-science/semantic-model-best-practices
- Microsoft Power BI Blog, “Power BI Q&A retirement reminder: February 2027 timeline update,” September 2026. https://community.fabric.microsoft.com/blog/fbc_pbiupdatesblog/power-bi-qa-retirement-reminder-february-2027-timeline-update/5365841
- Microsoft Fabric Updates Blog, “Retirement of Fabric data agent integration in Copilot in Power BI,” August 2026. https://community.fabric.microsoft.com/blog/fbc_fabricupdatesblogs/retirement-of-fabric-data-agent-integration-in-copilot-in-power-bi/5328344
- Microsoft Learn, “Consume Fabric data agent from external applications with Python client SDK,” 2026-08-27. https://learn.microsoft.com/en-us/fabric/data-science/consume-data-agent-python
- Microsoft Learn, “How to use the data agents in Microsoft Fabric with Foundry Agent Service (classic),” 2026-03-23. https://learn.microsoft.com/en-us/azure/foundry-classic/agents/how-to/tools-classic/fabric
New here? I write Data and AI Demystified, the hidden costs and reality checks on Microsoft Fabric most partners won’t publish. Subscribe here.
Click here to read Dave’s Demystify Data and AI newsletter on LinkedIn.