Fix it now
Entra ID checked the credential it was given and did not accept it. The exact code decides what you do next: 50126 is a wrong password, 50053 is lockout or a blocked sign-in, 50056 means no password exists in the directory for that account, and 50137 means the password has to be changed under a security policy rule. None of them is a multi-factor or conditional access failure.
- In the Microsoft Entra admin center, go to Entra ID then Monitoring & health then Sign-in logs and find the failed attempt. Reports Reader is the minimum role.
- Open the failed record and read the failure reason, the client application and the correlation identifier. The code an application shows the user is rarely the whole story.
- If several failures arrive in a burst from one application or device, treat that application as the source before you touch the account, because resetting first just restarts the cycle.
- Reset the password where the authoritative copy lives: in Entra ID for a cloud-only account, in on-premises Active Directory for an account that synchronises.
- Have the user sign in through a browser at the standard Microsoft sign-in page rather than through the failing application, to prove the credential itself now works.
- Then fix the application: update stored credentials on devices, scripts and mobile clients so the old password stops generating failures.
For AADSTS50053 read the failure reason on the sign-in log entry rather than assuming lockout. Microsoft documents two causes: too many incorrect attempts, and a sign-in blocked because it came from an IP address associated with malicious activity.
If the browser sign-in succeeds and no fresh failures appear, you are done. If they keep arriving, the next section covers where the password actually lives and what keeps replaying the old one.
Why it happens
Where the password lives depends on how the tenant is configured. With password hash synchronisation, a hash derived from the on-premises Active Directory password is synchronised to Entra ID and validated in the cloud. With pass-through authentication, an on-premises agent validates the credential against a domain controller. With federation, the sign-in is redirected to your own identity provider. A wrong password produces AADSTS50126 in all three, but where you fix it differs, and resetting in the wrong place either fails or is overwritten at the next synchronisation.
The neighbouring codes are not variations on the same theme. AADSTS50056 means Entra ID has no usable password material for the account at all rather than a mismatch, which on a synchronised tenant points at password hash synchronisation not reaching that object. AADSTS50137 is different again and frequently misread: Microsoft publishes it as the password needing to be changed due to a security policy rule, which is a forced change rather than a rejection. The user is not being told they are wrong; they are being told to pick a new one.
Lockout sits on top of all of this. Smart lockout tracks failed attempts and blocks further tries for a period, distinguishing attempts that look like the genuine user from attempts that look like an attack. A locked-out user is often doing nothing wrong: an old password saved in a phone’s mail client or a scheduled script generates a steady stream of failures that relocks the account minutes after every reset. The same code also covers a sign-in blocked because it came from an IP address associated with malicious activity, and only the failure reason on the sign-in log entry separates the two.
An old password is cached somewhere and keeps replaying
You have this one if Failures resume shortly after each reset, and the sign-in logs show the same client application or device every time.
- Filter the sign-in logs by that user and read the client application column to identify what is failing.
- Update or remove the stored credential on that device, service or script. Check mobile mail clients, Windows Credential Manager, scheduled tasks and anything using the account to send mail.
- Reset the password once more only after the source has been dealt with, otherwise the lockout returns.
This is by far the most common cause of repeated lockouts. Resetting again without finding the source simply restarts the cycle, usually within the hour.
The account is locked out, or the sign-in was blocked
You have this one if AADSTS50053 rather than 50126, and the user reports it started after several failed attempts or after travelling.
- Sign in to the Microsoft Entra admin center, open Monitoring & health then Sign-in logs, find the failure with sign-in error code 50053 and read the failure reason.
- If it is smart lockout, wait out the lockout period or reset the password, having first found what caused the failures.
- If the sign-in was blocked because it came from an address associated with malicious activity, treat it as a risk finding and remediate the account rather than simply unblocking it.
- If sign-in is blocked on the account object itself, re-enable it deliberately; somebody may have blocked it for a reason.
The password has to be changed under a policy rule
You have this one if AADSTS50137, and the credential the user is presenting is one they believe is correct.
- Treat this as a forced change rather than a rejection, and tell the user so. It is not a lockout and it is not a mistake on their part.
- Have them complete the change through a browser at the standard sign-in page, where the change prompt can actually be shown.
- Update any stored copy of the password afterwards, because the old one becomes a source of new failures the moment it changes.
Applications that cannot present a change-password prompt will keep failing until the change is completed somewhere that can, which is why the browser step is not optional here.
No password exists in the directory for the account
You have this one if AADSTS50056, on an account that synchronises from on premises and that nobody has changed recently.
- Confirm the synchronisation service is running and that recent cycles completed.
- Confirm password hash synchronisation is enabled for the connector using the troubleshooting task in the Entra Connect wizard.
- Force a synchronisation cycle with
Start-ADSyncSyncCycle -PolicyType Deltaand check whether the object updates. - Check whether the object is filtered out of scope, which produces a cloud account nobody can sign in to.
The password was changed in the wrong place
You have this one if The reset appeared to work but the cloud still rejects the credential, or the change is reverted a while later.
- Establish where the authoritative copy lives: on premises for a synchronised account, in Entra ID for a cloud-only one.
- Reset it there and let synchronisation carry the change.
- Have the user sign in through a browser first to confirm it has propagated before blaming an application.
Full reference
Which code you actually have
| Code | What Entra ID is saying | First move |
|---|---|---|
AADSTS50126 |
The credential did not validate | Find what is presenting it before resetting |
AADSTS50053 |
Locked out, or blocked from a suspicious address | Read the failure reason on the sign-in log entry |
AADSTS50056 |
No password exists in the directory for this user | Look at password hash synchronisation, not the password |
AADSTS50137 |
The password must be changed under a security policy rule | Complete the change in a browser |
None of these is a multi-factor authentication failure and none is conditional access. Those produce their own distinct codes, and chasing an MFA configuration on one of these four is time spent in the wrong blade.
Matching what you observe to where to look
| What you observe | Where to look |
|---|---|
| One user, one device, repeated failures | A cached credential on that device |
| Failures resume within minutes of every reset | Something is replaying an old password; find it in the sign-in logs |
| The account is blocked rather than rejected | Smart lockout, a risky-address block, or sign-in blocked on the account |
| A synchronised account has no password at all | Password hash synchronisation is not reaching that object |
| The user says the password is right and it is | A forced change under a policy rule |
Finding the source in the sign-in logs
- Open Entra ID then Monitoring & health then Sign-in logs in the Microsoft Entra admin center.
- Filter by the user and by the sign-in error code, rather than scrolling.
- Read the client application and the IP address on the failed entries, not just the timestamp.
- Look for a cluster: the same client application repeating on a schedule is a stored credential, not a person typing.
- Take the correlation identifier with you if you need to raise a case, because the code alone is not enough for anyone to help.
Reducing how often this happens
- Self-service password reset lets a user reset without a ticket, and with write-back it reaches a synchronised on-premises account too.
- Password protection refuses weak and banned passwords at the point they are set, which removes a category of guessable credential.
- Both reduce volume rather than fixing an individual incident, so judge them on how many of these tickets you actually raise.
- Neither removes the need to find the device replaying an old password, which is the cause of most repeat lockouts.
- Check what your existing subscription already includes before buying anything. A good deal of this is already paid for in most Microsoft 365 estates.
When a licence is the actual fix
Resetting a password costs nothing and everything above can be done with what you already have. What a licence changes is how often you do it. Microsoft Entra ID P1 adds self-service password reset with write-back to on-premises Active Directory, so a synchronised user can reset their own account without a ticket, and it is what enables Entra Password Protection for on-premises Active Directory Domain Services, which refuses weak and banned passwords at the point they are set. Check your entitlement first: the global banned password list is free for cloud-only users, and Microsoft 365 Business Premium, E3, E5, F1 and F3 and Enterprise Mobility + Security E3 all include P1 already. If the recurring cost here is help desk time rather than the incident itself, P1 is the honest answer, and we can confirm which of your users actually need it.
Every code this article covers
| Code | What it points at | Source |
|---|---|---|
AADSTS50126 |
InvalidUserNameOrPassword: error validating credentials due to an invalid username or password. Some volume of these is expected from people making mistakes | Microsoft Learn |
AADSTS50053 |
IdsLocked: the account is locked after too many incorrect sign-in attempts, or the sign-in was blocked because it came from an IP address with malicious activity | Microsoft Learn |
AADSTS50056 |
Invalid or null password: no password exists in the directory for this user | Microsoft Learn |
AADSTS50137 |
The password needs to be changed due to a security policy rule. This is a forced change rather than a rejected credential | Microsoft Learn |
Confirm the fix worked
- The user signs in through a browser at the standard sign-in page and it succeeds.
- The sign-in logs show no further failures from the device or application that was responsible.
- The account is neither locked nor blocked from signing in.
- Where the code was AADSTS50137, the password change actually completed rather than being dismissed.
- A day later, no fresh cluster of failures has appeared from a cached credential you missed.
Questions people ask about this
Where do I reset the password, in the cloud or on premises?
Wherever the authoritative copy lives. For a synchronised account that is on-premises Active Directory, and resetting in the cloud is either blocked or overwritten. For a cloud-only account it is Entra ID.
What does AADSTS50137 mean?
Microsoft publishes it as the password needing to be changed due to a security policy rule. It is a forced change, not a rejection, so the user has to complete a password change somewhere that can show the prompt, which usually means a browser.
Why does the account lock again minutes after every reset?
Because something is still presenting the old password: a phone, a saved credential, a scheduled script, a device that sends mail. Find it in the sign-in logs before resetting again.
Does AADSTS50053 always mean too many attempts?
No. Microsoft documents two causes: the account being locked after repeated incorrect attempts, and a sign-in blocked because it came from an IP address with malicious activity. The failure reason on the sign-in log entry tells you which.
Does this mean multi-factor authentication failed?
No. These codes are raised at the password stage, before any second factor. Multi-factor and conditional access failures produce their own distinct codes.
