Troubleshooting Common Custom Policy Issues in Policy Development

If you're looking to troubleshoot common issues with creating Azure custom policies, this blog post is here to guide you through the process. While Azure's built-in policies are useful, custom policies offer a level of flexibility that can't be achieved by the standard offerings. However, developers often run into problems with policy definitions, compliance reports, and alias availability.

The article covers a range of common issues and provides tips and tricks on how to resolve them. One common issue is using an incorrect or nonexistent alias in a policy definition. Developers can use PowerShell Get-AzPolicyAlias command to check the correct policy Alias. Another issue may arise when resources are not found in compliance reports. To fix this, developers are advised to ensure they have provided the correct resource type and that read operation is available in policy definitions.

The article also covers the problem of having incorrect compliance reports and provides tips on how to fix it. To solve this issue, developers will need to check if their policy rule is correct, adjust the policy rules and effects. The blog post also advises that developers report cases where the Alias is not available to the PG team and await further assistance. Lastly, there is the issue of using incorrect Mode in policy definitions. To avoid incompatible resources, developers are advised to always use Mode as "All" in policy definitions.

By following the troubleshooting tips outlined in the article, developers can work around the most common issues and create custom policies with ease.

The post is originally published on Microsoft Developer Community. You can access the full article here.