Android - Not Compliant
Hello All, We have some android personal(enrolled with personally owned work profile) and corporate devices (enrolled with Corporate-owned, fully managed user devices) which are not compliant due to "Require the device to be at or under the Device Threat Level". When the devices are enrolled, all the required apps are installed including Microsoft Defender. Employees have to manually provision Microsoft Defender and sync the device and then it becomes compliant. However after a few days it again becomes non compliant. I'm trying to figure out if Microsoft Defender provisioning can be automated and if the devices can be synced automatically on a daily basis and somehow it stays compliant. Thank you for your valuable suggestions and solution. Benny S
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 Defender ATP in combination with Intune compliance policies on a limited amount of devices. We had a first test group of three devices, and a second test group of four devices. So 7 in total. In Intune our 'second wave' of test devices is somehow marked as "non compliant" because a violation of our rule that "Require the device to be at or under the machine risk score = clean, low,...". However, these machines are onboarded in Windows Defender ATP and are showing to have no issues. In Intune the table in Device Compliance -> Device Compliance shows that for these machines the Device Threat Level is "Deactivated". (Our other test machines report "Secured", machines outside the test group are reporting "Unknown".) I cannot find any documentation where this state of "deactivated" is discussed. We identified three other differences between or first test group and the second test group: - License level was on Microsoft E3 for the non-compliant machines, instead of E5 - Windows version was 1803 for the non-compliant machines, instead of 1809 - The very first test group was onboarded in Windows Defender ATP using a script. The second non-comliant group was onboarded using a configuration policy in Intune. To test if any of these three differences could have caused the issue I did three separate tests: 1) I moved one user to Microsoft E5, as I understand for Windows Defender ATP this is required. 2) I had one other machine upgraded to Windows 10 1809 3) I ran the manual onboarding script once more on a third machine But none of these machines would be compliant afterwards. I onboarded the first test group to ATP using a script downloaded from ATP. They were active for a few weeks with just the ATP link. I then assigned both the compliance policy and the final ATP configuration at the same time to this first group. The second group was onboarded by the ATP configuration policy in Intune. I assigned the identical compliance policy a day later. I assume that the compliance check fails because the machines do not communicate their threat level (shown as "deactivated" in the Intune portal) properly. One widget in the device compliance screen does show 5 of the 7 devices to be clean: I do not understand why it counts 5 devices. What with the remaining two? And if these 5 are indeed clean, why do at least two of them (7 minus 5) report as having a threat level "deactivated" and "non-compliant"? Does anyone know why the Device Threat Level of the second test group is "deactivated"? What causes this? How can I solve this? Thanks for your help! Best regards, Wim
