02-28-2019 06:40 AM
02-28-2019 06:40 AM
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!
03-06-2019 01:40 PM
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?
03-12-2019 05:41 AM
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?
04-23-2019 03:08 PM
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.
04-24-2019 01:31 AM
@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.
05-27-2019 10:38 PM
I am having the same issue, I have tested this on 6 Win10 computers at this point, it seems that if I Azure AD Domain Join the computers everything works fine, if I Azure AD Register and MDM Manage the device, it will show up as clear or level 1 in WATP poral and as Deactivated in Intune portal.
I've read conflicting information in the documentation, is Azure AD Domain Join mandatory? Seems ridiculous if it is, I mean the Mac client was releases and how are you supposed to deal with BYOD if this is the case? I am working a support case with Microsoft and they are adamant about the fact that MDM Managed devices should report correctly but we have been working the case for 15 days so far and no changes. The strange thing is I can configure ASR, cloud protection, and set any of the other policies with no trouble. This makes it seem it may just not currently work unless the system is Domain Joined and MDM Managed and not Domain Registered and MDM Managed.
If anyone has any details at all, would love to hear them. We have several deals closed with clients to deploy M365 E5 and I want to prepare them if Intune isn't going to show their security status in Intune as this is going to effectively kill our ability to use Conditional Access to limit access based on risk.
06-14-2019 07:34 AM
06-14-2019 12:50 PM
Mine never went compliant, no idea what the heck, everything else works but not that and I can't get support from Defender ATP team to save my life even with a support contract. Intune guys took me through a million steps and were great but even they say it is a DATP issue so I am just sort of stuck. Overally clearly some major issues with the integration still. @Wim Borgers
07-30-2019 04:50 AM
any Updates on this case?
I´ve got a customer with same problems. Device ist not compliant because of: Require the device to be at or under the machine risk score:
Test with different settings (not configured till High) won´t fix this.
Securitycenter shows all devices with no problems.
07-31-2019 11:50 PM
@Markus Dinkel, Same issue here, MS ticket has been open for a few weeks, no clear response.
I've tested by joining a device in Azure AD instead of a hybrid join and then the device reports compliant but as stated in previous messages, Azure AD join shouldn't be a requirement.
10-03-2019 02:02 AM
@Jerod PowellWe are having the same issue with one of our customers, I have had 4 different Intune teams trying to solve it but it looks to be a bug in Defender ATP portal not showing up a threat for the device which causes this issue.
10-03-2019 01:38 PM
@myron helgering I believe the issue typically ends up being the licensed version of Windows 10, we were running Windows Insider builds and for whatever reason they weren't being registered as Windows 10 Enterprise E5, this is what was causing the issue. That said there was no workaround but to load Windows 10 Enterprise E5 without insider builds. This resolved our issue, not an ideal situation though, all sorts of issues we have found with E3 vs. E5 vs. Pro, etc., with Windows 10.
10-04-2019 05:07 AM
@Jerod PowellUhmm this doesn't seem to be related to our problems with the Defender ATP policy. None of the devices run insider builds.
10-16-2019 08:33 AM
@Jerod Powell, do you have an easy way of checking whether or not a machine is properly recognizing the licensing as Windows 10 Enterprise E5? About 80% of our machines are showing this "Deactivated" status and although I'm fairly confident that it's not an OS license issue for us, I'd like to know if there's a simple way to rule it out for sure.
I do have a support case open with Microsoft, but it's moving very slowly as those things do. They always seem to call with about 5 min to go in the workday. I've begun to accept that this is actually done with intent on their end.
10-16-2019 12:25 PM - edited 10-16-2019 06:55 PM
10-16-2019 12:50 PM
10-16-2019 12:53 PM
10-16-2019 12:56 PM
10-16-2019 01:01 PM
@Jerod Powell Mine is somewhat ambiguous and simply states "Windows 10 Enterprise". Similarly, under Settings - Update & Security - Activation it states "Windows 10 Enterprise" and "Windows is activated with a digital license". I assume it's the assigned E5 license, but I don't know for certain.
10-16-2019 01:06 PM
@Philip Kluss To check if you have Windows 10 E5 (or A5 for EDU's), or MTP E5, are you able to login to SecurityCenter.Microsoft.com and see your Windows 10 1607 or newer enrolled there?
10-16-2019 01:08 PM
10-16-2019 06:44 PM
Hi Philip, I was able to reproduce the issue. I edited my first reply on this e-mail thread w/ details on how to make it work. At least in my lab. Give it a try, and hopefully that will help you in your environment too.
10-17-2019 01:15 AM - edited 10-17-2019 01:17 AM
I am the OP of this thread. Just checked the compliance state again and for us it seems the issue is transient. All our machines are Hybrid Azure AD joined.
We do still see machines being reported as 'not compliant'. Some of them have no compliance issue if you look at the policies in detail on the device level, but in the overview list they are still 'not compliant'.
Other are not compliant because one of the policies is not compliant for the system users. Still very confusing. It messes up all the reports and we cannot work with the compliance level at all in policies. :(
10-17-2019 08:08 AM
@Wim Borgers Thanks for checking back in. I've been working with support and the Intune team verified that everything is configured correctly on our end. We, too, are dealing with hybrid Azure AD joined devices that have tons of inexplicable, transient issues regarding device compliance. As of yesterday evening, the Intune team agreed to reach out to the Windows Defender ATP team to figure out why the services aren't talking to each other successfully. The WD ATP dashboard shows all of these devices as healthy, but still our devices are marked Deactivated under Device Threat Level in Intune. I'll report back with any useful findings. Until this works, the whole Zero Trust model of secure network design will remain out of reach for us which is a shame.
10-24-2019 09:42 AM
Even though the ATP <--> Intune connector claims to be healthy and working fine, I had a thought to try to recreate it and have gotten some troubling results. When I toggled off the Connect Windows devices version 10.0.15063 and above to Microsoft Defender ATP option in the Intune settings and I received an error stating "An error occurred. Couldn't establish the connector. Try again later." I receive this error whether I'm toggling it On or Off. Toggling on and off the connector from the Defender ATP portal gives me no errors.
Is anyone else willing to see if they get a similar error when toggling in the Intune portal?
10-24-2019 01:55 PM
@Philip Kluss I dont want to try that but I am having issues onboarding Windows 10 1903 devices to the Microsoft Security Defender Center. I have tried local script, GPO and Intune to try to join the devices and I have had not luck. I tried an 1809 device and it showed up in the Defense Center within 5 minutes. It seems like there are some issues with ATP. All my devices show as Successful for the Microsoft Defender ATP configuration profile- none of the 1903 devices I have tried to add in the last week have made it.