Description
A Conditional Access policy for All users on All resources grants access only if the device is marked as compliant by Intune or is Microsoft Entra hybrid joined (Require one of the selected controls). Intune compliance policies exist for each platform in use, and devices without a compliance policy are marked not compliant.
The policy excludes only the emergency access accounts, the Directory Synchronization Accounts role on hybrid tenants and, if documented, guests. Organisations that allow personal devices can tailor this control: keep the policy for desktop clients and mobile apps, and give browsers on unmanaged devices limited web-only access through app enforced restrictions.
Rationale
A stolen password or session cookie is only useful from a device the attacker controls. Requiring a managed device moves the trust decision to a device the organisation configures, patches, encrypts and can wipe, and stops data from being synchronised to unknown machines.
Impact
Strong impact where personal devices are used: users can no longer reach Microsoft 365 from a device the organisation does not manage. Enroll every corporate device in Intune first, check compliance results, and plan the personal-device scenario (web-only access, app protection policies on mobiles). Guests from partner tenants need cross-tenant trust of their device claims, or an exclusion.
Applies when
Requires: Microsoft Entra ID P1, Microsoft Intune
Audit
- Sign in to the Microsoft Entra admin center (https://entra.microsoft.com) as at least a Security Reader.
- Browse to Entra ID > Conditional Access > Policies.
- Find a policy with State set to On (not Report-only) where:
- Users > Include is All users, and Exclude contains only the accounts listed above;
- Target resources includes All resources, without exclusions;
- Grant is Require device to be marked as compliant and/or Require Microsoft Entra hybrid joined device. If the organisation tailored the control for personal devices, check that the excluded client apps are only Browser and that a second policy applies app enforced restrictions to them.
- In the Intune admin center (https://intune.microsoft.com), as at least a Global Reader, check under Devices > Compliance that a policy exists per platform and that Compliance policy settings marks devices with no policy as Not compliant.
- Read-only alternative with Microsoft Graph PowerShell (scope
Policy.Read.All):Get-MgIdentityConditionalAccessPolicy | Where-Object { $_.GrantControls.BuiltInControls -match 'compliantDevice|domainJoinedDevice' } | Select-Object DisplayName, State, @{n='Users';e={$_.Conditions.Users.IncludeUsers}}, @{n='Apps';e={$_.Conditions.Applications.IncludeApplications}} - Fail if no such policy exists, if it is Report-only or Off, or if it does not cover all users and all resources.
Remediation
- Create Intune compliance policies for each platform and enroll corporate devices; check that they report Compliant.
- As at least a Conditional Access Administrator, browse to Entra ID > Conditional Access > Policies and select New policy.
- Name it, for example
ALL - Require managed device. - Users > Include: All users. Exclude: the emergency access accounts and the Directory Synchronization Accounts role.
- Target resources > Resources > Include: All resources.
- Grant > Grant access: select Require device to be marked as compliant and Require Microsoft Entra hybrid joined device, then Require one of the selected controls.
- Set Enable policy to Report-only, save, and review the sign-in logs for at least two weeks to find unmanaged devices.
- Switch Enable policy to On.
Graph equivalent:
New-MgIdentityConditionalAccessPolicywithgrantControls.builtInControlsset tocompliantDeviceanddomainJoinedDeviceand operatorOR.
Rollback
Set the policy to Report-only. Sign in with an emergency access account if needed.
References
- Require device compliance with Conditional Access Microsoft, vendor-doc, accessed 2026-10-24
- Use application enforced restrictions for unmanaged devices Microsoft, vendor-doc, accessed 2026-10-24
- CISA SCuBA Microsoft Entra ID baseline CISA, standard, accessed 2026-10-24
Mappings
| Framework | ID | Relation |
|---|---|---|
| NIST SP 800-53 Rev. 55.1.1 | AC-19 | related |
| NIST SP 800-53 Rev. 55.1.1 | IA-3 | related |
| CISA SCuBA Microsoft 365 Secure Configuration Baselines2.0.0 | MS.AAD.3.7v1 | equivalent |
How this control relates to the other framework's: equivalent, stricter, looser, partial or related.
Threats mitigated
| Taxonomy | ID |
|---|---|
| MITRE ATT&CK | T1078.004 |
| MITRE ATT&CK | T1539 |
Related controls
- related
CB-M365-AUTH-019Protect security information registration with a managed device or MFA - related
CB-M365-AUTH-021Block unknown or unsupported device platforms - related
CB-M365-AUTH-028Require a fresh sign-in with MFA for every Intune device enrollment - related
CB-M365-ADMIN-002Keep two protected emergency access accounts - requires
CB-M365-DEVICE-001Mark devices without a compliance policy as not compliant - related
CB-M365-COLLAB-015Limit SharePoint and OneDrive to web-only access from unmanaged devices - related
CB-M365-COLLAB-034Restrict Teams Rooms resource accounts to managed room devices
People and lifecycle
| Authors |
|
| Introduced in | v0.1.0 |
| Created, updated | 2026-10-24, 2026-10-24 |
| Translations | fr |