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
I noticed that the following Enterprise Scale policy definition remains non-compliant after a remediation task has run:
Deploy Diagnostic Settings for API Management to Log Analytics workspace
To Reproduce
Steps to reproduce the behaviour:
Deploy the Enterprise Scale policy definitions/initiatives
Create a policy assignment for the policy initiative 'Deploy Diagnostic Settings to Azure Services'
Create an API Management Service instance
After a while the API Management instance appears in policy compliance overview as non-compliant
Create a remediation task for the policy Deploy Diagnostic Settings for API Management to Log Analytics workspace.
A diagnostic setting is created but the APIM instance remains non-compliant
Expected behaviour
Diagnostic Setting should be created for APIM instance and APIM instance should be compliant
Screenshots 📷
If applicable, add screenshots to help explain your problem. Please feel free to blur/cover any sensitive information.
Correlation ID
A correlation ID really helps us investigate your issue further. Please provide one if possible. Details on how to find a correlation ID can be found here: Correlation ID and support
Additional context
Anything else we should know to help us troubleshoot this bug?
The text was updated successfully, but these errors were encountered:
Describe the bug
I noticed that the following Enterprise Scale policy definition remains non-compliant after a remediation task has run:
To Reproduce
Steps to reproduce the behaviour:
Expected behaviour
Diagnostic Setting should be created for APIM instance and APIM instance should be compliant
Screenshots 📷
If applicable, add screenshots to help explain your problem. Please feel free to blur/cover any sensitive information.
Correlation ID
A correlation ID really helps us investigate your issue further. Please provide one if possible. Details on how to find a correlation ID can be found here: Correlation ID and support
Additional context
Anything else we should know to help us troubleshoot this bug?
The text was updated successfully, but these errors were encountered: