-
Notifications
You must be signed in to change notification settings - Fork 111
Update how-to-configure-key-rotation.md #107
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 a note section to ensure both the key versions are in enabled state so ACR can automatically apply the new version of the key.
@AbhishekG0509 : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
Learn Build status updates of commit fb3f511: ✅ Validation status: passed
For more details, please refer to the build report. |
Can you review the proposed changes? IMPORTANT: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
@msmbaldwin Could you review this proposed update to your article and enter Thanks! |
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 #sign-off in a comment if it's ready to merge? Thanks! |
Invalid command: '#sign-off'. Only the assigned author of one or more file in this PR can sign off. @msmbaldwin |
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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR adds documentation to clarify the proper state management for key versions during manual key rotation in Azure Key Vault. The change helps users understand the correct process for rotating customer-managed keys used with Azure Container Registry (ACR).
- Added a note section explaining the required key version states during manual rotation
- Clarified the process for safely disabling old key versions after ACR updates
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
I sent an email to the content owner today. @MicrosoftDocs/public-repo-pr-review-team |
Added a note section to ensure both the key versions are in enabled state so ACR can automatically apply the new version of the key.
https://learn.microsoft.com/en-us/azure/key-vault/keys/how-to-configure-key-rotation#key-rotation-policy