Skip to content

Clarify that an ID is required for user-assigned managed identity - #4393

Merged
Jiashuo Li (jiasli) merged 1 commit into
MicrosoftDocs:mainfrom
jiasli:uami
Jul 1, 2024
Merged

Jiashuo Li (jiasli) merged 1 commit into
MicrosoftDocs:mainfrom
jiasli:uami

Conversation

@jiasli

Copy link
Copy Markdown
Contributor

Corresponds to Azure/azure-cli#29198

@learn-build-service-prod

Copy link
Copy Markdown
Contributor

Learn Build status updates of commit e932dce:

✅ Validation status: passed

File Status Preview URL Details
docs-ref-conceptual/authenticate-azure-cli-managed-identity.md ✅Succeeded View

For more details, please refer to the build report.

For any questions, please:

az login --identity
```

If the resource has multiple user assigned managed identities and no system assigned identity, you must specify the client ID or object ID or resource ID of the user assigned managed identity with `--username` for login.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

  1. Even if the resource has only one user-assigned managed identity, an ID should be specified.
  2. This is not related to system-assigned managed identity. Even if the resource has a system-assigned managed identity, we can still use the user-assigned managed identity by specifying an ID.

@jiasli Jiashuo Li (jiasli) changed the title {Profile} Clarify that an ID is required for user-assigned managed identity Clarify that an ID is required for user-assigned managed identity Jul 1, 2024
@jiasli
Jiashuo Li (jiasli) merged commit beccf41 into MicrosoftDocs:main Jul 1, 2024
@jiasli
Jiashuo Li (jiasli) deleted the uami branch July 1, 2024 10:47
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.

4 participants