Azure Intune Compliance policy Not evaluated Error 65001 (Not applicable)

Recently I’ve been trying to move fully over to InTune for device management and compliance but ran into an issue getting devices to show as compliant in the portal.

Some devices report in fine but others show compliance policies as ‘Not evaluated’ or they show the Default Device Compliance Policy in an error state showing the error state 65001 (Not applicable).

I opened a case with Microsoft support who have confirmed that there is currently an issue with the InTune interface not reporting back properly. If the device shows as ‘Compliant’ in the ‘All devices’ section then the device is truly compliant.

Below shows Office-pc03 as Compliant but if you click onto the device.

Then click on ‘Device compliance’  you will see that the default policy is in an error state and any other policies will show as ‘Not evaluated’. Very confusing right!

If you click into the default policy you will see the error 65001.

As I mentioned above Microsoft support have assured me that if the device shows as compliant on the devices screen then it is compliant. The errors and warnings you see should be ignored and will be fixed soon.

This was confirmed on 10/07/2018 so if more than a couple of months have passed and you are seeing this exact issue then please raise a case with Microsoft support and let us know what they say 🙂

As of 11/04/2019 i’m still seeing reports of this issue!

Author: Ian@SlashAdmin

Share This Post On
468 ad


  1. Hi Ian,

    It appears that the compliance policy is not taking effect on the deice and the option that says that has a compliance policy assigned can be overridden by Intune Compliance policy setting.

    Please navigate to: Intune > Device Compliance > Compliance policy setting and check the first option that says mark devices with no compliance policy assigned as: compliant or not compliant.

    If the compliant option is selected, the 65001 you are getting is an expected message.

    if not, please let me know.

    Post a Reply
    • Hi Ankit,

      According to support the compliance policy is applied but the dashboard is reporting its status incorrectly due to a known issue.

      Thanks for your input on the setting to mark them as complaint is no policy is assigned. This case there is a compliance policy assigned so we don’t want to give a false reading but rather know there is an issue and watch out for it to be resolved 🙂

      Many thanks.

      Post a Reply
  2. We are now currently at 08/04/2019 and still this error is prevailing.
    Shows how much MS does for customers!!

    Post a Reply
    • I have the same issue for some users unfortunately. Hoping on a fix soon

      Post a Reply
  3. Is the account you’re finding this with an Intune admin? Or have Intune RBAC roles? – I’m finding the same problem on a test Android device… as soon as the user I had the issue with was removed from the Intune RBAC role he was assigned to it started to work. I’m finding the same problem with my account as a full service admin, but haven’t tried removing myself from the admin role.

    Post a Reply
  4. Hi, I am still seeing this compliance issue with one of my user. Its 23/5/2019. Owing to this error and the device not being compliant with the 65001 error on Intune platform that affected user is unable to see all the published apps on the phone and is unable to use those, which is user impact for us. Thankfully the number of such users is not high. MS should take this seriously and fix the bug.

    Post a Reply
  5. I am receiving the same error 65001 on a number of devices. I have noticed these devices do not have a user restigered in the UPN field of the compliance page.

    I am using windows 10 1803 managed via intune in a co-management with SCCM

    none of the affected users are RBAC accounts.

    Post a Reply
    • I’d suggest you try targeting/assigning the Compliance Policy to a group with that has the devices in it. For devices that are enrolled without out direct user affinity, a Compliance policy assigned to Users will not be evaluated. This is in the Microsoft docs: https://docs.microsoft.com/en-us/intune/device-compliance-get-started#ways-to-deploy-device-compliance-policies

      On Windows 10 version 1803 and newer devices, it’s recommended to deploy to device groups if the primary user didn’t enroll the device. Using device groups in this scenario helps with compliance reporting.

      Post a Reply
      • In summary, make sure the account is not used to manage Intune to avoid this error.

        Post a Reply
  6. It’s 6/9/2021 and I’m still getting this error on my clients devices. Really taking your time on fixing this eh?

    Post a Reply
  7. 7/22 and still an issue for me also

    Post a Reply
    • Meh
      Still 65001
      6. Sept 2021

      Post a Reply
      • Still happening 15/10/21

        Post a Reply
  8. 11-17-21
    I’m finding this thread because it’s an issue in my environment as well 🙁
    Thanks Micro$oft

    Post a Reply
  9. It’s Christmas time 2021 and humanity still faces the thread of 65001…
    A brave team of sys admins tries to fight back the hordes of compability issues and refuses to give up…

    M$ have mercy with our souls!

    Post a Reply

Submit a Comment

Your email address will not be published.