Conditional Access policies block access from noncompliant devices

Overview

If Microsoft Entra Conditional Access policies don’t enforce device compliance, users can connect to corporate resources from devices that don’t meet security standards. This exposes sensitive data to risks like malware, unauthorized access, and regulatory noncompliance. Without controls like encryption enforcement, device health checks, and access restrictions, threat actors can exploit noncompliant devices to bypass security measures and maintain persistence.

Requiring device compliance in Conditional Access policies ensures only trusted and secure devices can access corporate resources. This supports Zero Trust by enforcing access decisions based on device health and compliance posture.

Remediation

Configure Conditional Access policies in Microsoft Entra to require device compliance before granting access to corporate resources:

• Create a device compliance-based Conditional Access policy

For more information, see:

• What is Conditional Access?
• Integrate device compliance results with Conditional Access

Run it

The check runs as part of the whole assessment, with the ZeroTrustAssessment module installed:

Install-Module ZeroTrustAssessment -Scope CurrentUser
Connect-Maester
Invoke-Maester -Pack ZTA -SkipBuiltIn

Leave out -SkipBuiltIn to run Maester’s own checks in the same run.

About this check

Severity	High
Effort to fix	Low
Impact on users	Medium
Pillar	Devices
Category	Data
Product	Entra ID
Feature	Conditional Access
Area	Access control
ATT&CK	T1078.004 Cloud Accounts
Licence	Intune
Tenant	Workforce

Product, feature, area and ATT&CK are Maester’s: the assessment does not record them, so Maester keeps them in the pack’s taxonomy.json.

A Microsoft check, part of the Zero Trust Assessment pack. Text from ZeroTrustAssessment 3.1.0, © Microsoft, MIT licence.