Microsoft Entra ID Smart Lockout: Prevent Brute-Force Password Attacks

Learn how Microsoft Entra ID Smart Lockout works, when to configure it, and best practices to prevent brute-force and password spray attacks.
SHARE THIS BLOG:
Table of contents
Introduction – The Brute-Force Attack Problem & Smart Lockout Solution
What Is Microsoft Entra ID Smart Lockout and How Does It Work?
How to Configure Smart Lockout Settings in Entra ID
Prerequisites
Step-by-Step Configuration
How to Verify and Test Smart Lockout
What Users See When Locked Out
How to Test Smart Lockout Safely
Verify Lockout in Sign-In Logs
What Happens After Lockout
Best Practices for Using Smart Lockout Effectively
Choose the Right Threshold
Set Smart Duration
Educate Your Team
Review Quarterly
Why Trust Penthara Technologies for Microsoft Entra ID Smart Lockout?
Frequently Asked Questions (FAQs)

Introduction – The Brute-Force Attack Problem & Smart Lockout Solution

Every day, attackers try to break into Microsoft 365 accounts. They don't need fancy malware - just common passwords and a list of usernames.

Here's how they do it:

Brute-force attacks – Rapidly guessing thousands of password combinations against one account.

Password spray attacks – Trying common passwords like "Winter2024!" across hundreds of accounts to avoid detection.

The result? Compromised accounts, stolen data, and major security incidents.

Why Old Lockout Policies Don't Work

Traditional on-premises lockout policies locked accounts after failed login attempts. The problem? They couldn't tell attackers from real users who forgot their password.

Everyone got locked out equally. Attackers even used this to intentionally lock out users.

The Smart Lockout Solution

Microsoft Entra ID Smart Lockout (also called Azure AD Smart Lockout) uses intelligence to stop attacks while keeping real users working.

When an attacker tries thousands of passwords, Smart Lockout blocks them.

When your user mistypes their password twice, nothing happens. They stay unaffected.

Smart Lockout is one of the top identity configurations that improve your Secure Score in Microsoft Entra — it's a low-effort setting with a direct impact on how Microsoft evaluates your tenant's identity posture.

Traditional Lockout Policies

What Is Microsoft Entra ID Smart Lockout and How Does It Work?

Microsoft Entra ID Smart Lockout (also called Azure AD Smart Lockout) is a security feature that automatically locks out accounts after repeated failed sign-in attempts.

What makes it "smart"? It tells the difference between an attacker and a real user who forgot their password.

It's enabled by default. No setup required.

Default Settings

  • Lockout threshold: 10 failed attempts
  • Lockout duration: 1 minute (increases with repeated attacks)

The Key Difference: Two Separate Counters

Traditional lockout policies locked everyone out equally. If an attacker tried 10 wrong passwords, you couldn't log in either - even from your own device.

Smart Lockout fixes this.

It tracks failed attempts based on location:

Familiar locations – IP addresses where you've successfully logged in before (office, home).

Unfamiliar locations – New or suspicious IPs.

An attacker in another country hits the unfamiliar counter and gets locked out after 10 attempts.

You, logging in from your office, use the familiar counter. You stay unaffected.

The attacker gets blocked. You don't.

Risk-Based Blocking

Smart Lockout also uses Microsoft's intelligence to block suspicious sign-ins based on:

  • Known malicious IPs
  • Bot-like behavior
  • Unusual locations or timing

When blocked, users see the AADSTS50053 error.

The Result

Attackers get stopped. Legitimate users keep working. Smart Lockout prevents brute-force and password spray attacks without disrupting your workforce.

What happens during a smart lockout event?

How to Configure Smart Lockout Settings in Entra ID

Smart Lockout is already enabled by default in your tenant. But you might want to customize the settings to fit your security needs.

Here's everything you need to know before you start - and how to configure it step by step.

Prerequisites

Before you configure Smart Lockout, make sure you have:

Licensing

Smart Lockout works for everyone at default settings. But to customize the lockout threshold or duration, you need Microsoft Entra ID Premium P1 or higher.

Premium P1 is included in:

  • Microsoft 365 E3 or E5
  • Enterprise Mobility + Security E3/E5
  • Microsoft 365 Business Premium

Step-by-Step Configuration

  1. Sign in to the Microsoft Entra admin centeras at least an Authentication Policy Administrator.
  2. Navigate to Entra IDAuthentication methods > Password protection.
