Managing external identities to enable secure access for partners, customers, and other non-employees
The 10-attempt Smart Lockout threshold is not guaranteed to produce a lockout on exactly the 11th submitted password; seeing lockout on the 11th in one test and the 15th in another can be expected because Microsoft Entra counts qualifying failures rather than every raw submission.^1^
Factors that change the observed count
- Repeated passwords might not increment the counter. Smart Lockout tracks the last three bad password hashes. Reusing the same incorrect password does not continue incrementing the counter.
- Familiar and unfamiliar locations have separate counters. Changing the source IP, network, VPN, browser path, or test location can cause attempts to be evaluated against different counters.
- Datacenter distribution introduces slight variation. Authentication requests can be processed by different Microsoft Entra datacenters. Although lockout state is synchronized, Microsoft states that the total failures permitted can vary slightly from the configured threshold.
- Other protections can block a sign-in. Microsoft Entra also evaluates IP traffic and anomalous behavior. These controls can return
AADSTS50053regardless of whether the supplied password was valid, so that code alone does not prove the configured Smart Lockout counter was reached. - Previous lockouts affect subsequent behavior. After the lockout period expires, another failed sign-in immediately locks the account again, and repeated lockouts increase the lockout duration.
- Authentication architecture matters. Bad-password hash tracking is unavailable with pass-through authentication because password validation occurs on-premises rather than in the cloud.
The default for Azure Public tenants is 10 failed attempts with an initial lockout duration of 60 seconds. Smart Lockout is always enabled, but customizing its values requires Microsoft Entra ID P1 or higher.^1^
Verify the tenant configuration
Using an account with at least the Authentication Policy Administrator role:
- Open the Microsoft Entra admin center.
- Go to Entra ID → Authentication methods → Password protection.
- Review:
- Lockout threshold
- Lockout duration in seconds
- Confirm that the external tenant itself is selected in the tenant switcher; settings in the workforce tenant do not establish what is configured in the external tenant.
Test consistently
For a controlled test:
- Use one user, one client, and one network/IP throughout the test.
- Submit a distinctly different incorrect password on each attempt. Do not alternate among only a few passwords or use minor variations.
- Avoid changing VPN endpoints or networks during the test.
- Record the timestamp and correlation details for each request.
- Review the tenant’s sign-in logs and compare the failures around the lockout event.
A failed sign-in showing AADSTS50053 means the sign-in was blocked, but correlate it with the preceding attempts rather than treating it as proof that exactly ten passwords were counted. Default anomaly protection can produce the same error.^1^
If these are actually Email One-Time Passcode attempts rather than password attempts, the numeric Smart Lockout threshold does not apply in the same way. External ID OTP validation uses service-side throttling and adaptive abuse protections, for which a fixed per-user attempt threshold is not publicly documented.^2^
References