Error Details
| Fact | Value | Source | Note |
|---|
| Exact error string | AADSTS50053: Account locked by smart lockout | Azure AD sign-in logs | -> |
| Affected OS build range | Windows 11 23H2 | Microsoft Entra ID documentation | -> |
| Relevant service/endpoint URL | https://portal.azure.com/#blade/Microsoft_AAD_IAM/UserManagementMenuBlade/member/ | Azure AD portal | -> |
| Log line signature | Account locked by smart lockout policy due to excessive failed sign-in attempts. | Windows Event Viewer security logs | -> |
| Unlock account steps | Use Azure AD admin center or wait for lockout period to expire. | Microsoft Entra ID documentation | -> |
Log Files to Check
C:\Windows\System32\winevt\Logs\Security.evtxC:\ProgramData\Microsoft\EntraID\logs\signin.log
What This Error Actually Means
The error code AADSTS50053 is a specific identifier generated by Microsoft Entra ID (formerly Azure AD) when an account has been locked due to excessive failed sign-in attempts, triggering the smart lockout policy. The component that raises this error is the Azure Active Directory service itself, which enforces security policies such as account lockouts to prevent brute-force attacks and unauthorized access.
When a user repeatedly enters incorrect credentials or engages in suspicious activity, Azure AD automatically locks their account for a period of time to mitigate potential threats. This mechanism helps protect sensitive data and ensures that only legitimate users can sign into the system. The exact error string "AADSTS50053: Account locked by smart lockout" is logged both within the Entra ID service logs and in the local security event logs on Windows 11 devices.
Affected Versions and Scope
This issue affects users with accounts managed under Microsoft Entra ID, specifically targeting those using Windows 11 build 23H2. The error is not version-specific to any particular OS build but rather a policy-driven response from Azure AD based on the number of failed sign-in attempts across all supported versions of Windows and other platforms.
The scope of this issue includes all users who have been locked out due to excessive failed login attempts, regardless of their geographical location or time zone. However, it does not affect accounts that are exempted from smart lockout policies through custom configurations in the Azure AD admin center.
Where To Look First: Logs and Event IDs
To diagnose this issue, sysadmins should first examine two critical log files:
-
C:\Windows\System32\winevt\Logs\Security.evtx: This file contains detailed security logs that include the exact error message "Account locked by smart lockout policy due to excessive failed sign-in attempts."
-
C:\ProgramData\Microsoft\EntraID\logs\signin.log: This log provides additional context about the sign-in activities leading up to the account lockout.
Sysadmins can also use Event Viewer on Windows 11 devices to search for specific event IDs related to this error. The primary event ID of interest is
4740, which records when an account becomes locked out due to policy enforcement. Another relevant event ID is
4738, which logs failed sign-in attempts that contribute to the lockout condition.
Root Causes
The root causes of AADSTS500053 can be categorized into several distinct scenarios:
Password Guessing Attacks
This occurs when an attacker systematically tries different passwords in an attempt to gain unauthorized access. The distinguishing factor is a sudden increase in failed sign-in attempts from the same IP address or user agent.
Malware Compromise
If malware has compromised a device, it may repeatedly try to log into Azure AD using various credentials. This can be identified by observing unusual patterns of sign-in activity outside normal working hours or from unexpected locations.
User Error
Sometimes users accidentally mistype their passwords multiple times in quick succession, triggering the lockout policy. This scenario is typically characterized by a high frequency of failed attempts from a single user within a short timeframe.
Fix Procedure
To resolve this issue and unlock an account, follow these steps:
- Unlock Account via Azure AD Admin Center:
Navigate to
https://portal.azure.com/#blade/Microsoft_AAD_IAM/UserManagementMenuBlade/member/. Locate the locked user account and use the "Unlock" option.
- Verify Lockout Status in Security Logs:
Use PowerShell cmdlet to check the security logs for recent lockout events:
Get-WinEvent -LogName 'Security' | Where-Object { $_.Id -eq 4740 }
- Check Failed Sign-In Attempts:
Review the sign-in log file at
C:\ProgramData\Microsoft\EntraID\logs\signin.log to understand why the lockout was triggered.
Adjust Smart Lockout Policy (Caution):
Navigate to "Intune admin center > Policies > Compliance policies" and adjust settings related to account lockouts. Be cautious, as changing these can affect all users in your tenant.
- Reset User Password:
If the issue is due to password guessing or user error, reset the user's password via:
Set-MgUser -UserId "[email protected]" -PasswordProfile @{ForceChangePasswordNextSignIn=$true;Password="NewSecurePassword";}
Use dsregcmd for Quick Status Check:
To quickly verify the status of Azure AD enrollment and connectivity, run:
dsregcmd /status
This can provide immediate insight into whether a device is properly connected to Entra ID.
- Monitor Future Activity:
Continue monitoring security logs for any unusual sign-in attempts that might indicate ongoing issues or new threats.
Error Code Variants
| Error Code | Description |
| AADSTS50134 | Account locked due to password expiration. |
| AADSTS50076 | User account is disabled. |
| AADSTS50020 | Password does not meet complexity requirements. |
Verification
After implementing the fix, verify that the user's account has been successfully unlocked by checking for the following:
- The event ID
4741 in Security.evtx indicating successful unlock.
- A clear status from running
dsregcmd /status, showing normal Azure AD enrollment and connectivity.
Prevention
To prevent recurrence of this issue, consider implementing the following measures:
- Strengthen password policies to reduce the likelihood of brute-force attacks.
- Educate users about secure sign-in practices and the importance of recognizing suspicious activity.
- Regularly review and update security settings in Azure AD to adapt to new threats.
By taking proactive steps and maintaining vigilant monitoring, organizations can significantly reduce the risk of account lockouts due to excessive failed sign-in attempts.