Home › Entra ID › AADSTS53003

Entra ID · AADSTS53003 · Microsoft 365

Entra ID AADSTS53003 Error in Microsoft 365 - Conditional Access Block

AADSTS53003 error indicates a blocked sign-in due to non-compliance with Conditional Access policies. Fix involves adjusting policy grant controls or enrolling devices in Intune.

Error Details

FactValueSourceNote
Exact error stringAADSTS53003: access_denied - The operation was blocked by policy.Entra ID sign-in logs
Affected build rangeMicrosoft 365
Registry key or OMA-URI involvedNone specific to this error
Relevant service/endpoint URLhttps://login.microsoftonline.com/common/oauth2/v2.0/token
Log line signatureFailureReason=AADSTS53003 ConditionalAccessStatus=failureEntra ID sign-in logs

Log Files to Check

What This Error Actually Means

The error code AADSTS53003 is raised by Microsoft Entra ID when a sign-in attempt is blocked due to non-compliance with Conditional Access policies set up within the tenant environment. The exact error string reads "AADSTS53003: access_denied - The operation was blocked by policy." This indicates that while the user's credentials and identity meet the initial conditions of one or more Conditional Access policies, they fail to satisfy at least one grant control specified in those policies. Common reasons for this include a lack of multi-factor authentication (MFA), use of non-compliant devices, or attempts from unapproved client applications.

Affected Versions and Scope

This error is relevant across all builds of Microsoft 365, as it pertains to the core identity management framework that underpins these services. It impacts any tenant configuration where Conditional Access policies are enabled and enforced. The scope includes both on-premises hybrid environments and cloud-only deployments. Notably, this issue does not affect tenants without Conditional Access policies or those with such policies configured in a manner that allows all sign-in attempts to proceed unimpeded.

Where To Look First: Logs and Event IDs

To diagnose AADSTS53003 errors, start by examining the Entra ID sign-in logs. These can be accessed through the Microsoft Entra admin center under Identity > Monitoring & health > Sign-in logs. Filter these logs for entries with a FailureReason of "AADSTS53003" and ConditionalAccessStatus set to failure. Additionally, review the log files located at C:\Program Files\Microsoft Monitoring Agent\Agent\Bin\WaAppAgent.log and C:\inetpub\logs\LogFiles\W3SVC1\u_ex*.log. These logs may contain Event IDs 4769 and 4770, which provide additional context about the sign-in attempt that was blocked.

Root Causes

MFA Requirement Not Met

One common cause is when a user attempts to log in without fulfilling an MFA requirement. This can be identified by checking if the Conditional Access policy includes "Require multi-factor authentication" as a grant control and whether the sign-in attempt was made from a location or device that does not support this method.

Non-Compliant Device

Another frequent cause is when a user's device fails to meet compliance requirements set by Intune policies. This can be determined by reviewing the Conditional Access policy for "Require compliant devices" and checking if the device in question has enrolled with Intune but not yet achieved compliance.

Unapproved Client Application

If the sign-in attempt is made through an application that does not meet the criteria specified in a Conditional Access policy, such as using an unapproved client app or API version, this will also trigger AADSTS53003. This can be verified by examining the "Grant control" section of the relevant Conditional Access policy for restrictions on specific applications.

Fix Procedure

  1. Identify the Blocking Policy: In the Microsoft Entra admin center, navigate to Identity > Protection > Conditional Access and use the What-If tool to simulate a sign-in attempt from the affected user or device. This will reveal which policy is blocking access.
  2. Evaluate Compliance Status: Use Get-MgDeviceManagementManagedDevice -Filter "userPrincipalName eq ''" in PowerShell to check if the user's device meets compliance requirements set by Intune policies.
  3. Adjust Policy Settings: If the block is due to a misconfiguration, navigate to Identity > Protection > Conditional Access and edit the policy that is causing the issue. Adjust grant controls or exclude specific users/groups temporarily until compliance can be achieved.
  4. Exclude Service Accounts Temporarily:
    For service accounts or automation scripts, create an exclusion in the policy for the affected service principal or use a named location that exempts the IP range of the server running the script. This prevents disruptions to critical services while compliance issues are resolved.
  5. Audit Policy Impact: Review Conditional Access Insights & Reporting workbooks in the Entra admin center to assess the impact of changes made to policies.

Error Code Variants

Error Code Description Distinguishing Features
AADSTS53014 Access denied due to Conditional Access policy blocking sign-in. This error occurs when a user is blocked from signing in because their device does not meet the required compliance status, but no specific MFA requirement was violated. It can be distinguished by checking for "Require compliant devices" as the primary grant control failure.
AADSTS53024 Access denied due to Conditional Access policy blocking sign-in. This error is similar but indicates that a specific client application or API version was blocked by the policy. It can be identified through Event IDs 4769 and 4770 in logs, which will specify an unapproved app as the cause of failure.

Verification

To verify that a fix has been successfully implemented, monitor Entra ID sign-in logs for entries with FailureReason=AADSTS53003 and ConditionalAccessStatus=failure. Successful resolution will result in these errors no longer appearing for the affected user or device. Additionally, use Get-MgIdentityConditionalAccessPolicy to confirm that any necessary adjustments have been made to the relevant Conditional Access policies.

Prevention

To prevent recurrence of AADSTS53003 errors, ensure thorough testing and validation of all Conditional Access policies before they are enabled. Regularly review compliance status for devices and applications through Intune admin center > Devices > Compliance and adjust policies as needed to accommodate new or changing requirements without blocking legitimate sign-in attempts. Implementing a phased rollout approach can help minimize disruptions while ensuring that security standards are maintained.
A useful shortcut is to use the Conditional Access What-If tool in the Entra admin center to simulate sign-ins and identify potential issues before they affect users.

Sources & References

Related Guides

Get new error code fixes by email

Product-specific solutions for Intune, Autopilot, SCCM and Entra ID — straight to your inbox. No spam.