Microsoft Entra admin center showing Entra ID section expanded with Authentication methods selected in the left navigation pane.
  1. Set the Lockout threshold, based on how many failed sign-ins are allowed on an account before its first lockout.

The default is 10 for Azure Public tenants and 3 for Azure US Government tenants.

  1. You'll see two key fields:
  • Lockout threshold – Number of failed sign-in attempts before lockout (default: 10)

The lockout threshold controls how many failed attempts trigger a lockout.

  • Lockout duration in seconds – How long the lockout lasts (default: 60 seconds)

The lockout duration sets how long an account stays locked after hitting the threshold.

Modify the Lockout Threshold default values as required.

NOTE: If the first sign-in after a lockout period has expired also fails, the account locks out again. If an account locks repeatedly, the lockout duration increases.

Microsoft Entra Password protection settings showing custom smart lockout configuration with lockout threshold, lockout duration, and enforced password protection options.
  1. To modify the default values, click in the Lockout threshold field, enter a value between 1 and 50.

Example settings:

  • 5 attempts – More secure, stricter protection
  • 10 attempts – Microsoft's default, balanced approach
  • 15 attempts – More lenient for environments with frequent password mistakes

Lower numbers increase security but may lock out legitimate users more often.

  1. To modify the default values, click in the Lockout duration in seconds field, enter a value between 5 and 18,000 seconds (5 seconds to 5 hours).

Example settings:

  • 60 seconds (1 minute) – Default, minimal disruption
  • 300 seconds (5 minutes) – Gives security teams time to investigate
  • 600 seconds (10 minutes) – Stronger deterrent for attackers

Longer durations slow down attackers but may frustrate legitimate users.

  1. Click Save at the top of the page and your new settings take effect immediately for all future sign-in attempts.

Example Configuration

Let's say your organization wants tighter security:

Lockout threshold: 5 failed attempts
Lockout duration: 120 seconds (2 minutes)

This means any account with 5 incorrect password entries gets locked for at least 2 minutes.

This configuration stops attackers faster while still allowing legitimate users a few chances to get their password right.

How to Verify and Test Smart Lockout

After configuring Smart Lockout, you'll want to confirm it's actually working.

Here's how to safely test it without disrupting real users.

What Users See When Locked Out

When Smart Lockout triggers, users see this message:

"Your account is temporarily locked to prevent unauthorized use. Try again later, or contact your admin for assistance."

Microsoft sign-in page displaying an account temporarily locked message after repeated incorrect password attempts.

This appears on the sign-in screen and indicates the lockout is active.

The error code behind this message is AADSTS50053 (IdsLocked).

How to Test Smart Lockout Safely

Never test on production user accounts. Create a test account instead.

Here's the testing process:

  1. Create a test user account in Entra ID (or use an existing test account).
  2. Open an InPrivate or Incognito browser window to simulate an unfamiliar location.
  3. Try signing in with the wrong password repeatedly.
  4. Count your attempts. After you hit your threshold (default is 10), you should see the lockout message.
  5. Try one more time. You'll stay locked out until the duration expires.

Pro tip: Use a VPN or different network to simulate an attacker from an unfamiliar IP address. This helps you see how Smart Lockout blocks unfamiliar locations while potentially allowing familiar ones.

3-Step Smart Lockout Test

Verify Lockout in Sign-In Logs

To confirm Smart Lockout is working, check the logs.

Navigate to: Entra ID → Monitoring & health → Sign‑in logs

Microsoft Entra admin center showing Sign-in logs under Monitoring and health with interactive user sign-ins selected.

As an administrator, it is crucial to actively monitor Azure AD sign-in reports to identify any accounts that may be under attempted compromise. You can spot locked accounts by recognizing the AADSTS50053 – IdsLocked error code.

Next, locate the failed user with sign-in error code 50053, and proceed to analyze the cause of the failure.

Microsoft Entra sign-in activity details showing the Authentication details tab with a failed password sign-in and incorrect password result.

What to look for:

  • Status: Failure
  • Error code: 50053 (IdsLocked)
  • Failure reason: "The account is locked. The user has tried to sign in too many times with an incorrect user ID or password."
Microsoft Entra sign-in activity details displaying error code 50053 indicating the account is locked due to multiple failed sign-in attempts.

This confirms Smart Lockout blocked the attempts.

What Happens After Lockout

Once the lockout duration expires, the account automatically unlocks.

