Repository navigation
Fix Foundry deployment + Foundry User RBAC and add portal links (Inventory Planning Fabric hack) - #478
Merged
Marco Weber (qxsch) merged 3 commits intoSep 3, 2026
Conversation
…hack) The Fabric inventory-planning deploy-lab.ps1 created the Foundry project without a managed identity, ignored REST/provisioning failures (reporting success even on error), and never granted attendees access to Foundry - so Challenge 1 could not be completed and Foundry user RBAC was missing. - Create the project with a system-assigned managed identity and fail clearly on PUT/provisioning errors, waiting until it reaches Succeeded with a principalId. - Grant the Foundry User role at the Foundry account scope to each attendee and to the project managed identity, idempotently with retries. - Require at least one attendee object ID and document the new RBAC behaviour. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
On a freshly-provisioned F2 capacity the Lakehouse SQL analytics endpoint can take a couple of minutes to expose newly-written tables. The setup notebook's publish cell may raise 'No tables were selected (schema may still be syncing)' and the data agent portal may show 'Error updating data agent data source selection(s)' if tables are ticked too early. Both resolve once the schema syncs. Add an explanatory note after Run all and two troubleshooting rows so participants understand the behaviour and know to confirm tables via the SQL analytics endpoint, then re-run the publish cell or tick tables and Publish. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
…d (Fabric hack) The deploy previously returned only the Foundry SDK endpoint and the Fabric capacity name, so the MicroHack platform dashboard had no clickable link to the attendee's Foundry project or the Fabric portal - attendees had to navigate manually. - Add FoundryProjectUrl: a deep-link straight to the attendee's inventory-hack project in ai.azure.com, built deterministically from the subscription (base64url token), resource group, account, project, and tenant. - Add FabricPortalUrl: a link to app.fabric.microsoft.com to create the workspace on FabricCapacityName (the workspace URL cannot exist until the attendee creates it in Challenge 1). - Document both new credentials in labautomation/README.md. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Digvijay (Digvijay)
force-pushed
the
fix/fabric-inventory-foundry-deploy
branch
from
September 2, 2026 22:06
bfc064c to
963b827
Compare
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 & why
Testers of the low-code Inventory Planning with Microsoft Fabric hack (added in #387) reported that the Foundry project wasn't being set up correctly by the deployment pipeline and that Foundry user RBAC was missing — so Challenge 1 couldn't be completed and attendees couldn't build/test agents. This PR fixes the deployment and improves the attendee experience.
Changes
1. Fix Foundry project provisioning + RBAC —
labautomation/deploy-lab.ps1Succeededwith aprincipalId(previously fire-and-forget — it could report success even on failure).2. Document cold-capacity schema-sync behaviour —
challenges/challenge-01.mdNo tables were selected (schema may still be syncing)and the portal may showError updating data agent data source selection(s). Added an explanatory note after Run all plus two troubleshooting rows (confirm tables via the SQL analytics endpoint, then re-run the publish cell or tick tables + Publish).3. Emit clickable portal links to the dashboard —
labautomation/deploy-lab.ps1,labautomation/README.mdFoundryProjectUrl— deep-link straight to the attendee'sinventory-hackproject inai.azure.com(built deterministically from subscription/RG/account/project/tenant).FabricPortalUrl— link toapp.fabric.microsoft.comto create the workspace on the attendee's capacity (the workspace URL itself can't exist until the attendee creates it in Challenge 1).Validation (live)
deploy-lab.ps1against a real subscription: Foundry account, project (with managed identity),gpt-5.4-minimodel deployment, and Fabric F2 capacity all provisioned Succeeded; Foundry User granted to attendee + project MI.inventory-hack-agentData Agent, and confirmed it answers correctly (Portland/Seattle on-hand stock with CRITICAL flags).FoundryProjectUrlmatches the real portal URL byte-for-byte.Microsoft.CognitiveServices/*data action covers both agent CRUD and inference, so the portal Build an agent flow is enabled without an extra role.Builds on #387.