Require Compliant Or Hybrid Azure AD Joined Device.

This Conditional Access Policy requires that administrators sign in only from devices that are compliant or hybrid Azure AD joined. It helps ensure that only trusted and managed devices can access sensitive resources, reducing the risk of unauthorized access.

Settings this baseline controls

Setting	What it does
Policy name	Specifies a display name for the Conditional Access Policy Learn more
Enable policy	Specifies the state of the conditional Access Policy. Possible values are: enabled, disabled, enabledForReportingButNotEnforced. Required. Learn more
Included users	User IDs in scope of policy Learn more
Included roles	Role IDs in scope of policy Learn more
Included groups	Group IDs in scope of policy Learn more
Included guest types	Guest or external user types in scope of policy Learn more
Excluded users	User IDs excluded from scope of policy Learn more
Excluded roles	Role IDs excluded from scope of policy Learn more

5 more settings

Setting	What it does
Excluded groups	Group IDs excluded from scope of policy Learn more
Excluded guest types	Guest or external user types excluded from scope of policy Learn more
Grant controls	List of values of built-in controls required by the policy. Possible values: block, mfa, compliantDevice, domainJoinedDevice, approvedApplication, compliantApplication, passwordChange, unknownFutureValue Learn more
Included applications	The list of client IDs (appId) the policy applies to, unless explicitly excluded (in excludeApplications) All, Office365 - For the list of apps included in Office365. Learn more
Client app types	Client application types included in the policy. Possible values are: all, browser, mobileAppsAndDesktopClients, exchangeActiveSync, easSupported, other. Required. Learn more

Adding a baselineAdd, configure or remove a single baseline on a tenant, a user or a group, without deploying a whole scheme.→

Configure it

Add this baseline when sign-in should be allowed only from a device Intune has already marked compliant, or from a device joined to both your on-premises Active Directory and Microsoft Entra, and never from an arbitrary personal machine.

1. Add the baseline to the tenant directly (see Adding a baseline), or carry it in a scheme you deploy to every tenant you manage (see Deploying a scheme).

2. Leave Included users covering everyone, and use Excluded users or Excluded groups for break-glass accounts. If you want this to reach only your admin roles rather than the whole tenant, scope it further with Included roles.

3. Leave Grant controls set to require a compliant device or an Entra hybrid-joined device, satisfying either one. Most tenants have devices that meet one or the other, not always both.

4. Save.

   Turn on Auto-remediation if you want Octiga to reapply the policy whenever it’s changed in Microsoft 365.

Caution

Before you enforce this baseline, it needs a device compliance policy set up in Intune and at least one compliant or hybrid-joined device among the people it targets. Otherwise, everyone in scope can be locked out at once.

Licence: Entra ID P1 or P2

This baseline needs Entra ID P1 or P2 on the tenant. Without it, Octiga excludes the baseline rather than reporting it as deviated — see Licence requirements.

Check it worked

After the next sync, this baseline shows Passing once a policy with state set to enabled and the compliant-device-or-hybrid-joined grant controls exists in Microsoft Entra. You can confirm it in the Microsoft Entra admin centre under Entra ID > Conditional Access > Policies. Anyone it targets notices nothing on a compliant or hybrid-joined device; from any other device, sign-in is blocked.

Standards this addresses

CISM365 5.2.2.xv8 4.1v8 6.4

NISTPR.AC-7SC-7CM-7

ISO 27001A.8.3A.8.22

GDPRArticle 32

Doing this for every tenant?

Step through the deploy wizard to apply a scheme to a tenant, groups or users, and see what Managed and Direct do at deploy time.

Deploying a scheme→