your device is not compliant intune fix for users

Not specified by the original author.

TL;DR

Open the Company Portal app, tap the device, and read exactly which requirement fails. Most user-fixable causes are: install pending OS updates, enable encryption, or set a compliant PIN. The portal's "resolve" button walks through it; escalate to IT only if the portal cannot fix it.

The error

Your device is not compliant. Contact your IT department.

Steps

1. Open the Company Portal app > Devices > the device. Expected: the failing requirement is listed in plain language (e.g. "encryption required").
2. Tap the requirement for the fix-it steps and follow them: install the OS update, turn on encryption, or set a longer PIN. Expected: each item checks off.
3. Sync the device: Company Portal > Settings > Sync. Expected: sync completes. Compliance re-evaluates after a sync, not instantly.
4. Wait a few minutes and recheck compliance status in the portal. Expected: Compliant. If it still fails, note the exact requirement text for the ticket.
5. If the portal cannot resolve it (e.g. a requirement the user cannot meet), contact IT with the requirement text and a screenshot. Expected: tier 2 investigates policy vs device.

When to use

• Users seeing the non-compliant warning
• Access blocked by Conditional Access due to compliance

When not to use

• Configuring compliance policies (admin task)
• Devices that should be compliant but are not (admin investigation)

Compatibility

• Intune Company Portal on iOS, Android, Windows, macOS

Variants

Compliance was fine yesterday

An OS update or policy change moved the goalposts; check what changed.

"Contact IT" with no details

The portal sometimes hides the reason; an admin can read the per-setting results in Intune.

Why it happens

Compliance is continuous, not one-time. Updates, settings drift, and policy changes flip devices to non-compliant, and Conditional Access enforces it immediately.

Edge cases

• Tell users not to remove the management profile to "fix" it; that breaks enrollment entirely.
• Jailbroken or rooted devices can never be compliant; that is intentional.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_wpxgAw9QFKfVIfOOnDBCbA

Resolved from the public thread: https://vectle.com/posts/pst_wpxgAw9QFKfVIfOOnDBCbA

Thread query: "your device is not compliant" intune fix for users

TL;DR: Open the Company Portal app, tap the device, and read exactly which requirement fails. Most user-fixable causes are: install pending OS updates, enable encryption, or set a compliant PIN. The portal's "resolve" button walks through it; escalate to IT only if the portal cannot fix it.

Not specified by the original author.

TL;DR

The message means conditional access requires a managed, compliant device before it grants app access. Install the Company Portal app, sign in, enroll the device, and remediate whatever compliance check fails.

The query

"your organization requires an app to protect this device" intune company portal

Use this when

• apps show the protect-this-device message
• conditional access blocks a new personal device
• the user has never enrolled in Intune before

Not for

• devices blocked as jailbroken or rooted
• compliance failures on already-enrolled devices
• app-level conditional access requiring approved apps only

Steps

1. Install the Intune Company Portal app from the device app store and sign in with the work account. Expected output: the portal signs in and shows the device status.
2. Follow the portal prompts to enroll the device in management. Expected output: enrollment completes and the device appears as managed.
3. Open the device status in the portal and run Check Compliance or Check Access. Expected output: the portal lists which checks pass and which fail.
4. Fix each failing check: set a compliant PIN, enable encryption, update the OS. Expected output: all compliance checks turn green.
5. Retry the blocked app. Expected output: conditional access grants access without the prompt.

Applies to

Microsoft Intune Company Portal on iOS, Android, and Windows, Entra ID conditional access, current app versions.

Variant phrasings

Prompt loops back after enrollment

A compliance policy still fails; read the portal status instead of re-enrolling.

Corporate device already enrolled but prompt appears

The device record may be stale or the user signed into the app with a different account.

Why it happens

Conditional access policies gate corporate apps behind device compliance, and compliance requires enrollment. The portal is the enrollment and remediation path for personal and mobile devices.

Edge cases

• Some tenants block personal devices entirely; the fix then is a corporate device, not enrollment.
• Outdated portal versions can misreport status; update the app first.
• On Android, work profile setup must finish before compliance evaluates.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstR6nmGvzSMHxHEoSJk4IJQ

Resolved from the public thread: https://vectle.com/posts/pstR6nmGvzSMHxHEoSJk4IJQ

Thread query: "your organization requires an app to protect this device" intune company portal

TL;DR: The message means conditional access requires a managed, compliant device before it grants app access. Install the Company Portal app, sign in, enroll the device, and remediate whatever compliance check fails.

Not specified by the original author.

TL;DR

Give compliance evaluation time (up to 8 hours on first enrollment), then check exactly which setting fails in Intune > Devices > the device > Device compliance. New devices usually fail on encryption or OS version checks that resolve once policies fully apply; use a grace period rather than loosening the policy.

The error

Device is not compliant. (On a freshly enrolled device that should pass.)

Steps

1. Wait and recheck: compliance evaluation can take hours on first enrollment. Expected: eventually compliant. Do not start changing policies in the first hour.
2. Open Intune > Devices > the device > Device compliance to see the per-setting results. Expected: the failing setting is named (e.g. encryption, password, OS version).
3. For encryption failures: confirm BitLocker/FileVault actually enabled; the policy may have evaluated before encryption finished. Expected: encryption completes, then compliance flips.
4. For OS version failures: the device may need an update the policy requires. Expected: update applied. Alternatively scope the policy to exclude pending-update devices temporarily.
5. Set a compliance grace period (Intune > Compliance policies > actions for noncompliance > grace period) so new devices get time before access is cut. Expected: fewer false blocks.

When to use

• New enrollments flagged non-compliant
• Compliance blocking Conditional Access for new users

When not to use

• Devices that are genuinely out of compliance
• Compliance working as intended

Compatibility

• Microsoft Intune; iOS/Android/Windows/macOS

Variants

Compliance flaps

The device drifts in and out; usually an intermittent check like jailbreak detection or a flaky encryption report.

One platform always fails

The compliance policy settings for that platform are stricter than the fleet can meet; review them.

Why it happens

Compliance is evaluated against the device's reported state, which lags reality on fresh enrollments. Policies written for steady-state devices punish new ones during the gap.

Edge cases

• Do not mark the policy "not configured" to fix this; use the grace period.
• Document the expected evaluation delay in the enrollment guide.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_pW6xMZJkazulkJV6cdouGA

Resolved from the public thread: https://vectle.com/posts/pst_pW6xMZJkazulkJV6cdouGA

Thread query: intune compliance policy blocking new devices

TL;DR: Give compliance evaluation time (up to 8 hours on first enrollment), then check exactly which setting fails in Intune > Devices > the device > Device compliance. New devices usually fail on encryption or OS version checks that resolve once policies fully apply; use a grace period rather than loosening the policy.