-
Notifications
You must be signed in to change notification settings - Fork 964
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Misconfigured Policy Definition #864
Comments
Fix was proposed in Azure/terraform-azurerm-caf-enterprise-scale#201 by @marcusfriede but have transferred issue to source repository and closed the original PR so we can make the update here. |
This was referenced Nov 25, 2021
ghost
locked as resolved and limited conversation to collaborators
Jan 11, 2022
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Community Note
Versions
terraform: 1.0.5
azure provider: 2.76.0
module: 0.4.0 (Policy definition looks same as in 1.0.0)
Description
Describe the bug
I was doing a check for our Landing Zone Policies and noticed a misconfiguration in one of the policy definitions.
Initiative Definition "Deploy Diagnostic Settings to Azure Services" has a policy called "Deploy Diagnostic Settings for Automation to Log Analytics workspace". This policy enables diagnostic settings for Automation Account created by the module. Policy is shown as non-compliant, even though i had done the remediation successfully.
Expected Output
Expected output is that the policy should be compliant.
Actual Output
Policy is non-compliant even though the remediation was done successfully.
Steps to Reproduce
Screenshots
First screenshot shows the diagnostic settings and the policy compliance after running the remediation.
Second screenshot show the diagnostic settings and the policy compliance when remediation is run and AuditEvent category is enabled manually.
Additional context
Policy will be shown as compliant, if AuditEvent option is chosen in Diagnostic settings of the Automation Account.
The problem would be solved if AuditEvent option is enabled in the policy definition.
The text was updated successfully, but these errors were encountered: