Forum Discussion
Intune Compliance Policy: Device not compliant because of missing machine risk score: deactivated?
Dear all, I have this curious compliance issue for which I cannot find any information online or on docs.microsoft.com. Any help or suggestions are appreciated. We are testing Windows Defende...
I am having a very similar issue. On my Device compliance policy I am showing "Require the device to be at or under the machine risk score" as not compliant. The device appears to be onboarded but is now showing up in the Windows Defender Security Center Portal. Only machines I have onboarded manually with a script appear there. I have gone through the Intune - WDATP onboarding instructions located here https://docs.microsoft.com/en-us/intune/advanced-threat-protection several times and everything seems to be set correctly. If I look on the device WDATP shows that there are no threats and no action needed. Why is the device not showing up in the console and why am I getting the compliance issue?
Thanks for the comment.
After the initial post in this thread I did not make any more changes due to business travel. After about a week suddenly the machines became compliant. Again: with no changes. Could it be that some process needs to run in the course of about a week before a client really is marked as compliant?
Are you seeing this too?
Best regards,
Wim
Still having issues getting devices to join to WDATP through the Intune process. I have switched to a hybrid deployment because of some of the limitations of transferring all of our GPO settings to Intune. I can join devices using the script. I do not really trust Intune at this point to not mark one of my devices not compliant and cut off the VP while he is out of the office. Not a great feeling. We are going to do more testing with a rollout to IT staff.
RyanReynoldsThanks for the feedback. That is indeed not a comfortable situation to be in. I just checked our device list and they are still marked as compliant, with the exception of one device for another reason.
In any case, the behaviour seems flaky to it would be great if this could be addressed by the Intune team.
