Skip to content

Est. 2011ยทMicrosoft Partner ID 7033487ยทDelivery under 3 minยทSupport 7 days a week

Your vault is empty.

Free Fix AADSTS50126

AADSTS50126 and AADSTS50055: Outlook Keeps Asking for a Password That Works Online

10 min read Updated October 5, 2026 Outlook & Office Applications

Fix it now

AADSTS50126 is InvalidUserNameOrPassword: error validating credentials due to invalid username or password. The same password works in a browser because what Outlook is sending is not what the user is typing – Windows is replaying a saved credential that has since changed.

  1. Confirm the account is healthy by signing in to the Microsoft 365 portal in a browser on the same machine.
  2. Close Outlook and every other Office application, checking Task Manager for stragglers.
  3. Open Credential Manager from Control Panel, go to Windows Credentials, and delete every entry relating to Office, Outlook, OneDrive and Microsoft accounts. Note what was there before you delete it.
  4. Restart the machine so nothing recreates the entries from memory.
  5. Start Outlook, enter the current password once, and complete any second-factor prompt.
  6. If the prompt returns immediately, read the actual code from the tenant sign-in logs. A rejected password and an expired password are different codes with different fixes.

Deleting Credential Manager entries signs the user out of everything that was using them, so expect to sign in again in several applications.

If Outlook connects and stays connected through a restart, you are done. The next section explains why the wrong password keeps being sent and how to find what is sending it.

Why it happens

Windows caches credentials so applications do not have to prompt constantly. Once a credential is saved against a resource, anything using the same store presents it automatically. When the password changes, that saved entry does not update itself. It keeps offering the old value until a person deletes it or something overwrites it.

The result is a loop that looks like user error and is not. Outlook presents the stale credential, the service rejects it with AADSTS50126, the client prompts, the user types the correct password, and the stale credential is presented again on the next request. Worse, repeated rejections count towards lockout protection, so an account can end up locked by a machine sitting idle in another room with nobody near it.

The other codes separate account state from credential state, and the distinction leads to different places. AADSTS50055 is InvalidPasswordExpiredPassword – the password is expired, so the login or session was ended, and the user will be offered the chance to reset it. AADSTS50057 is UserDisabled: the user object backing the account has been disabled. Those are not credential caching problems and clearing Credential Manager will not touch them.

AADSTS50133 is the one worth knowing about, because it explains a burst of prompts nobody caused. Microsoft publishes it as SsoArtifactRevoked: the session is not valid due to password expiration or a recent password change. A reset invalidates existing sessions, which is why every device a user owns prompts at once shortly after one. AADSTS50089 is a flow token that expired, which Microsoft describes as expected – auth codes, refresh tokens and sessions expire or are revoked, and the app will request a new login.

A stale credential in Windows Credential Manager

You have this one if Browser sign-in works, Outlook prompts, and the machine has been in use since before the password changed.

  1. Close every Office application.
  2. Delete the Office, Outlook, OneDrive and Microsoft account entries from Credential Manager, under Windows Credentials.
  3. Restart the machine so nothing recreates them from memory.
  4. Start Outlook, sign in once, and confirm the prompt does not return.

Another device or service is replaying the old password

You have this one if The account locks out repeatedly, and the lockouts continue while the user’s own machine is switched off.

  1. Use the tenant sign-in logs to find the failing attempts and the address or device they come from.
  2. Work through the usual suspects: a phone with an old mail profile, a multifunction printer configured to send mail, a scheduled task, or an application using the account as a service identity.
  3. Update or remove the stored credential wherever it actually lives.
  4. Watch the sign-in logs for a full day afterwards to confirm the failures have stopped.

Scan-to-email devices and application mail submission are the most common hidden source. Give them their own identity rather than a person’s, so a password change never causes this again.

The password has expired rather than been rejected

You have this one if The sign-in log shows AADSTS50055 rather than AADSTS50126.

  1. Have the user change the password through the normal self-service route in a browser.
  2. Clear cached credentials on each of the user’s devices afterwards.
  3. Sign in once on each device and confirm the new password is what gets cached.
  4. Review whether a forced expiry policy is still earning its place, particularly where multifactor authentication is already in use.

The account is disabled or blocked from signing in

You have this one if Everything fails, including the browser, and the sign-in log shows AADSTS50057.

  1. Check the account’s state in the admin centre.
  2. For a synchronised account, confirm the on-premises account is enabled and that directory synchronisation has run since it was changed.
  3. Re-enable the account and force a synchronisation cycle if one is needed.
  4. Test in a browser first, then on the desktop.

An old client is attempting an unsupported authentication method

You have this one if An older client version or an unusual mail application prompts endlessly while a current Outlook on the same machine works normally.

  1. Update the client to a version that supports modern authentication.
  2. Confirm modern authentication is enabled for the organisation and the mailbox.
  3. Move any application still submitting mail with a basic credential onto a supported method.
  4. Retire any device profile that cannot be updated, rather than weakening the tenant to accommodate it.

Full reference

Working out what is really being rejected

What you observe Where to look
Browser sign-in works, Outlook does not A stale saved credential on this machine
Prompts started immediately after a password change Cached credentials on this or another device
The account locks repeatedly with nobody typing A device or service replaying an old password
Every device prompts at once A recent reset; expect AADSTS50133 in the log
Sign-in fails everywhere, browser included Account state, not credential caching

Reading the codes in the sign-in log

Code Short name Published meaning
AADSTS50126 InvalidUserNameOrPassword Error validating credentials due to invalid username or password
AADSTS50055 InvalidPasswordExpiredPassword The password is expired, so the login or session was ended
AADSTS50057 UserDisabled The user account is disabled
AADSTS50133 SsoArtifactRevoked The session is not valid due to password expiration or a recent password change
AADSTS50089 – Authentication failed due to flow token expired; expected, and the app will request a new login

Finding the machine nobody is sitting at

A lockout that continues while the user is on holiday is the clearest sign in this whole family, and the sign-in logs will tell you where it comes from if you filter to failures for that user and read the client application and IP address columns. What you are looking for is repetition: the same source, the same interval, the same failure code. A human retyping a password produces irregular attempts; a stored credential produces a metronome.

Once you have the source, resist the temptation to just reset the password again. A reset re-invalidates every session the user has, produces a fresh burst of AADSTS50133 across their devices, and leaves the offending stored credential exactly where it was. Fix the store, then decide whether a reset is still needed.

Password expiry policy, honestly

Forced rotation was designed for a world without multifactor authentication and leaked-credential detection. Where both are in place, rotation mostly produces the credential-caching mess this article describes, on a schedule. That is a decision to make deliberately rather than by default in either direction, and it is worth putting on the table when the same user has generated three of these tickets in a year.

If the prompt survives everything here

  • Check whether the machine holds more than one signed-in identity in Office, which produces prompts that look like credential failures.
  • Check whether a conditional access policy is refusing the request, which is a different family of codes and a different article.
  • Check the machine clock; a large offset breaks token validation and looks like a rejected credential.
  • Test with a new Windows user account on the same machine to separate profile state from machine state.
  • Confirm the account is not being blocked by a sign-in risk policy, which will show in the sign-in log as a risk-based refusal rather than a bad password.

Every code this article covers

Code What it points at Source
AADSTS50126 InvalidUserNameOrPassword: error validating credentials due to invalid username or password Microsoft Learn
AADSTS50055 InvalidPasswordExpiredPassword: the password is expired, so the login or session was ended Microsoft Learn
AADSTS50057 UserDisabled: the user account is disabled Microsoft Learn
AADSTS50133 SsoArtifactRevoked: the session is not valid due to password expiration or a recent password change Microsoft Learn
AADSTS50089 Authentication failed because the flow token expired; expected behaviour, and the application will request a new login Microsoft Learn

Confirm the fix worked

  1. Sign in once and confirm no repeat prompt after a full restart.
  2. Credential Manager holds a single fresh set of entries rather than several stale ones.
  3. The tenant sign-in logs show a success and no further failures for that account.
  4. The account does not lock out at any point across a full working day.
  5. Any printer or service that was replaying the old password now has its own identity.

Questions people ask about this

Do I need to buy anything to stop these prompts?

No. Every fix here is a cached credential, an account state or a client version. If sign-in is being refused by a policy rather than by a credential, that is a different family of codes with a different article.

Should I turn off password expiry?

It is worth reviewing. Forced rotation was designed for a world without multifactor authentication and leaked-credential detection, and where those are in place it mostly produces exactly this credential-caching mess. Make the decision deliberately.

Why does the account keep locking out?

Because something is retrying an old password automatically. Find it in the sign-in logs rather than by asking users what they typed; in practice it is nearly always a phone, a printer or a service using stored credentials nobody remembers configuring.

Everyone’s devices started prompting at once. What happened?

Almost certainly a password reset. Microsoft publishes AADSTS50133 as a session that is not valid due to password expiration or a recent password change, and a reset invalidates existing sessions across every device at the same moment.

Can I stop Outlook remembering the password entirely?

You can, but it is rarely what you want. The goal is for it to remember the correct credential rather than none at all. Clear the stale entry, sign in once, and let it cache the right one.

Related error codes

Was this article helpful?

Your feedback helps us improve our documentation.

Related articles

License Error AADSTS50058 and AADSTS53003: Outlook Sign-in Loop From Conditional Access Rules Free Fix VBA Runtime Error 91 Object Variable or With Block Variable Not Set Free Fix Word could not create the work file: Fix a Broken Temp Path and Cache Location Free Fix OneDrive and Office Sign-in Error 0x8004DE40: Login Was Interrupted or Unsuccessful
โ† Back to Knowledge Base