Add AKV vault+key generation guidance #36196
Merged
+11
−7
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
There was a problem hiding this comment.
Pull Request Overview
This PR adds comprehensive guidance for Azure Key Vault setup and key generation to the ASP.NET Core Data Protection configuration documentation. The changes address issue #36045 by providing users with direct links to Azure documentation and clear instructions for configuring key vault permissions and key rotation settings.
Key changes:
- Added hyperlinks to Azure Key Vault creation and key generation quickstart guides
- Included new paragraphs explaining key permissions and automatic rotation considerations
- Enhanced NuGet package references with proper markdown formatting
wadepickett
approved these changes
Oct 9, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #36045
I use links to avoid us having to worry about the portal changing. The links go to ...
In the bullet for "
{KEY IDENTIFIER}," the only change that I'm making there is a slight highlight (italics) of the word "versionless" because they need to be careful not to peg the key to a version with a GUID. The rest of that remains unchanged.I add a paragraph on the key config, calling out key permissions and what to do if they plan to use automatic key rotation.
Internal previews