Fix it now
A Conditional Access policy evaluated this sign-in and refused it after the credentials were accepted. The code never names the policy, so the fix always starts in the sign-in logs rather than on the user’s machine.
- In the Microsoft Entra admin center, open the sign-in logs under Entra ID monitoring and find the failed attempt by user name and time. The error page the user saw carries a request ID and timestamp that take you straight to it.
- Open the record and select the Conditional Access tab. Every policy evaluated is listed with its result, and the one reported as a failure is the one that blocked the sign-in.
- Read the Basic info and Device info tabs on the same record for the condition that fired: location, device state, client application or risk.
- Decide whether the block is correct. If it is, satisfy the condition rather than weakening the policy – get onto a trusted network, enrol the device, or use an approved client.
- If it is wrong, open Entra ID, then Conditional Access, open the named policy and adjust its assignment or add a deliberate exclusion.
- Confirm a break-glass account is still excluded from every policy before you save anything.
If the Conditional Access area is not available in your tenant, you are almost certainly looking at security defaults instead, which is a single tenant-wide switch under Entra ID, Overview, Properties, Manage security defaults.
If the sign-in now succeeds and the policy reports success on a fresh record, stop here. If not, the next section covers what the neighbouring codes mean and why the message is deliberately vague.
Why it happens
Conditional Access runs after authentication, not instead of it. Once Entra ID is satisfied the credentials are genuine, it evaluates every enabled policy whose assignment matches this user, this application and this set of conditions. Microsoft documents AADSTS53003 as access being blocked by Conditional Access policies, with the access policy not allowing token issuance. A single block outranks every grant, so one narrow policy nobody remembers writing can stop a sign-in that ten other policies were happy with.
The message returned to the user is generic on purpose. Telling an unauthenticated caller which control failed would hand an attacker a map of your policy set. That design decision moves the whole diagnosis into the sign-in logs, where the Conditional Access tab shows the evaluation policy by policy, including policies running in report-only mode.
The neighbouring codes narrow the family. AADSTS50131 is documented as covering various Conditional Access errors – bad Windows device state, requests blocked for suspicious activity, access policy or security policy decisions. AADSTS530032 is a tenant-level security policy configured by an administrator rather than a policy you authored. AADSTS53011 is documented plainly as the user being blocked due to risk on their home tenant, which matters in cross-tenant access because the decision was taken somewhere you do not administer.
A block policy targets the user, group or application
You have this one if The Conditional Access tab names a policy whose grant control is Block, and the user falls inside its assignment.
- Open the named policy and read Users, Target resources and Conditions in that order.
- If the assignment is wrong, exclude a group rather than an individual, so the exception is visible at the next review.
- Re-run the sign-in and confirm the policy now reports success on the new record.
A location condition no longer matches reality
You have this one if Office users are fine and remote users are blocked, or the reverse after an office move or a change of internet circuit.
- Compare the named locations against your current outbound addresses, including any secondary or failover circuit.
- Add the missing ranges rather than removing the condition.
Legacy authentication is blocked and the client is still using it
You have this one if Browsers and modern desktop clients work; an older mail client, a copier or a line-of-business integration fails.
- Read the client application column on the failed sign-in record to confirm which protocol was used.
- Move the client onto modern authentication, which is the real fix.
- Where a device genuinely cannot, give it a dedicated account with narrow permissions and scope any exclusion to that account alone.
Blocking legacy authentication removes the most common route for password spray. Do not switch that policy off to make one scanner work.
The policy is correct and the user does not qualify
You have this one if The grant control demands a compliant device, an approved client application or multifactor authentication, and the user is not meeting it.
- Read what the grant control actually demands from the policy detail.
- Bring the user into compliance rather than removing the control: enrol the device, register the second factor, or use the approved application.
You cannot see or edit the policies at all
You have this one if Conditional Access is unavailable in the portal, or the sign-in record shows a decision you have no policy to explain.
- Check whether the tenant holds any Microsoft Entra ID Premium licences. Conditional Access requires Entra ID P1.
- If it does not, look at Entra ID, Overview, Properties, Manage security defaults, because on a free tenant that is usually what is refusing the sign-in.
- Accept that security defaults cannot be narrowed or scoped: they are one switch for the whole tenant.
Full reference
What the pattern of failures tells you
| Who is blocked | Which condition to check first |
|---|---|
| One user or group, one application, everywhere | The policy assignment targets them directly |
| Everyone, but only away from the office | A location or named network condition |
| Only personal or unmanaged devices | A device state or compliance requirement |
| Only older mail clients and scanners | A block on legacy authentication |
| Intermittently, for one person | A risk-based condition reacting to that sign-in |
| A guest from another organisation | AADSTS53011 – risk on their home tenant, which you do not control |
Where the controls live now
| What you want | Documented route |
|---|---|
| Conditional Access policies | Microsoft Entra admin center, Entra ID, Conditional Access |
| Security defaults on or off | Entra ID, Overview, Properties, Manage security defaults |
| The evaluation for one sign-in | The sign-in logs under Entra ID monitoring, Conditional Access tab on the record |
| Unmanaged-device restrictions for SharePoint and OneDrive | SharePoint admin center, with the enforcement carried by Conditional Access |
Report-only and staged rollout
A policy in report-only mode is evaluated against every matching sign-in and recorded on the sign-in record, but never enforces its controls. That is the safe way to see what a new policy would have done to real traffic before you turn it on, and it is also why a sign-in record can list a policy result that had no effect on the outcome. When you are reading the Conditional Access tab looking for the culprit, check the mode as well as the result.
Break-glass accounts
- Keep at least one cloud-only administrator account excluded from every Conditional Access policy in the tenant.
- Give it a long password held securely offline, and know where that is before you need it.
- Exclude it by group membership so a new policy cannot quietly omit it.
- Test that it still signs in after any policy change, as part of the change rather than after the incident.
- Policies apply to administrators exactly as they apply to users. Locking yourself out of the portal with a policy you just wrote is entirely possible.
Cross-tenant sign-ins
When a guest from another organisation is refused, two policy sets are in play: yours, and whatever their home tenant decided about the account. AADSTS53011 is the documented case where the block came from risk on the home tenant. You cannot clear that from your side, and adding an exclusion in your own policies will not help. The route is through their administrator, and the sign-in record is what tells you which side made the decision.
When a licence is the actual fix
This is one of the cases where a licence genuinely is the fix. Microsoft documents Conditional Access as requiring Microsoft Entra ID P1 licences for the users in scope, and states that customers with Microsoft 365 Business Premium licences can also use Conditional Access features. Without it, a tenant gets security defaults: one switch for everyone, with no per-application targeting, no trusted locations and no exclusions, which is exactly the wall administrators hit when they try to let a single meeting-room device or service account through. Check what you already hold before buying anything, because the entitlement is often already there inside a suite. Arco can confirm what your subscription covers and supply P1 seats for the users who need policy control.
Every code this article covers
| Code | What it points at | Source |
|---|---|---|
AADSTS53003 |
Access has been blocked by Conditional Access policies; the access policy does not allow token issuance | Microsoft Learn |
AADSTS50131 |
Covers various Conditional Access errors, including bad Windows device state, a request blocked for suspicious activity, and access or security policy decisions | Microsoft Learn |
AADSTS530032 |
A security policy configured at tenant level by an administrator blocks the request | Microsoft Learn |
AADSTS53011 |
The user is blocked due to risk on their home tenant | Microsoft Learn |
Confirm the fix worked
- Re-run the sign-in and confirm the Conditional Access tab on the new record shows success for every policy evaluated.
- Run the What If evaluation for that user, application and condition and confirm the result matches what you intended.
- Confirm the break-glass account still signs in after the change.
- Check that any exclusion you added is on a group, and that the group has the members you expect.
Questions people ask about this
Can the user tell me which policy blocked them?
Not from the error page, which is vague by design. It does carry a request identifier and a timestamp, and those find the exact record in the sign-in logs in seconds.
Does report-only mode block anything?
No. A report-only policy is evaluated and recorded against every matching sign-in but never enforces its controls. It is the safe way to see what a new policy would do before you enable it.
Do I really need a paid licence for this?
To manage Conditional Access, yes: Microsoft documents Entra ID P1 for the users in scope, and notes that Microsoft 365 Business Premium customers can use Conditional Access features too. Multifactor authentication itself can be required for nothing through security defaults, but you cannot scope or exclude anything there.
What if I lock myself out of the portal?
That is what break-glass accounts exist for: at least one cloud-only administrator account excluded from all policies, with a long password held securely offline. Set that up before your next policy, not after.
A guest cannot sign in and my policies all report success. What now?
Look for AADSTS53011 on the record. That is the documented case where their home tenant blocked the account for risk. Nothing you change in your tenant will clear it; their administrator has to.
