Compliance policies not evaluated for every device in Microsoft Intune.

Deon Williamston 20 Reputation points
2024-03-14T17:46:09.8333333+00:00

Hi, I've recently been tasked with updating all of our endpoints to have Microsoft Defender for Endpoint.

We have upgraded to Business Premium licenses which come the MDE and Intune.

I've successfully onboarded 4 devices for testing through MDE, and the devices appeared within Intune.

But for some reason the devices Device Compliance states: "Not Evaluated" even though I've made a simple compliance policy in Intune and assigned it to a test group with all 4 devices in the group.

I assigned a configuration policy with using the same test group and the policies all succeeded, so not sure what the problem is.

I need help troubleshooting why the compliance policy isn't pushing to these devices.

I've looked online for solutions but haven't found any that work.

Microsoft Defender for Cloud
Microsoft Defender for Cloud
An Azure service that provides threat protection for workloads running in Azure, on-premises, and in other clouds. Previously known as Azure Security Center and Azure Defender.
1,186 questions
Microsoft Intune
Microsoft Intune
A Microsoft cloud-based management solution that offers mobile device management, mobile application management, and PC management capabilities.
4,298 questions
{count} votes

1 answer

Sort by: Most helpful
  1. ZhoumingDuan-MSFT 7,355 Reputation points Microsoft Vendor
    2024-03-15T01:55:17.1033333+00:00

    @Deon Williamston,Thanks for posting in Q&A.

    From your description, I know your devices shown Not Evaluated after assigned device compliance policy.

    To narrow down the issue, please share with us some information.

    1.What is the platform of the device, Windows, Android or iOS?

    2.How did you enroll the devices?

    3.Could you please go to targeted device and sync it manually?

    4.Please check the possible reasons for this state as below.

    Not evaluated: An initial state for newly enrolled devices. Other possible reasons for this state include:

    • Devices that aren't assigned a compliance policy and don't have a trigger to check for compliance.
    • Devices that haven't checked in since the compliance policy was last updated.
    • Devices not associated to a specific user, such as: --iOS/iPadOS devices purchased through Apple's Device Enrollment Program (DEP) that don't have user affinity. --Android kiosk or Android Enterprise dedicated devices.
    • Devices enrolled with a device enrollment manager (DEM) account.

    If there is any unclear, feel free to contact me.

    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.