IT Support Portal

ServiceNow-style demo portal

Affiliate Disclosure

Some recommendations may include affiliate links. If you purchase through these links, the site may earn a commission at no additional cost to you. Recommendations are still selected for fit, safety, and support relevance.

Intune Windows Device Not Checking In or Compliance Is Stale

Use this guide when a Windows device stops checking in to Intune, stays noncompliant after the user is back online, or shows outdated policy status in the admin center. It helps you separate transient sync delay from a deeper enrollment or compliance problem.

Estimated time

20-35 min

Overview

A stale Intune device record usually means the endpoint and the service stopped agreeing about the device state, not that the device vanished entirely. The safest approach is to confirm connectivity, Company Portal health, enrollment state, and policy refresh behavior before taking any action that could trigger a needless reenrollment.

Severity: HighAdmin RequiredEnv: WindowsMicrosoftMicrosoft Intune (Windows Device Management)

Author & Verification

Tamem J

IT Solutions Engineer

Last reviewed: March 3, 2026

Runbooks and troubleshooting guides are reviewed for enterprise-safe usage and avoid security bypass patterns.

  • Enterprise Microsoft 365 Administration
  • Endpoint Management (Intune, Jamf, Kandji)
  • Identity & Access (Entra ID, Okta)
Tested on Windows 11 23H2Tested on Windows 10 22H2

Reviewed under Editorial Standards.

Trust Signals

No ratings yet

0 total helpfulness votes

  • Enterprise Microsoft 365 Administration
  • Endpoint Management (Intune, Jamf, Kandji)
  • Identity & Access (Entra ID, Okta)

Reference This Page For

Best use cases

This page is designed to be the narrow, issue-specific reference when the support query, product, and environment closely match.

  • Use this page when the issue is closest to the exact query “intune device not compliant.”
  • Best for Microsoft / Microsoft Intune (Windows Device Management) troubleshooting in Windows enterprise environments.
  • Prefer this ticket when you need enterprise-safe steps, escalation criteria, and commands tied to this specific issue.

Symptoms of intune device not compliant

  • Device last check-in time is stale in Intune admin center.
  • Compliance status remains Unknown or Noncompliant after remediation.
  • Conditional Access blocks user sign-in despite recent device use.

Likely Causes of intune device not compliant

  • Enrollment metadata or device registration state is unhealthy.
  • Enterprise management scheduled tasks are disabled or failing.
  • Local Intune Management Extension is not processing policy queue.

Interactive Decision Tree

ITIL-style triage path powered by state machine logic.

How to Fix: intune device not compliant

Accordion runbook sections

  1. 1

    Confirm scope, user impact, and reproduction

    Info
    v

    Document whether the issue affects one user, multiple users, or multiple devices. Confirm exact error messages, recent changes (password reset, update, network change), and whether the same issue reproduces in web vs desktop workflows where applicable.

  2. 2

    Validate prerequisites and application/session state

    Info
    v

    Confirm the user is signed in with the correct corporate account, system time is accurate, network/VPN connectivity is stable, and the application is not running in offline or limited mode.

  3. 3

    Run safe diagnostics from the Commands section

    Command
    v

    Use the command snippets below to collect non-destructive diagnostics. Capture output in the ticket when escalation may be required. Avoid deleting profiles, cached credentials, or managed app data unless the runbook or admin approval explicitly allows it.

  4. 4

    Apply safe remediation steps

    Info
    v
    • Confirm the device is assigned to the correct user and Intune scope.
    • Run manual sync from Windows Settings and collect timestamped behavior.
    • Validate enterprise management scheduled tasks and Intune extension service state.
    • Escalate before unenrolling/re-enrolling when device is tied to Conditional Access.
  5. 5

    Escalate when access, policy, or security controls are involved

    WarningAdmin required
    v
    • Multiple Windows devices stop checking in after policy rollout.
    • Security compliance controls are not reporting for regulated users.
    • Re-enrollment is required for executive or high-risk user devices.

Commands

Copyable diagnostic or remediation commands (2 snippets).

Check registration and enterprise management task state

PowerShell

dsregcmd /status
Get-ScheduledTask -TaskPath "\\Microsoft\\Windows\\EnterpriseMgmt\\" | Select-Object TaskName, State

Check Intune Management Extension service and recent logs

PowerShell

Get-Service IntuneManagementExtension | Select-Object Name, Status, StartType
Get-Content "C:\ProgramData\Microsoft\IntuneManagementExtension\Logs\IntuneManagementExtension.log" -Tail 150

When to Contact IT / Security

  • Multiple Windows devices stop checking in after policy rollout.
  • Security compliance controls are not reporting for regulated users.
  • Re-enrollment is required for executive or high-risk user devices.

Recommended Partners for This Topic

Selected from your affiliate registry based on this article's category, product family, and tags.

Disclosure: Active partner links may generate commission with no additional user cost.

Was this helpful?

Your response is stored locally in this browser for demo analytics.

Continue With Related Resources

Move from the troubleshooting article into related downloads, broader fix libraries, and pillar guides without restarting your search.