Clarify managed identity type constraints for Foundry projects - #796
Clarify managed identity type constraints for Foundry projects#796joaocarlossa wants to merge 1 commit into
Conversation
Document that user-assigned managed identity must be configured at Foundry project creation and that changing identity type after creation is not supported.
|
@joaocarlossa : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
1 similar comment
|
@joaocarlossa : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
|
Learn Build status updates of commit 55e0b95: ✅ Validation status: passed
For more details, please refer to the build report. |
There was a problem hiding this comment.
Pull request overview
Clarifies Microsoft Foundry documentation around managed identity constraints for Foundry projects, specifically that user-assigned managed identities must be chosen at project creation and that switching identity types after creation isn’t supported.
Changes:
- Adds an IMPORTANT note under “Project setup” describing the supported timing for user-assigned managed identity configuration.
- Documents that changing a project’s identity type after creation (system-assigned ↔ user-assigned) isn’t supported.
| > [!IMPORTANT] | ||
| > Currently, user-assigned managed identities are supported only when configured during the Foundry project creation. | ||
| > Changing the project identity type after creation isn't supported. This limitation includes changing from system-assigned to user-assigned managed identity, or from user-assigned to system-assigned managed identity. |
|
Can you review the proposed changes? IMPORTANT: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
prmerger-automator
Bot
added
the
aq-pr-triaged
Document that user-assigned managed identity must be configured at Foundry project creation and that changing identity type after creation is not supported.