Microsoft Intune - "Device Compliance Policy" error codes

%3CLINGO-SUB%20id%3D%22lingo-sub-283817%22%20slang%3D%22en-US%22%3EMicrosoft%20Intune%20-%20%22Device%20Compliance%20Policy%22%20error%20codes%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-283817%22%20slang%3D%22en-US%22%3E%3CP%3EI%20see%20different%20error%20codes%20%22%3CSPAN%3EDevice%20Compliance%20Policy%22.%20I%20am%20unable%20to%20find%20resolution%20for%20the%20error%20codes.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3ECould%20you%20please%20me%20with%20resources%20where%20I%20can%20learn%20about%20%22%3C%2FSPAN%3E%3CSPAN%3EDevice%20Compliance%20Policy%22%20error%20codes.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EFor%20example%20I%20see%20error%20code%20%22%3C%2FSPAN%3E%3CSPAN%3E0xfde9%22.%26nbsp%3B%20unable%20to%20find%20any%20resource%20about%20these%20error%20codes%20online.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-283817%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EIntune%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMobile%20Device%20Management%20(MDM)%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-283888%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Intune%20-%20%22Device%20Compliance%20Policy%22%20error%20codes%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-283888%22%20slang%3D%22en-US%22%3E%3CP%3EThere%20currently%20is%20an%20issue%20with%20the%20Intune%20interface%20not%20reporting%20back%20the%20status%20correctly.%20If%20the%20device%20shows%20as%20%22Compliant%22%20in%20the%20%22All%20devices%22%20section%2C%20the%20device%20is%20compliant.%20Other%20errors%20or%20warnings%20should%20be%20ignored.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20state%20details%20will%20reveal%20the%20code%2065001%20(like%20mentioned%20by%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F238847%22%20target%3D%22_blank%22%3E%40Patrick%20Stalman%3C%2FA%3E)%20with%20remark%20Not%20applicable%2C%20as%20seen%20in%20your%20screenshot%20as%20well.%20Microsoft%20seems%20to%20be%20aware%20and%20will%20push%20a%20fix.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20title%3D%22source%22%20href%3D%22http%3A%2F%2Fwww.slashadmin.co.uk%2Fazure-intune-compliance-policy-not-evaluated-error-65001-not-applicable%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Esource%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-283875%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Intune%20-%20%22Device%20Compliance%20Policy%22%20error%20codes%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-283875%22%20slang%3D%22en-US%22%3E%3CP%3EI%20do%20not%20have%20a%20list%20of%20the%20error%20code%2C%20but%20what%20I%20usually%20do%20is%20translate%20them%20to%20hex%20or%20decimal%20and%20search%20around.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHEX%200xfde9%20is%2065001%20in%20decimal.%3C%2FP%3E%3CP%3EThats%20the%20error%20code%20for%20Not%20Applicable%2C%20I%20see%26nbsp%3Ba%20post%20about%20it%20on%20%22%2Fadmin%22%20with%20the%20default%20compliance%20policy.%20The%20conclusion%20of%20that%20post%20is%20that%20MS%20said%20it%20would%20be%20solved%20in%20the%20future.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-662791%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Intune%20-%20%22Device%20Compliance%20Policy%22%20error%20codes%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-662791%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F239759%22%20target%3D%22_blank%22%3E%40Ferry%20Jansen%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20notice%20this%20problem%20is%20still%20in%20effect.%26nbsp%3B%20I've%20got%20this%3A%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F116863i80F1CEFD0899B5FE%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22Capture.PNG%22%20title%3D%22Capture.PNG%22%20%2F%3E%3C%2FSPAN%3E...and%20then%20this%3A%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F116864i11FAE3A54B7C7F8B%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22Capture2.PNG%22%20title%3D%22Capture2.PNG%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIt%20seems%20like%20this%20problem%20has%20been%20around%20at%20minimum%20for%206%2B%20months.%26nbsp%3B%20At%20least%20Intune%20support%20is%20among%20the%20best%20for%20speed.%26nbsp%3B%20Even%20still%2C%20it's%20like%20an%20alpha%20beta%20service%20that%20is%20not%20discounted%20accordingly.%26nbsp%3B%20It%20should%20almost%20be%20free%20until%20they%20finally%20have%20it%20ready.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1576315%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Intune%20-%20%22Device%20Compliance%20Policy%22%20error%20codes%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1576315%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F64125%22%20target%3D%22_blank%22%3E%40Jeremy%20Bradshaw%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20the%20same%20error%20in%20Aug%202020.%20It%20seems%20to%20be%20quite%20some%20time..%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWere%20you%20able%20to%20get%20this%20resolved%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERegards%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESudipta%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1577971%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Intune%20-%20%22Device%20Compliance%20Policy%22%20error%20codes%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1577971%22%20slang%3D%22en-US%22%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F753842%22%20target%3D%22_blank%22%3E%40sudiptakp%3C%2FA%3E%20%2C%3CBR%20%2F%3E%3CBR%20%2F%3ENope%2C%20never%20did%20see%20it%20resolve.%20I%20do%20though%20have%20the%20update%20to%20share%20that%20my%20errors%20are%20coming%20from%20one%20of%20two%20compliance%20policies%20-%20one%20assigned%20to%20the%20device%2C%20and%20the%20other%20assigned%20to%20the%20user.%20The%20user%20one%20is%20more%20restrictive%20and%20the%20device%20is%20not%20compliant%20according%20to%20some%20of%20its%20requirements.%20Not%20sure%20if%20this%20the%20reason%20for%20mysterious%20error%20codes%20or%20not%2C%20but%20thought%20I'd%20share%20it.%3CBR%20%2F%3E%3CBR%20%2F%3ELooking%20forward%20to%20the%20day%20that%20policy%2Fprofile%20conflicts%20in%20Intune%20are%20more%20graceful.%20It's%20a%20weird%20stone%20left%20unturned%20for%20sure.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1591896%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Intune%20-%20%22Device%20Compliance%20Policy%22%20error%20codes%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1591896%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%C2%B4m%20new%20with%20intune%2C%20I%20connected%20my%20device%20(Windows%2010%20Home%20on%20Leonovo%20laptop)%20and%20notice%20that%20Windows%20Defender%20options%20is%20unavailable%20due%20to%20'administrator%20settings'.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ELooking%20at%20the%20Intune%20console%20(%3CA%20href%3D%22https%3A%2F%2Fendpoint.microsoft.com%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fendpoint.microsoft.com%3C%2FA%3E)%2C%20I%20was%20unable%20to%20find%20what%20is%20the%20policy%20applyed%20to%20this%20device%20and%20then%20look%20for%20a%20change%20it%3B%20that's%20why%20I%C2%B4m%20here%20because%20de%20same%20error%20on%20the%20console.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1989168%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Intune%20-%20%22Device%20Compliance%20Policy%22%20error%20codes%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1989168%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F90460%22%20target%3D%22_blank%22%3E%40Renato%20Pereira%3C%2FA%3E%26nbsp%3BHaving%20the%20same%20issue%20and%20wondering%20what%20the%20workaround%20is.%20Based%20on%20this%20thread%20its%20been%202yrs%20and%20MS%20hasn't%20sorted%20it%20yet.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2039501%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Intune%20-%20%22Device%20Compliance%20Policy%22%20error%20codes%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2039501%22%20slang%3D%22en-US%22%3ELooks%20like%202%20years%20on%20and%20now%20in%202021%20the%20problem%20still%20exists%20with%20no%20solution%2C%20not%20good.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2129482%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Intune%20-%20%22Device%20Compliance%20Policy%22%20error%20codes%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2129482%22%20slang%3D%22en-US%22%3EHere%20is%20a%20workaround%20suggestion%20for%20it%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Ftroubleshoot%2Fmem%2Fintune%2Fwin10-devices-show-incorrect-compliance-status%23workaround%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Ftroubleshoot%2Fmem%2Fintune%2Fwin10-devices-show-incorrect-compliance-status%23workaround%3C%2FA%3E%3C%2FLINGO-BODY%3E
Occasional Visitor

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.

9 Replies

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.

 

 

 

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. 

 

source

@Ferry Jansen 

I notice this problem is still in effect.  I've got this:Capture.PNG...and then this:

Capture2.PNG

 

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.

@Jeremy Bradshaw 

I have the same error in Aug 2020. It seems to be quite some time..

 

Were you able to get this resolved?

 

Regards,

 

Sudipta

Hi @sudiptakp ,

Nope, never did see it resolve. I do though have the update to share that my errors are coming from one of two compliance policies - one assigned to the device, and the other assigned to the user. The user one is more restrictive and the device is not compliant according to some of its requirements. Not sure if this the reason for mysterious error codes or not, but thought I'd share it.

Looking forward to the day that policy/profile conflicts in Intune are more graceful. It's a weird stone left unturned for sure.

Hi,

 

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.

@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. 

Looks like 2 years on and now in 2021 the problem still exists with no solution, not good.