Ab37721 KV Update Effect Names and Initial updates to support policy versioning #1824
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.
Overview/Summary
This pull request includes several updates and improvements to the policy definitions and templates for Azure Landing Zones. The changes primarily focus on updating policy versions, improving display names for policy parameters, and fixing deployment issues.
Policy Updates and Improvements:
Effect
parameters to clearly identify the policy it applies to in the initiativeEnforce recommended guardrails for Azure Key Vault
. [1] [2] [3] [4] [5] [6] [7] [8]2023-04-01
to support policy versioning. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15] [16] [17] [18] [19]Bug Fixes:
eslz-portal.json
to remove the dependency on theidentity
step.Version Updates:
bicep
version and template hash inpolicies.json
.These changes improve the clarity, functionality, and compatibility of the policy definitions and templates used in Azure Landing Zones.
Addresses AB#37721