AADSTS50034: The user account does not exist in the directory
There’s no user with that sign-in name in the tenant.
Seen on:
Azure
Meaning
Often a typo, a UPN that differs from the email, an account created in a different tenant, or a user deleted/not yet synced from on-premises AD.
Common causes
- Typo or using email instead of UPN
- User in another tenant
- User deleted or not yet synced (Entra Connect)
- Personal account used for a work-only app
⚡ Quick fix
- Check the user’s UPN in Entra ID
- Wait for/force directory sync
- Use the right account/tenant
Detailed fix by platform
Azure CLI
az ad user show --id user@contoso.com --query userPrincipalName
How to diagnose
- User — Exists in this tenant?
- UPN — Matches what was typed?
- Sync — Last sync time
🔧 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
- AADSTS500113 AADSTS500113: No reply address is registered for the application
- AADSTS50020 AADSTS50020: User account from identity provider does not exist in tenant and cannot access the application
- AADSTS50053 AADSTS50053: Your account is locked (Smart Lockout) / sign-in blocked due to suspicious activity
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