Repository navigation
Inventory Planning Fabric: switch Challenges 2-4 to Fabric IQ (deprecated Fabric Data Agent tool) - #563
Merged
Marco Weber (qxsch) merged 3 commits intoOct 21, 2026
Conversation
Foundry's Fabric Data Agent tool is deprecated (greyed out for new agents) and retires on 6 Nov 2026. This is the minimal change to keep the existing hack working for events before then. It does not include the hosted-agent work. - Challenge 2: connect the published Data Agent with Fabric IQ (OneLake Catalog) by selecting it by name, instead of entering a Workspace ID and Agent ID. - Challenges 3 and 4: reuse the existing inventoryhackagent connection. - Challenge 1 and solutions: IDs are now for diagnostics only; Traces tab wording. - Replaced the screenshots that showed the retired tool or old trace view; removed the unused connection-dialog image; images catalogue updated. - The visual workflow in Challenge 5 is unchanged (retires 1 Dec 2026). Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
…rompt Ran the visual workflow with the three Fabric IQ agents through the API. It works end to end: three nodes in about 90 s, Fabric calls in the demand and replenishment nodes, and the multi-turn approval loop waits and then submits on YES. The prompt without a product occasionally makes the Fabric Data Agent fail with a collation conflict (1 of 4 runs); naming Leaf Blower X2 (P004) did not fail in 3 of 3. Use it as in Challenge 3, add a troubleshooting row for the $20 fallback cost, and refer to the Fabric IQ tool in the trace step. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
…sing recommendations Measured the visual workflow over 25 runs. When an earlier node returns no usable recommendation the replenishment node asks for data instead of a proposal (1 of 9 baseline runs). Tell participants to start a new conversation and name the product. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Digvijay (Digvijay)
left a comment
Digvijay (Digvijay)
left a comment
Author
There was a problem hiding this comment.
changes requested by the Danish team
Author
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this changes
In 03-Azure/01-04-AI/02_Inventory_Planning_Fabric, Challenges 2-4 told participants to add Foundry's Fabric Data Agent tool and paste a Workspace ID and Agent ID. That tool is now deprecated and greyed out in the tool catalogue for new agents (it retires on 6 Nov 2026), so participants cannot follow Challenge 2 as written.
This PR is the minimal change to keep the existing hack working: connect the published Data Agent with Fabric IQ (OneLake Catalog) by selecting it by name.
Add -> Add tools -> Fabric IQ (OneLake Catalog), pickinventory-hack-agent(check its Location is your own workspace). Troubleshooting rows updated, including the "deprecated tool" message.inventoryhackagentconnection from the Configured tab.images/README.mdupdated.20 files, text and images only, all in the lab folder. No scripts, provisioning or hosted-agent changes. (A separate hosted-agent replacement for the workflow, which retires on 1 Dec 2026, is not part of this PR.)
Verified (20 Oct 2026, fresh lab: new Foundry account, project and F4 Fabric capacity)
MODIFYandYES(values checked against the seed data: P004 Portland 8, Seattle 6; unit costs $95 / $140 / $85).YES.Not verified - please test before merging
NOandMODIFYon the workflow's replenishment node (onlyYESwas exercised there).Known behaviour (documented, not fixed)
Across about 25 workflow runs, roughly 1 in 8 did not produce a purchase order, usually because an earlier node returned no recommendation table, or the replenishment agent used the
$20fallback price instead of the Fabric cost. Naming the product in the prompt helped, and the lab now says to start a new conversation and check the unit costs.How to test
Follow Challenges 2, 3, 4 and 5 from this branch. Watch for: the Fabric IQ steps matching the portal, unit costs of $95 (P004), and the workflow pausing for approval.