Error Details
| Fact | Value | Source | Note |
|---|
| Error Code | AADSTS53003 | Entra ID Sign-in Logs | -> Indicates Conditional Access policy failure. |
| OS Build | Windows 11 22H2 | System Information | -> Affected operating system version. |
| Registry Key | HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion | Device Configuration | -> Contains OS build information. |
| Service URL | https://portal.azure.com/#blade/Microsoft_AAD_IAM/ConditionalAccessBlade | Entra ID Admin Portal | -> Location to review Conditional Access policies. |
| Log Signature | Microsoft-Identity-Service/Operational | Windows Event Viewer | -> Log file containing error details. |
Log Files to Check
C:\Windows\System32\winevt\Logs\Microsoft-Identity-Service%4Operational.evtx
What This Error Actually Means
The
AADSTS53003 error is a Conditional Access policy enforcement failure in Entra ID. It indicates that a sign-in attempt was blocked because the device or user did not meet the conditions defined in an active Conditional Access policy. Specifically, the error is raised by the **Microsoft Identity Service** (MIS) component during authentication, which evaluates device compliance status, multi-factor authentication (MFA) requirements, and other risk-based rules. The hexadecimal error code translates to a violation of the
DeviceCompliance or
MultiFactorAuthentication conditions in the policy. This error is distinct from transient authentication failures and reflects a hard block enforced by policy logic.
Affected Versions and Scope
This error occurs on **Windows 11 22H2** (OS build 22621.x) when Conditional Access policies require device compliance or MFA. It affects tenants with policies that enforce compliance-based access (e.g., "Require device to be marked as compliant") or MFA for specific risk levels. Tenants using older OS versions (e.g., Windows 10 21H2 or earlier) may not trigger this error due to differences in device attestation mechanisms. Additionally, tenants without Conditional Access policies configured for device compliance or MFA are unaffected. The error is not specific to any particular Entra ID tenant configuration but is contingent on policy enforcement logic and device state.
Where To Look First: Logs and Event IDs
The primary diagnostic artifacts are in the **Microsoft-Identity-Service/Operational** event log. The exact log path is
C:\Windows\System32\winevt\Logs\Microsoft-Identity-Service%4Operational.evtx. Use
Get-WinEvent -LogName "Microsoft-Identity-Service/Operational" to query entries. Look for Event IDs **501** (device compliance check initiated) and **503** (Conditional Access policy evaluation failure). In the Entra ID Sign-in Logs (
https://portal.azure.com/#blade/Microsoft_AAD_IAM/SigninLogsMenuBlade), filter by error code
AADSTS53003 and inspect the "Applied Conditional Access Policies" section for the violating policy name. Registry key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion may show device attestation status via the
ProductId and
BuildLabEx values.
Root Causes
1. Device Not Marked Compliant in Intune
The device lacks compliance status due to missing Intune profiles or failed compliance checks. Verify via
Get-MgDeviceManagementManagedDevice -Filter "id eq 'deviceID'" and check the
complianceState property. This cause is identifiable by Event ID 501 showing
ComplianceStatus: NonCompliant.
2. MFA Requirement Unmet
The user account lacks registered MFA methods (e.g., Authenticator app, SMS). Check via
Get-MgUserAuthenticationMethods -UserId "[email protected]". The error log will reference
AuthenticationMethod: None in the MIS operational log.
3. Conditional Access Policy Misconfiguration
A policy may incorrectly target unenrolled devices or exclude required MFA scenarios. Review policies at
https://portal.azure.com/#blade/Microsoft_AAD_IAM/ConditionalAccessBlade and look for rules with
DeviceState or
Location conditions that conflict with the device's actual state.
Fix Procedure
- **Enforce Device Compliance via Intune**:
Invoke-MgGraphRequest -Method POST -Uri "https://graph.microsoft.com/v1.0/deviceManagement/deviceCompliancePolicies/assign" -Body @{"assignments"=@{"target"=@{"deviceAndAppManagement"=@{"deviceCompliancePolicyAssignments"=@{"target"=@{"groupId"="groupObjectId"}}}}}}}
Apply a compliance policy to the device group.
- **Register MFA Methods**:
Set-MgUserAuthenticationMethod -UserId "[email protected]" -AuthenticationMethodId "mfaMethodId" -IsEnabled $true
Ensure at least one MFA method is enabled for the user.
- **Adjust Conditional Access Policy**:
Navigate to
Entra ID admin center > Security > Conditional Access, edit the policy, and refine Device platforms or Locations to exclude non-compliant devices.
- **Registry Fix for Device Attestation** (use cautiously):
REG ADD "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\DeviceManagement" /v "EnrollmentMode" /t REG_DWORD /d 4 /f
This forces Azure AD enrollment mode; incorrect values may break Intune enrollment.
- **OMA-URI for Compliance Settings**:
./Device/Vendor/MSFT/Policy/Config/DeviceCompliance/CompliancePolicyName
Use this in Intune device profiles to enforce compliance rules.
Error Code Variants
| Error Code | Description | Distinguishing Factor |
AADSTS53003 | Conditional Access policy block | Policy evaluation failure in MIS logs |
AADSTS50058 | Device not enrolled in MDM | Missing enrollmentStatus in device logs |
AADSTS50059 | Device not compliant | ComplianceState: NonCompliant in Intune API |
Verification
After remediation, check the Entra ID Sign-in Logs for a successful entry with
status: Succeeded and no error code. In the MIS operational log, confirm Event ID 503 is absent and Event ID 501 shows
ComplianceStatus: Compliant. Run
dsregcmd /status to verify
AADJoin: Yes and
Compliance: Compliant. In Intune (
Intune admin center > Devices > Windows > All Devices), the device should show
Compliance: Compliant.
Prevention
Implement a baseline policy in Intune to auto-enroll devices and enforce compliance checks. Use
Get-AutopilotDevice | Where-Object { $_.deviceEnrollmentType -eq "windowsAutoEnrollment" } to audit enrollment status. Schedule monthly
Get-MgDeviceManagementDeviceCompliancePolicy reviews to ensure policies align with Conditional Access rules. For MFA, enforce registration via
Set-MgUserAuthenticationMethodConfiguration -UserId "[email protected]" -AuthenticationMethodConfiguration @{"state"="Enabled"}. Regularly audit Conditional Access policies at
Entra ID admin center > Security > Conditional Access to avoid over-restrictive rules.