Skip to content

Migrate AI-03, AI-06, AI-07 labs to Microsoft Foundry pattern#125

Open
theresa-i wants to merge 5 commits into
mainfrom
update-ai-03-06-07-foundry-migration
Open

Migrate AI-03, AI-06, AI-07 labs to Microsoft Foundry pattern#125
theresa-i wants to merge 5 commits into
mainfrom
update-ai-03-06-07-foundry-migration

Conversation

@theresa-i

Copy link
Copy Markdown
Contributor

Summary

Migrates AI-03, AI-06, and AI-07 labs from the legacy Azure OpenAI provisioning pattern to the Microsoft Foundry pattern, consistent with AI-04 (PR #122, merged) and AI-05 (PR #124).

Changes per file

AI-07-LLMOps.md, AI-06-Responsible-AI.md, AI-03-Multi-stage-reasoning.md

Provisioning pattern migration:

  • Replaced Azure OpenAI resource creation steps with Foundry resource + project creation steps
  • Added step to copy the Foundry endpoint from Keys and Endpoint > Foundry tab
  • Updated navigation: "Go to Microsoft Foundry" → "Go to Foundry portal" (actual button label)
  • Added Cloud Shell step to obtain Entra ID access token: az account get-access-token --resource https://cognitiveservices.azure.com

Authentication migration:

  • Replaced API key auth (api_key=) with Entra ID token auth (azure_ad_token=)
  • Environment variable: AZURE_OPENAI_ENDPOINT + COGNITIVE_SERVICES_TOKEN

Model migration:

  • Replaced gpt-4 / gpt-35-turbo with gpt-4.1 (version 2025-04-14, deployment name gpt-4.1)
  • API version updated to "2024-08-01-preview"

Deployment form field fixes (browser-verified against live Foundry UI):

  • Deployment type: StandardGlobal Standard
  • Removed Enable dynamic quota: Disabled (field no longer exists in Foundry UI)
  • Model version and upgrade policy now noted as being under the collapsible Model version settings accordion
  • AI-03 text-embedding-ada-002 deployment: removed Content filter: Default, replaced with Guardrails: DefaultV2

Clean up section:

  • Updated to reference Microsoft Foundry resource instead of Azure OpenAI

Testing

All provisioning and deployment steps were browser-tested against a live Foundry resource (lab5fix, North Central US) to verify UI accuracy.

…ttern

- Replace 'Provision an Azure OpenAI resource' with 'Create a Microsoft Foundry resource and project' section
- Update model deployments to use Foundry portal navigation and gpt-4.1 (2025-04-14)
- Replace API key auth with Entra ID token via az account get-access-token
- Update AZURE_OPENAI_API_KEY/API_VERSION env vars to COGNITIVE_SERVICES_TOKEN
- Replace api_key= / openai_api_key= with azure_ad_token= in all client/LangChain code
- Update api_version to 2024-08-01-preview
- Update Databricks workspace provisioning to reference Foundry resource
- AI-03: update both AzureOpenAIEmbeddings and AzureChatOpenAI for token auth; fix missing comma bug
…pecify Foundry endpoint tab, update project creation wording
- Fix #4: 'Go to Microsoft Foundry' -> 'Go to Foundry portal' (actual button text)
- Fix #5: Deployment type 'Standard' -> 'Global Standard'
- Fix #5: Remove 'Enable dynamic quota: Disabled' (field no longer exists in UI)
- Fix #5: Add note that Model version settings are under collapsible accordion
- Fix #5: AI-03 text-embedding-ada-002: remove 'Content filter: Default', add 'Guardrails: DefaultV2', remove non-existent fields
…rite generic section text, replace image with step-by-step Trace UI instructions
@SkillableKarl

Copy link
Copy Markdown
Contributor

Drat, just a heads-up: while I had no problems using GPT4.1 yesterday, today as I start testing these 4 docs (AI-03-Multi-stage-reasoning.md in this instance) I am finding GPT4.1 displays deprecated and unavailable in the 2 regions referenced in the .md, or as it turns out...any region I've tried. In the past I could swear I recall the very same GPT4.1 showing up as 'deprecated' but was still usable, but that time seems to have ended.

text-embedding-ada-002 deploy seems to be fine for now, so I tested out GPT5 in this lab using the updated instructs, and while I could certainly deploy I ran into another error in Task 'Create a Vector Index and Store Embeddings' Step 2.

image

Oddly, if I changed line openai_api_version="2025-04-01-preview", to openai_api_version="2024-02-15-preview", this seemed to avoid the error. Pressing on in this lab, editing gpt-4.1 where referenced in Notebook to gpt-5, I got to the end successfully I think?

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants