Nov 07 2018 09:21 PM
Nov 07 2018 09:21 PM
I see different error codes "Device Compliance Policy". I am unable to find resolution for the error codes.
Could you please me with resources where I can learn about "Device Compliance Policy" error codes.
For example I see error code "0xfde9". unable to find any resource about these error codes online.
Nov 08 2018 12:55 AM
I do not have a list of the error code, but what I usually do is translate them to hex or decimal and search around.
HEX 0xfde9 is 65001 in decimal.
Thats the error code for Not Applicable, I see a post about it on "/admin" with the default compliance policy. The conclusion of that post is that MS said it would be solved in the future.
Nov 08 2018 01:30 AM
There currently is an issue with the Intune interface not reporting back the status correctly. If the device shows as "Compliant" in the "All devices" section, the device is compliant. Other errors or warnings should be ignored.
The state details will reveal the code 65001 (like mentioned by @Patrick Stalman) with remark Not applicable, as seen in your screenshot as well. Microsoft seems to be aware and will push a fix.
Jun 01 2019 07:26 AM
I notice this problem is still in effect. I've got this:...and then this:
It seems like this problem has been around at minimum for 6+ months. At least Intune support is among the best for speed. Even still, it's like an alpha beta service that is not discounted accordingly. It should almost be free until they finally have it ready.
Aug 09 2020 05:58 AM
I have the same error in Aug 2020. It seems to be quite some time..
Were you able to get this resolved?
Aug 10 2020 04:19 AM
Aug 16 2020 06:09 PM - edited Aug 16 2020 06:12 PM
I´m new with intune, I connected my device (Windows 10 Home on Leonovo laptop) and notice that Windows Defender options is unavailable due to 'administrator settings'.
Looking at the Intune console (https://endpoint.microsoft.com), I was unable to find what is the policy applyed to this device and then look for a change it; that's why I´m here because de same error on the console.
Dec 15 2020 07:18 AM
@Renato Pereira Having the same issue and wondering what the workaround is. Based on this thread its been 2yrs and MS hasn't sorted it yet.
Jan 07 2021 02:47 AM
Feb 12 2021 11:08 AM