refactor: Updated Foundry Roles name#851
Merged
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
This PR rebrands all user-facing references to the Azure RBAC role with ID 53ca6127-db72-4b80-b1b0-d745d6d5456d from "Azure AI User" to "Foundry User" across documentation, Bicep modules, and local-dev scripts. It also picks up an incidental regeneration of infra/main.json (new Bicep compiler version, refreshed template hashes, and a reordering of two dependsOn entries for private DNS zones).
Changes:
- Rename role label "Azure AI User" → "Foundry User" in docs, Bicep comments, and script log/error messages.
- Regenerate
infra/main.jsonwith Bicep 0.43.8.12551 (new template hashes, minordependsOnreordering). - No functional code changes; role GUID
53ca6127-db72-4b80-b1b0-d745d6d5456dis unchanged.
Reviewed changes
Copilot reviewed 7 out of 7 changed files in this pull request and generated 4 comments.
Show a summary per file
| File | Description |
|---|---|
| docs/LocalDevelopmentSetup.md | Updates troubleshooting heading and the --role argument in manual az role assignment create examples. |
| infra/main.bicep | Updates inline comments next to role assignment entries. |
| infra/main_custom.bicep | Same comment updates as main.bicep for the custom variant. |
| infra/modules/deploy_foundry_role_assignment.bicep | Updates two header comments; symbol names retained. |
| infra/main.json | Regenerated ARM output: new bicep version/template hashes and reordered DNS zone dependsOn. |
| scripts/local_dev.sh | Updates print messages in ensure_azure_ai_user_role. |
| scripts/local_dev.ps1 | Updates Write-Info/Success/Error messages in Ensure-AzureAIUserRole. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Prajwal-Microsoft
approved these changes
May 19, 2026
Contributor
|
🎉 This PR is included in version 2.6.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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.
Purpose
Role naming consistency updates:
All documentation and code comments now refer to the "Foundry User" role instead of "Azure AI User" to match the official role name. This includes updates in
docs/LocalDevelopmentSetup.md, Bicep modules, and comments ininfra/modules/deploy_foundry_role_assignment.bicep. [1] [2] [3] [4] [5] [6] [7]All user-facing messages and logging in local development scripts (
scripts/local_dev.shandscripts/local_dev.ps1) have been updated to use "Foundry User" instead of "Azure AI User". [1] [2] [3] [4]Infrastructure and template updates:
The Bicep-generated ARM templates (
infra/main.json) have updated metadata to reflect the new Bicep compiler version and template hashes. [1] [2] [3] [4] [5] [6] [7] [8]The dependency order for private DNS zones in the ARM template was corrected for improved deployment reliability.
Does this introduce a breaking change?
Golden Path Validation
Deployment Validation
What to Check
Verify that the following are valid
Other Information