AADSTS50053

Account locked (smart lockout)

Last reviewed 2026-07-18 by the Just Software engineering team · also seen as 50053, IdsLocked, account is locked

What it means

AADSTS50053 — the account is locked because of too many failed sign-in attempts, or sign-in was blocked because it originated from an address associated with malicious activity. Entra smart lockout locks the account for a short period after repeated wrong passwords (by default, 10 failed attempts trigger a 60-second lockout, escalating on continued failures). It protects the cloud credential — the on-prem AD account may or may not be locked separately.

Common causes

  1. A stale saved password keeps retrying: old phone mail profile, background service, mapped drive, scheduled task or forgotten device.

  2. Password-spray or brute-force attempts against the account from the internet.

  3. The user genuinely mistyping repeatedly after a recent password change.

How to fix it

  1. Check Entra sign-in logs (Entra admin center > Users > (user) > Sign-in logs) for the failing source: client app, IP and device usually identify the stale credential or the attack source.

  2. Hunt down the device/app replaying the old password and update or remove the saved credential.

  3. If under spray attack: confirm smart lockout settings (Entra admin center > Protection > Authentication methods > Password protection), enforce MFA, and consider blocking legacy authentication via Conditional Access.

  4. The lockout clears itself after the lockout window; a password reset by an admin also unlocks cloud sign-in.

An unhandled error has occurred. Reload 🗙