AADSTS50057

User account is disabled

Last reviewed 2026-07-18 by the Just Software engineering team · also seen as 50057, UserDisabled, user account is disabled

What it means

AADSTS50057 — "The user account is disabled." The accountEnabled flag on the user object is false, so all sign-ins fail regardless of credentials. In hybrid environments the disabled state usually flows from on-prem AD via sync, so the fix may belong on-prem rather than in the cloud.

Common causes

  1. The account was deliberately disabled (leaver process, security response) and someone is still trying to use it — including background apps and services signing in as that user.

  2. Hybrid: the on-prem AD account is disabled and Entra Connect synced that state.

  3. Automated lifecycle tooling (HR-driven provisioning) disabled the account by rule.

How to fix it

  1. Check state: Get-MgUser -UserId <upn> -Property accountEnabled | Select accountEnabled. Re-enable in Entra admin center > Users > (user) > Edit properties > Account enabled, or Update-MgUser -UserId <upn> -AccountEnabled:$true.

  2. For synced users, enable the account in on-prem AD instead and let sync propagate — cloud-side edits to synced attributes will be overwritten.

  3. If the disable was intentional, treat the sign-in attempts as signal: find which app/device keeps trying (sign-in logs) and decommission it.

An unhandled error has occurred. Reload 🗙