Account Locked & Blocked

Investigate Microsoft 365 Account Lockouts After Pass-Through Authentication Setup

Adam DavisAdam Davis Nov 22, 2026 868 views

Question details

Identify why Microsoft 365 and on-premises Active Directory accounts are locking after pass-through authentication and seamless single sign-on are configured.

Investigate Microsoft 365 Account Lockouts After Pass-Through Authentication Setup
Product
Microsoft Entra ID and Microsoft 365 with on-premises Active Directory
Device & OS
not provided
Scenario
Users experience account lockouts after an Azure AD Pass-through Authentication and seamless single sign-on deployment, with some attempts coming from anonymous or unknown IP addresses.
Observed behavior
Accounts are repeatedly locked, and sign-in attempts may originate from unknown or anonymous IP addresses.
Before you start

Collect the affected user names and approximate lockout times, and confirm whether the lockout is in Microsoft Entra ID, on-premises Active Directory, or both. Use an account with permission to review Entra sign-in logs and relevant domain controller security logs.

Solution 1Recommended

Trace the source of the account lockouts

Use sign-in and domain controller logs to distinguish suspicious attempts from devices or applications using outdated credentials.

1
Review Entra sign-ins

In the Microsoft Entra admin center, open Monitoring & health > Sign-in logs. Filter by the affected user and lockout time, then inspect the status, authentication details, client application, and source IP address for failed attempts.

2
Check risk detections

In the Microsoft Entra admin center, open Protection > Identity Protection and review risky users and risk detections for the affected account, if available. Look for leaked credentials, anonymous IP addresses, or unfamiliar sign-in properties.

3
Correlate on-premises events

On the relevant domain controllers, open Event Viewer > Windows Logs > Security and review account lockout event 4740 around the same time. Check the caller computer name when present and correlate related authentication events, such as 4771 or 4776, where available.

4
Find saved credentials

Inspect the identified devices and applications for old passwords, including scheduled tasks, services, mobile mail accounts, saved credentials, and legacy authentication clients. Update or remove stale credentials at the source.

5
Recover and escalate

After addressing known sources, unlock the on-premises account through Active Directory Users and Computers if appropriate, and follow Microsoft Entra guidance for any cloud-side block. If lockouts continue, share timestamps, event details, and the support request number with Microsoft Support through the case's private channel.

Trace the source of the account lockouts
An anonymous IP is a lead, not proof: An anonymous IP or unfamiliar location can indicate suspicious activity, but it does not by itself prove that credentials were compromised. Correlate the sign-in details with other evidence.
Free Microsoft Office alternative

Work on Office Documents with WPS Office

WPS Office is a free, lightweight alternative with a familiar interface for working on Office documents. Its format compatibility helps make migration straightforward, but it does not resolve Microsoft Entra or Active Directory account lockouts.

Open and edit Microsoft Word, Excel, and PowerPoint formatsUse familiar document, spreadsheet, and presentation toolsWork with a lightweight office suite available for freeContinue working on local documents while an administrator investigates account access
microsoft office alternative - wps office

Frequently Asked Questions

Where can I see which IP addresses are attempting to sign in?

In the Microsoft Entra admin center, open Monitoring & health > Sign-in logs, filter for the affected user and time, and inspect the IP address and authentication details for each attempt.

Can pass-through authentication lock an on-premises account?

Yes. Pass-through authentication validates passwords against on-premises Active Directory, so repeated failed attempts can contribute to an on-premises lockout. Check domain controller Security logs for event 4740 and related authentication events.

Will Smart Lockout stop the source of bad password attempts?

No. Smart Lockout helps limit repeated sign-in attempts, but it does not find or remove their source. Review sign-in logs and check devices, services, scheduled tasks, and applications for outdated credentials.

What should I do if the logs show an anonymous IP address?

Review the sign-in's status, authentication details, time, and risk detections in Microsoft Entra ID. If compromise is suspected, follow your incident process to reset the password and revoke sessions as appropriate.