Skip to content

fix: use AZURE_AI_DEPLOYMENTS_LOCATION for model deployment location#68

Merged
trangevi merged 1 commit into
Azure-Samples:mainfrom
v1212:fix/separate-model-deployment-location
May 22, 2026
Merged

fix: use AZURE_AI_DEPLOYMENTS_LOCATION for model deployment location#68
trangevi merged 1 commit into
Azure-Samples:mainfrom
v1212:fix/separate-model-deployment-location

Conversation

@v1212
Copy link
Copy Markdown
Contributor

@v1212 v1212 commented May 22, 2026

Summary

Updates aiDeploymentsLocation parameter to read from AZURE_AI_DEPLOYMENTS_LOCATION env var instead of AZURE_LOCATION, and adds a default fallback to the main location parameter so existing environments without the new var continue to work.

Changes

  • main.parameters.json: aiDeploymentsLocation${AZURE_AI_DEPLOYMENTS_LOCATION} (was ${AZURE_LOCATION})
  • main.bicep: param aiDeploymentsLocation string = location (default fallback ensures backward compatibility)

Companion PR

Related

Update aiDeploymentsLocation parameter to read from AZURE_AI_DEPLOYMENTS_LOCATION
env var instead of AZURE_LOCATION, and add a default fallback to the main location
parameter so existing environments without the new var continue to work.

Companion to Azure/azure-dev PR for fixing #7670.
Supersedes Azure-Samples#58
Copy link
Copy Markdown
Contributor

@therealjohn therealjohn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks

@trangevi trangevi merged commit 7a699db into Azure-Samples:main May 22, 2026
1 check 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.

Allow developers to deploy when the Foundry project and resource group are in different regions

3 participants