About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.
AADSTS53003 is Microsoft's code for BlockedByConditionalAccess. A Conditional Access policy in your tenant matched the sign-in and its controls were not met, so no token was issued. The user sees an error page; you find the policy in the Microsoft Entra sign-in log, on the Conditional Access tab of the failed event.
Do not edit policies until you know which one applied and whether the block is deliberate. A policy that blocks one user may be doing exactly its job for everyone else it applies to.
What the error means
The Microsoft Entra error-code reference lists AADSTS53003 as: "BlockedByConditionalAccess - Access has been blocked by Conditional Access policies. The access policy does not allow token issuance. If this is unexpected, see the Conditional Access policy that applied to this request or contact your administrator."
It is one of a family. The Conditional Access troubleshooting page lists these codes and strings:
| Sign-in error code | Error string |
|---|---|
| 53000 | DeviceNotCompliant |
| 53001 | DeviceNotDomainJoined |
| 53002 | ApplicationUsedIsNotAnApprovedApp |
| 53003 | BlockedByConditionalAccess |
| 53004 | ProofUpBlockedDueToRisk |
| 53009 | Application needs to enforce Intune protection policies |
The same page says the codes appear with the prefix AADSTS, "like AADSTS53002". A different code, AADSTS530035 (BlockedBySecurityDefaults), is listed in the error reference for requests blocked by security defaults. That is a different error from AADSTS53003, with a different cause.
Policies apply only when all their conditions are satisfied or not configured. A sign-in can therefore be blocked by one policy while the others do not apply to it at all.
Two details explain why a block can look wrong to the user. First, service dependencies: the Conditional Access page says users can be blocked because a cloud app depends on a resource that a policy blocks, so the sign-in log for the application and the resource it called both matter. Second, audience: when someone signs in to Teams they request access to several resources, such as chat, calendar and documents, and a policy restricting SharePoint applies even though the user believes they only started Teams. The Audience entry under Resource in the sign-in log lists every resource requested in that sign-in.
Likely causes
| Cause | What you see | How to confirm |
|---|---|---|
| A policy with a Block access control matches the user, app, location or device | AADSTS53003 on every attempt for that combination | Conditional Access tab of the failed sign-in shows a policy with result Failure |
| A policy requiring a compliant, hybrid-joined or app-protected device is applied to a user without such a device | Error page says the app can only be used from devices or client apps meeting the organisation's management policy | The policy's grant control; the Device Info tab of the event |
| The policy hits a resource the user did not think they asked for | The user signed in to one app but another resource (for example SharePoint behind Teams) is in scope | Audience under Resource on the policy detail, and the app and resource named in the sign-in log |
| A broad "all users, all resources" policy was released without exclusions | Many users, or an administrator, are blocked at once | The policy's Users and Target resources assignments |
Prove the cause before changing anything
Everything here only reads. You need at least the Reports Reader role.
- Ask the user to select More Details on the error page. The Conditional Access troubleshooting page says this reveals the information that helps when searching the sign-in events or opening a Microsoft support incident. Write down what it shows, and the time of the failure.
- Sign in to the Microsoft Entra admin center and browse to Entra ID > Monitoring & health > Sign-in logs.
- Filter by Username, Date, Resource and, when you have it, Correlation ID. Add the Conditional Access filter and scope it to failures.
- Select the failed event and open the Conditional Access tab. It lists each policy that resulted in the interruption. The Troubleshooting and support tab may state a reason such as a device that did not meet compliance.
- Select the ellipsis on the right of a policy to see why it did or did not apply. The left side shows what was collected at sign-in; the right shows whether those details meet the policy's requirements.
- If the event is still unclear, use the sign-in diagnostic under Basic info > Troubleshoot Event, or the What If tool.
The What If tool is under Entra ID > Conditional Access > Policies > What If. It needs an identity, a target resource, a device platform and a client app. Microsoft's page warns that it does not test Conditional Access service dependencies: a test for Teams does not include a policy that applies to Exchange Online, which Teams depends on. It also says that for the application you provide the App ID, because groups of apps such as Office 365 do not match.
Example (illustrative): at Contoso, a user amelia@contoso.com.au is blocked at 09:12 opening Teams from an overseas hotel. The sign-in log shows two Conditional Access policies with result Failure: "Require compliant device" and "Block access outside Australia". The first policy lists Office 365 Exchange Online in its audience, which Teams requested on her behalf. The second matches her hotel's overseas location. Changing only the first policy would not have let her in.
Fix
Choose from what the log shows. The policy is doing its job if it is intended; the fix is then with the user, device or location, not the policy.
Disruptive step: editing or disabling a Conditional Access policy. It changes who can reach your data. If the policy protects administrators, the edit can lock you or others out. Before any edit, write down the policy's state and its Users, Target resources, Conditions, Grant and Session settings. To back out, put those values back and save. Microsoft's page warns that some "all users, all resources" configurations block the whole organisation, and that a compliant-device requirement blocks an administrator who has no enrolled device from getting back in to change the policy.
- Intended block: tell the user which condition failed (device, location, app) and how to meet it.
- Policy too broad: add the affected users or a group to the exclusion list, or narrow the target resources.
- Mistaken policy: set it to Report-only while you correct it. Report-only evaluates the policy without enforcing it, and results appear in the Conditional Access and Report-only tabs of the sign-in log. Microsoft notes that report-only is not available for the User Actions scope.
- Unknown policy: copy it, put the copy into report-only with your proposed change, and compare results against the enforced original, as the report-only page advises.
Microsoft's page also lists configurations that must not be used for all users and all resources: Block access, Require device to be marked as compliant, Require Hybrid Microsoft Entra domain joined device, and Require app protection policy.
Confirm the fix
- Ask the affected user to sign in again, from a new private browser window, and read the new sign-in event.
- On the Conditional Access tab, the policy should show Success or Not applied. Remember the sign-in "might still be blocked by a different policy".
- Run What If for the same user, app, platform and client to confirm no other policy now applies a block.
- Move a report-only policy to On only after the report-only results show the intended outcome.
What to watch afterwards
- Failed Conditional Access sign-ins in the log, filtered by the policy you changed, for the next few days.
- The request ID, time and date from the sign-in event. Microsoft's page says that if you need to submit a support incident, you should include the request ID, time and date from the sign-in event in the incident details.
- Report-only results for any policy you are still correcting. On macOS, iOS and Android, report-only policies requiring a compliant device can prompt users to select a device certificate; Microsoft suggests excluding those platforms from such report-only policies.
Read next
Related articles you may want next.
- CloudEntra ID Conditional Access: tenant lockout, break-glass accounts and how to test policy safelyHow Conditional Access locks administrators out, how to build emergency accounts that work under mandatory MFA, and a safe order for testing policy.Read article
- TroubleshootingAADSTS50105: The signed in user is not assigned to a role for the applicationAADSTS50105: the app requires user assignment. Check Assignment required, assign the user or a direct-member group, and avoid nested groups.Read article
- HostingKeeping email notifications and MFA working when the application server movesKeep email notifications and staff sign-in working through a hosting move. Check mail relays, registered application addresses and authentication dependencies with controlled tests.Read article
Risks and limits
- No commands are given. The portal steps have not been run or lab-tested.
- What If estimates results; the real sign-in log is the record of what happened.
- Your tenant's portal labels can differ from Microsoft's pages, which Microsoft updates.
- Policies and error text depend on your licences and settings; check the current Microsoft pages before relying on any value here.
- A block can come from more than one policy at once; fixing the first one you find may not clear the error.
Sources
- Troubleshoot sign-in problems with Conditional Access — Microsoft Learn, page dated 2026-03-24, accessed 20 November 2026
- Microsoft Entra authentication and authorization error codes — Microsoft Learn, page dated 2025-02-03, accessed 20 November 2026
- Troubleshoot Conditional Access policies with the What If tool — Microsoft Learn, page dated 2026-08-27, accessed 20 November 2026
- Analyze Conditional Access policy impact — Microsoft Learn, page dated 2026-06-01, accessed 20 November 2026
This article was originally published on .