Skip to content

Document resource ID and object ID usage with ManagedIdentityCredential #37573

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

Closed
scottaddie opened this issue Sep 25, 2024 · 0 comments · Fixed by #37595
Closed

Document resource ID and object ID usage with ManagedIdentityCredential #37573

scottaddie opened this issue Sep 25, 2024 · 0 comments · Fixed by #37595
Assignees
Labels
Azure.Identity Client This issue points to a problem in the data-plane of the library. Docs
Milestone

Comments

@scottaddie
Copy link
Member

The Azure Identity README currently only shows how to use a client ID with a user-assigned managed identity. See https://github.com/Azure/azure-sdk-for-python/blob/main/sdk/identity/azure-identity/README.md#authenticate-with-a-user-assigned-managed-identity. Expand this section to provide 2 more examples:

  • object ID
  • resource ID

Here's an example of how .NET documents it: https://github.com/Azure/azure-sdk-for-net/blob/main/sdk/identity/Azure.Identity/README.md#examples-1

@scottaddie scottaddie added Docs Client This issue points to a problem in the data-plane of the library. Azure.Identity labels Sep 25, 2024
@scottaddie scottaddie added this to the 2024-10 milestone Sep 25, 2024
@scottaddie scottaddie moved this from Untriaged to In Progress in Azure Identity SDK Improvements Sep 25, 2024
@github-project-automation github-project-automation bot moved this from In Progress to Done in Azure Identity SDK Improvements Sep 27, 2024
@github-actions github-actions bot locked and limited conversation to collaborators Dec 26, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Azure.Identity Client This issue points to a problem in the data-plane of the library. Docs
Projects
Development

Successfully merging a pull request may close this issue.

3 participants