You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The Azure Policy Set for "deploy-private-dns-zones" contains a parameter called effect1 which is used for only these azure policy definitions;
Hi @SebastianClaesson, the reason there is a different effect is because the Policy engine is case sensitive, and those three policies use a lower case "d", where all the others use an upper case "D" for DeployIfNotExists. While we could update the allowed values for "effect" to include the lower case version, this would be a breaking change for little value (and we would only be able to address this in June/July timeframe.
Describe the bug
The Azure Policy Set for "deploy-private-dns-zones" contains a parameter called effect1 which is used for only these azure policy definitions;
The parameter should be removed and the parameter effect should be used instead across these three policy definitions.
Screenshots
The text was updated successfully, but these errors were encountered: