Skip to content

policy-all-users-device-compliance.md

Latest commit

 

History

History
73 lines (53 loc) · 5.67 KB

policy-all-users-device-compliance.md

File metadata and controls

73 lines (53 loc) · 5.67 KB
title How to Require Device Compliance with Conditional Access
description Learn how to enforce device compliance with Conditional Access policies. Ensure secure access to resources by meeting your organization's configuration requirements.
ms.topic how-to
ms.date 03/24/2026
ms.reviewer jodah

Require device compliance with Conditional Access

Overview

Microsoft Intune and Microsoft Entra work together to secure your organization through device compliance policies and Conditional Access. Device compliance policies ensure user devices meet minimum configuration requirements. The requirements can be enforced when users access services protected with Conditional Access policies.

Some organizations might not be ready to require device compliance for all users. These organizations might instead choose to deploy the following policies:

User exclusions

[!INCLUDE active-directory-policy-exclusions]

[!INCLUDE active-directory-policy-deploy-template]

Create a Conditional Access policy

The following steps help create a Conditional Access policy to require devices accessing resources be marked as compliant with your organization's Intune compliance policies.

Warning

Without a compliance policy created in Microsoft Intune, this Conditional Access policy won't function as intended. Create a compliance policy first and ensure you have at least one compliant device before proceeding.

  1. Sign in to the Microsoft Entra admin center as at least a Conditional Access Administrator.
  2. Browse to Entra ID > Conditional Access > Policies.
  3. Select New policy.
  4. Give your policy a name. Create a meaningful standard for the names of your policies.
  5. Under Assignments, select Users or workload identities.
    1. Under Include, select All users
    2. Under Exclude:
      1. Select Users and groups
        1. Choose your organization's emergency access or break-glass accounts.
        2. If you use hybrid identity solutions like Microsoft Entra Connect or Microsoft Entra Connect Cloud Sync, select Directory roles, then select Directory Synchronization Accounts
  6. Under Target resources > Resources (formerly cloud apps) > Include, select All resources (formerly 'All cloud apps').
  7. Under Access controls > Grant.
    1. Select Require device to be marked as compliant.
    2. Select Select.
  8. Confirm your settings and set Enable policy to Report-only.
  9. Select Create to enable your policy.

[!INCLUDE conditional-access-report-only-mode]

Note

You can enroll your new devices to Intune even if you select Require device to be marked as compliant for All users and All resources (formerly 'All cloud apps') using the previous steps. The Require device to be marked as compliant control doesn't block Intune enrollment.

Similarly, the Require device to be marked as compliant doesn't block Microsoft Authenticator app access to the UserAuthenticationMethod.Read scope. Authenticator needs access to the UserAuthenticationMethod.Read scope during Authenticator registration to determine which credentials a user can configure. Authenticator needs access to UserAuthenticationMethod.ReadWrite to register credentials, which doesn't bypass the Require device to be marked as compliant check.

Known behavior

On iOS, Android, macOS, and some non-Microsoft web browsers, Microsoft Entra ID identifies the device using a client certificate that is provisioned when the device is registered with Microsoft Entra ID. When a user first signs in through the browser the user is prompted to select the certificate. The end user must select this certificate before they can continue to use the browser.

B2B scenarios

For organizations you have a relationship with and trust, you might trust their device compliance claims. To configure this setting, see the article Manage cross-tenant access settings for B2B collaboration.

Subscription activation

Organizations that use the Subscription Activation feature to enable users to "step-up" from one version of Windows to another, might want to exclude the Windows Store for Business, AppID 45a330b1-b1ec-4cc1-9161-9f03992aa49f from their device compliance policy.

Related content