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
We are using the latest EPAC version and have started managing the MCSB with EPAC. The deploy works as expected and everything looks good in the Azure Policy Blade, but things are inconsistent when looking at the compliance views in Defender for Cloud. Most items reflect as expected, but any compliance items related to Defender for Cloud vulnerability assessments show 0 of 0 resources.
To Reproduce
Enable Defender vulnerability scans for SQL DB, SQL VM, Containers, etc. Deploy MCSB with EPAC. Looks at the compliance in the Policy view and see non compliant resources. Look at regulatory compliance in Defender for Cloud view and see the vulnerability entries show no associated resources.
Expected behavior
Whether we managed the MCSB assignment with Defender or with EPAC the compliance dashboards all report consistently
EPAC Version
10.7.5
The text was updated successfully, but these errors were encountered:
Describe the bug
We are using the latest EPAC version and have started managing the MCSB with EPAC. The deploy works as expected and everything looks good in the Azure Policy Blade, but things are inconsistent when looking at the compliance views in Defender for Cloud. Most items reflect as expected, but any compliance items related to Defender for Cloud vulnerability assessments show 0 of 0 resources.
To Reproduce
Enable Defender vulnerability scans for SQL DB, SQL VM, Containers, etc. Deploy MCSB with EPAC. Looks at the compliance in the Policy view and see non compliant resources. Look at regulatory compliance in Defender for Cloud view and see the vulnerability entries show no associated resources.
Expected behavior
Whether we managed the MCSB assignment with Defender or with EPAC the compliance dashboards all report consistently
EPAC Version
10.7.5
The text was updated successfully, but these errors were encountered: