Forum Discussion
Microsoft Intune - "Device Compliance Policy" error codes
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.
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 StableGuy) with remark Not applicable, as seen in your screenshot as well. Microsoft seems to be aware and will push a fix.
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.
I have the same error in Aug 2020. It seems to be quite some time..
Were you able to get this resolved?
Regards,
Sudipta
Batish1Microsoft
Here is a workaround suggestion for it
https://docs.microsoft.com/en-us/troubleshoot/mem/intune/win10-devices-show-incorrect-compliance-status#workaroundWhen i check the device it mentioned there is no license found. This device is the 2nd device(OSX, first is windows) enrolled to myself using a E5 license. It should allow up to 5 devices
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.
Chandramohan Gangaiah same problem
- o_O
yep, same sh*t - different day....
3,5 years now...I have the same error. Please update this thread. thanks!