No manual action required.

If you're testing and don't want to wait, you can reset the test account's password. This immediately clears the lockout.

  • Reset passwords with SSPR: Users can independently initiate a self-service password reset to unlock their accounts.
  • Reset User Password as Admin: If Self-Service Password Reset (SSPR) is not enabled, administrators can reset the user’s password from the Microsoft 365 admin center to unblock the account.

Best Practices for Using Smart Lockout Effectively

Smart Lockout works well by default. These best practices will help you optimize it.

Choose the Right Threshold

Too low (3-5): Users lock themselves out. Attackers can weaponize it.

Too high (15-20): Attackers get more chances to guess passwords.

Recommended: Start with 10 attempts. Lower to 5-8 if you see frequent attacks. Raise to 12-15 if legitimate users lock out often.

Choose the right threshold for Smart Lockout

Set Smart Duration

Too short (60 seconds): Attackers resume quickly.

Too long (hours): Users get frustrated.

Recommended: Use 5 minutes (300 seconds) for most environments. High-security? Try 10 minutes.

Educate Your Team

Train users: Don't keep guessing passwords. Use "Forgot password" instead.

Train helpdesk: Check logs before resetting. Look for attack patterns.

Review Quarterly

Are lockouts increasing? Have threats changed? Adjust settings accordingly.

Smart Lockout is a reactive control - it kicks in after failed attempts. enabling MFA in Microsoft 365 means that even if an attacker somehow guesses the right password, they still cannot get in without the second factor.

If you want to go beyond mitigating brute force, passwordless authentication eliminates the password attack surface entirely - removing the password means there is nothing to guess in the first place.

4 Smart Lockout Best Practices

Why Trust Penthara Technologies for Microsoft Entra ID Smart Lockout?

Microsoft Solutions Partner Expertise

As a certified Microsoft Solutions Partner, we align official Microsoft security guidance with hands-on deployment experience. We ensure Microsoft Entra ID Smart Lockout is configured correctly and integrated into your broader identity protection strategy.

Entra ID Security Specialists

Our team specializes in:

  • Smart Lockout threshold and duration tuning
  • Password Protection and banned password policies
  • Conditional Access integration
  • MFA and identity hardening
  • Monitoring AADSTS50053 (IdsLocked) events

We balance strong security with minimal user disruption.

Compliance-Aligned Identity Protection

We design Smart Lockout configurations that support ISO 27001, SOC 2, HIPAA, and GDPR requirements by ensuring:

  • Controlled authentication protections
  • Logged and auditable lockout events
  • Secure password reset workflows
  • Ongoing monitoring and reporting

Practical, Real-World Experience

We’ve helped organizations defend against password spray, brute-force, and credential stuffing attacks. Our approach ensures Smart Lockout works effectively across cloud-only and hybrid environments.

Strengthen Your Identity Security

Let Penthara Technologies help you configure and optimize Microsoft Entra ID Smart Lockout for secure, reliable protection against credential-based attacks.

Schedule a consultation to secure your environment today.

Why Trust Penthara Technologies?

Frequently Asked Questions (FAQs)

What is the default lockout threshold and duration?

By default, Smart Lockout locks accounts after 10 failed sign-in attempts for 60 seconds (1 minute).

These settings apply automatically to all Entra ID tenants.

Do I need a Premium license to use Smart Lockout?

No. Basic Smart Lockout protection is free for all Entra ID users.

But to customize the threshold or duration, you need Microsoft Entra ID Premium P1 or higher. This is included in Microsoft 365 E3/E5, Enterprise Mobility + Security E3/E5, and Microsoft 365 Business Premium.

Does Smart Lockout lock out real users?

Rarely. Smart Lockout uses separate counters for familiar and unfamiliar locations, so legitimate users usually stay unaffected.

You could still get locked out if:

  • You travel to a new location and mistype your password repeatedly
  • An attacker uses the same network as you

If locked out, wait for the duration to expire or use self-service password reset.

How do I unlock a locked account?

You don't need to. Accounts auto-unlock after the lockout duration expires.

For faster access:

  • The user can reset their password via self-service password reset
  • An admin can reset the password manually

Both methods clear the lockout immediately.

Does Smart Lockout work with MFA or passwordless authentication?

Yes. Smart Lockout monitors failed password attempts even when MFA is enabled.

It's an additional layer of defense. If an attacker guesses a password but MFA blocks them, Smart Lockout still protects against the guessing attempts themselves.

