Microsoft Intune and Microsoft Entra work together to secure your organization through device compliance policies and Conditional Access. Device compliance policies are a great way to 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 complance for all users, these organizations might instead choose to deploy the following policies:
Conditional Access policies are powerful tools, we recommend excluding the following accounts from your policies:
Emergency access or break-glass accounts to prevent lockout due to policy misconfiguration. In the unlikely scenario all administrators are locked out, your emergency-access administrative account can be used to log in and take steps to recover access.
Service accounts and Service principals, such as the Microsoft Entra Connect Sync Account. Service accounts are non-interactive accounts that aren't tied to any particular user. They're normally used by back-end services allowing programmatic access to applications, but are also used to sign in to systems for administrative purposes. Calls made by service principals won't be blocked by Conditional Access policies scoped to users. Use Conditional Access for workload identities to define policies targeting service principals.
If your organization has these accounts in use in scripts or code, consider replacing them with managed identities.
Template deployment
Organizations can choose to deploy this policy using the steps outlined below or using the Conditional Access templates.
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 will not function as intended. Create a compliance policy first and ensure you have at least one compliant device before proceeding.
Browse to Protection > Conditional Access > Policies.
Select New policy.
Give your policy a name. We recommend that organizations create a meaningful standard for the names of their policies.
Under Assignments, select Users or workload identities.
Under Include, select All users
Under Exclude, select Users and groups and choose your organization's emergency access or break-glass accounts.
Under Target resources > Resources (formerly cloud apps) > Include, select All resources (formerly 'All cloud apps').
Under Access controls > Grant.
Select Require device to be marked as compliant.
Select Select.
Confirm your settings and set Enable policy to Report-only.
Select Create to create to enable your policy.
After administrators confirm the settings using report-only mode, they can move the Enable policy toggle from Report-only to On.
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 does not block Intune enrollment.
Known behavior
On Windows 7, 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.
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.
Plan and execute an endpoint deployment strategy, using essential elements of modern management, co-management approaches, and Microsoft Intune integration.