Skip to content

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

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

apurvghai
Copy link
Member

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.

apurvghai added 2 commits June 3, 2025 11:02
Added changes to clarify System Identity vs Managed Identity explicitly
…llOut

Update tutorial-net-create-vault-azure-web-app.md
Copy link
Contributor

@apurvghai : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

Copy link
Contributor

Learn Build status updates of commit 7e60f22:

✅ Validation status: passed

File Status Preview URL Details
articles/key-vault/general/tutorial-net-create-vault-azure-web-app.md ✅Succeeded

For more details, please refer to the build report.

For any questions, please:

@v-dirichards
Copy link
Contributor

@msmbaldwin

Can you review the proposed changes?

Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

Copy link

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.
Get Help
Docs Support Teams Channel
Resolve Merge Conflict

@v-dirichards
Copy link
Contributor

@msmbaldwin Could you review this proposed update to your article and enter #sign-off in a comment if it's ready to merge?

Thanks!

@github-actions github-actions bot removed the inactive label Jul 2, 2025
@v-dirichards
Copy link
Contributor

@msmbaldwin

Can you review this old PR and determine whether it needs to be closed or merged?

@MicrosoftDocs/public-repo-pr-review-team

@v-dirichards
Copy link
Contributor

I sent an email to the content owner today.

@MicrosoftDocs/public-repo-pr-review-team

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants