AADSTS50053: Your account is locked (Smart Lockout) / sign-in blocked due to suspicious activity
Too many failed sign-ins (or sign-ins from a malicious IP) triggered Entra Smart Lockout.
Seen on:
Azure
Meaning
Old saved passwords on phones/apps, scripts retrying with a wrong secret, or password-spray attacks lock the account temporarily. The lockout clears after its duration.
Common causes
- Devices/apps retrying an old password
- Script with wrong credentials
- Password-spray attack from known bad IPs
⚡ Quick fix
- Wait for the lockout period, then update saved passwords everywhere
- Reset the password via SSPR
- Review sign-in logs for attack IPs
Detailed fix by platform
Azure CLI
# Entra ID → Sign-in logs → filter by user, status Failure, error 50053
How to diagnose
- Sources — Failing sign-ins’ apps/IPs
- Devices — Old credentials saved?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
Most viewed in Azure
- AADSTS50076 Azure AD (Entra ID): AADSTS50076 / AADSTS50079 — multi-factor authentication required
- AuthorizationPermissionMismatch Azure Storage: AuthorizationPermissionMismatch (403) — This request is not authorized to perform this operation using this permission
- AADSTS700016 Azure AD (Entra ID): AADSTS700016 Application not found in the directory
Other ways to find it
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
Was this page helpful?
Report a correction or suggest an improvement
Last updated 7 Oct 2026