Designed for Enterprise IT Support & Corporate Environments

Security

Conditional Access Blocked Due to Device Compliance or Location

Diagnose Conditional Access access denials caused by device compliance, network location, or sign-in risk conditions and route to identity/security teams appropriately. This troubleshooting guide is mirrored from the Support Portal knowledge base for quick access in Corporate Tech Fixes.

Severity: HighAdmin Required
Estimated Fix Time

10-20 min

Access Level

Admin Required

Total Steps

9

Author & Verification

Tamem J

IT Solutions Engineer

Last verified: March 3, 2026

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

Tested on Windows 11 23H2Tested on macOS Sequoia 15

Trust Signals

No ratings yet

0 total helpfulness votes

  • Enterprise Microsoft 365 Administration
  • Endpoint Management (Intune, Jamf, Kandji)
  • Identity & Access (Entra ID, Okta)
#conditional-access#entra-id#device-compliance#identity#m365#microsoft#support-kb#windows#macos

Note: “Download as PDF” opens the browser print dialog. Choose “Save as PDF” for a printable runbook copy.

Step-by-Step Resolution

Expand each section as needed

  1. 1

    Symptoms

    Info

    Recommended validation or troubleshooting step

    - Users receive 'You can't get there from here' or policy block messages. - Access works on one device but not another. - Users can sign in but are blocked when opening specific apps/resources.

  2. 2

    Likely Causes

    Info

    Recommended validation or troubleshooting step

    - Device not compliant or not recognized as managed. - Sign-in from restricted location/network or high-risk context. - Conditional Access policy targets specific app/resource conditions.

  3. 3

    Confirm scope, user impact, and reproduction

    Info

    Recommended validation or troubleshooting step

    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.

  4. 4

    Validate prerequisites and application/session state

    Info

    Recommended validation or troubleshooting step

    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.

  5. 5

    Run safe diagnostics from the Commands section

    Info

    Recommended validation or troubleshooting step

    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.

  6. 6

    Apply safe remediation steps

    Info

    Recommended validation or troubleshooting step

    - Capture the exact error message, correlation ID, timestamp, and affected app/resource. - Confirm device management/compliance state and whether the user is on VPN or an external network. - Verify the user is signing into the correct tenant/account and not a guest context unexpectedly. - Escalate to identity/security admins for sign-in log and policy evaluation.

  7. 7

    Escalate when access, policy, or security controls are involved

    Warning

    Review carefully before proceeding

    - Access to critical business systems is blocked and policy review is needed urgently. - Multiple users are blocked after a policy change. - Users propose bypassing compliance/VPN/security requirements to continue work.

    Admin review or admin rights may be required for this step.

  8. 8

    Session and device registration checks

    Command

    Includes a copyable command block

    Command
    # Windows
    dsregcmd /status
     
    # macOS
    date
    scutil --proxy
  9. 9

    When to Escalate to IT / Security

    Warning

    Review carefully before proceeding

    - Access to critical business systems is blocked and policy review is needed urgently. - Multiple users are blocked after a policy change. - Users propose bypassing compliance/VPN/security requirements to continue work.

Related Fixes by Exact Query

High-intent troubleshooting phrases mapped to related internal guides.