chore(08,12): scrub tenant identifiers and refresh deep-research outputs#14
Merged
Conversation
Replaced nine tenant-specific UUIDs with the conventional 00000000-0000-0000-0000-000000000000 placeholder, per the notebook-output hygiene policy in CONTRIBUTING.md. Targets: subscription ID, Entra principal IDs, project managed-identity principals, eval-run IDs in portal URLs, and one ACR build volume ID. Files scrubbed: - 08-03-hosted-agents/08-03-01-deploy-hosted-agent.ipynb (2) - 08-05-contoso-pmo-mcp/08-05-01-contoso-pmo-agent-setup.ipynb (1) - 08-05b-contoso-private-banking-mcp/08-05b-01-private-banking-agent-setup.ipynb (1) - 08-06-agent-offline-evaluation/08-06-05-results-and-portal.ipynb (2) - 08-07-agent-live-observability/08-07-01-deploy-observability-infra.ipynb (1) - 12-foundry-iq-deep-research/12-01-deploy-o3-backend.ipynb (2) Deterministic resource-name suffixes (c2676f, n5d3ja) are kept by convention. FOUNDRY_USER_ROLE_ID (53ca6127-...) is kept - it is the public Azure built-in role-definition ID, identical across tenants. Also refreshes cached outputs in 12-01 and 12-02 from a successful end-to-end run after the v0.8.4 / v0.8.5 fixes landed.
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
1 participant
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.
Summary
Two things in one PR:
00000000-0000-0000-0000-000000000000placeholder, per the notebook-output hygiene policy inCONTRIBUTING.md.12-01-deploy-o3-backend.ipynband12-02-deep-research-loop.ipynbfrom a successful end-to-end run after the v0.8.4 / v0.8.5 fixes landed.Scrub targets
08-03-01-deploy-hosted-agent.ipynb5db0aa5d-…08-03-01-deploy-hosted-agent.ipynbdef3c675-…08-05-01-contoso-pmo-agent-setup.ipynb187581c6-…08-05b-01-private-banking-agent-setup.ipynb67bc2a77-…08-06-05-results-and-portal.ipynb3e864d4f-…08-06-05-results-and-portal.ipynbb845d325-…08-07-01-deploy-observability-infra.ipynb5db0aa5d-…12-01-deploy-o3-backend.ipynb025aba94-…12-01-deploy-o3-backend.ipynb5db0aa5d-…Intentionally kept (not personal data)
08-03-01-deploy-hosted-agent.ipynb:53ca6127-db72-4b80-b1b0-d745d6d5456dis the public Azure built-in role-definition ID for "Foundry User" (FOUNDRY_USER_ROLE_ID = …). Identical across all Azure tenants.c2676fandn5d3ja- kept by repo convention so resource names stay readable.Verification
Re-scanned all 33 notebooks in sections 08 / 09 / 10 / 11 / 12 after the scrub. Clean: no real UUIDs remain (excluding the kept role-def ID and the zero placeholder). Also re-confirmed no leaked home paths, 32-char hex keys, or App Insights instrumentation keys / connection strings.
All seven touched notebooks parse as valid JSON post-edit.
Patch release 0.8.6.
Test plan
grep -rE '\b[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}\b'over sections 08-12 returns only cell IDs, the kept role-def ID, and zero placeholders