Skip to content

fix: Refactor AI Foundry Deployment to Use Resource ID Instead of Name and RG #532

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Aug 8, 2025

Conversation

UtkarshMishra-Microsoft
Copy link
Contributor

@UtkarshMishra-Microsoft UtkarshMishra-Microsoft commented Aug 6, 2025

Purpose

This update modifies Bicep templates and deployment scripts to replace separate AI_FOUNDRY_NAME and AI_FOUNDRY_RG_NAME parameters with a single AI_FOUNDRY_RESOURCE_ID.
Key changes include:

Updated Bicep outputs to provide aiFoundryId instead of name/RG.

Adjusted script arguments and environment variable fallbacks to use aif_resource_id.

Removed redundant Azure CLI calls for retrieving resource ID.

Improved cross-subscription compatibility and reduced complexity in deployment scripts.

Does this introduce a breaking change?

  • Yes
  • No

Golden Path Validation

  • I have tested the primary workflows (the "golden path") to ensure they function correctly without errors.

Deployment Validation

  • I have validated the deployment process successfully and all services are running as expected with this change.

What to Check

Verify that the following are valid

  • I have built and tested the code locally and in a deployed app
  • For frontend changes, I have pulled the latest code from main, built the frontend, and committed all static files.
  • This is a change for all users of this app. No code or asset is specific to my use case or my organization.

Other Information

@UtkarshMishra-Microsoft UtkarshMishra-Microsoft changed the title BugFix-21522 fix: Refactor AI Foundry Deployment to Use Resource ID Instead of Name and RG Aug 6, 2025
@Prajwal-Microsoft Prajwal-Microsoft merged commit 7c4ea83 into dev Aug 8, 2025
4 checks passed
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