GPv1 to GPv2 policy#536
Open
gtrossell-eng wants to merge 1 commit into
Open
Conversation
Author
|
#sign-off |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This contribution adds a Storage policy that identifies legacy GPv1 storage accounts and optionally upgrades them to GPv2 using DeployIfNotExists remediation.
The policy preserves the existing storage account SKU during remediation and supports AuditIfNotExists, DeployIfNotExists, and Disabled effects.
Tested successfully in a sandbox subscription using Azure Policy remediation.