Even in passwordless environments, accounts have underlying passwords that could be attacked - so Smart Lockout remains relevant.

Does Smart Lockout apply to on-premises AD accounts?

Not directly. Smart Lockout works in the cloud (Entra ID).

For cloud-only or password hash sync: Smart Lockout fully protects these accounts.

For pass-through authentication: Smart Lockout can act as a buffer to prevent attacks from reaching on-premises AD (if configured properly).

For ADFS: Use ADFS Extranet Smart Lockout instead for on-premises protection.

What is the AADSTS50053 error?

This error code means Smart Lockout blocked a sign-in attempt.

It indicates either:

  • The account is temporarily locked due to failed attempts
  • Microsoft's risk detection blocked a suspicious sign-in

If you see AADSTS50053 in sign-in logs, Smart Lockout is actively protecting that account from potential attacks.

Can Smart Lockout prevent password spray attacks?

Yes. Password spray attacks try common passwords across many accounts.

Smart Lockout detects these patterns and locks out accounts after the threshold is reached-stopping the attack before it succeeds.

Combined with Password Protection (banned password lists), you get even stronger defense against password spraying.

What's the difference between Smart Lockout and traditional account lockout?

Traditional lockout locks everyone out after failed attempts-including legitimate users from their own devices.

Smart Lockout uses intelligence to differentiate attack patterns from real users. It tracks separate counters for familiar and unfamiliar locations, so attackers get blocked while real users stay productive.

How do I monitor Smart Lockout activity?

Navigate to Monitoring & health > Sign-in logs in the Entra Admin Center.

Filter by:

  • Status: Failure
  • Error code: 50053

This shows all lockout events. Review these logs regularly to spot attack patterns and adjust your settings.

Does Smart Lockout prevent credential stuffing attacks?

Yes. Credential stuffing uses stolen username/password pairs from other breaches.

Smart Lockout detects rapid failed login attempts and blocks them-even if the attacker is using "real" credentials from other sites.

Combine with MFA and Password Protection for maximum defense.

Why does the lockout duration increase over time?

After the first lockout, repeated attacks trigger progressively longer lockout periods.

This adaptive behavior makes attacks increasingly impractical for attackers. The exact duration increase isn't disclosed to prevent attackers from gaming the system.

Can attackers bypass Smart Lockout?

Smart Lockout significantly raises the difficulty and cost of attacks, but determined attackers might:

  • Use distributed IP addresses to stay below thresholds per location
  • Target accounts with weak passwords that succeed before lockout

This is why you should layer defenses: Smart Lockout + MFA + Password Protection + monitoring.

Does Smart Lockout reset the counter after successful login?

No. The failed attempt counter persists until the lockout duration expires-even if a successful login occurs from another location.

This prevents attackers from resetting the counter by mixing valid credentials with attack attempts.

Can I configure different Smart Lockout settings for different users?

No. Smart Lockout applies tenant-wide settings to all users.

You cannot set different thresholds for specific users or groups. All users in your tenant follow the same policy.

Jasjit Chopra
Jasjit Chopra

CEO at Penthara Technologies

About the Author

Microsoft MVP LogoLinked-in

Jasjit Chopra is the CEO of Penthara Technologies and a Microsoft Most Valuable Professional (MVP) with over two decades of hands-on experience in Microsoft 365, SharePoint, and Security. He has led 100+ digital transformation projects across six countries, securing 50,000+ users, migrating 250+ TB of data, and automating processes that save organizations thousands of hours each year. A recognized leader at the crossroads of AI, security, and workplace modernization, Jasjit is passionate about simplifying complexity, mentoring technology professionals, and helping businesses build secure, intelligent, and future-ready digital environments.

More From This Category

How to Block USB Devices and Protect Corporate Data 

Learn how to block USB devices in Microsoft 365 using Intune and Defender to stop data theft, malware, and unauthorized file transfers.

Read More
Set Up Device Enrollment in Microsoft Intune – The Right Way - 2026 Guide

Learn how to set up Microsoft Intune device enrollment, choose the right method for Windows, iOS, Android, and macOS, and avoid common setup mistakes.

Read More
Full Wipe vs Selective Wipe in Intune: What IT Admins Need to Know

Learn how Intune full wipe and selective wipe work, when to use them, and best practices for secure device management in BYOD and corporate environments.

Read More
1 2 3 8
chevron-right