-
Notifications
You must be signed in to change notification settings - Fork 102
Clarifying the Use of DefaultAzureCredential with System-Assigned Managed Identity for Azure Key Vault Access #78
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
base: main
Are you sure you want to change the base?
Conversation
Added changes to clarify System Identity vs Managed Identity explicitly
…llOut Update tutorial-net-create-vault-azure-web-app.md
@apurvghai : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
Learn Build status updates of commit 7e60f22: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
Can you review the proposed changes? Important: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
This pull request has been inactive for at least 14 days. If you are finished with your changes, don't forget to sign off. See the contributor guide for instructions. |
@msmbaldwin Could you review this proposed update to your article and enter Thanks! |
Can you review this old PR and determine whether it needs to be closed or merged? @MicrosoftDocs/public-repo-pr-review-team |
I sent an email to the content owner today. @MicrosoftDocs/public-repo-pr-review-team |
This update explicitly calls out the use of system-assigned managed identity as the default authentication method when using DefaultAzureCredential. This clarification helps developers correctly configure RBAC roles for Azure Key Vault access by understanding which identity is being used under the hood. It reduces ambiguity and ensures that the right permissions are granted to the appropriate identity in managed environments.