Suspicious Login Issues

How to Understand Sign-In Logs for a Blocked Azure AD User

Natalie TaylorNatalie Taylor Oct 29, 2026 871 views

Question details

An administrator needs to understand why sign-in logs continue to populate for an Azure AD user who has already been blocked, specifically at regular intervals from an unfamiliar location.

How to Understand Sign-In Logs for a Blocked Azure AD User
Product
Azure Active Directory (Microsoft Entra ID)
Device & OS
not provided
Scenario
Monitoring user authentication attempts and investigating suspicious sign-in activity in Azure AD logs.
Observed behavior
Sign-in attempts continue to appear in the logs at regular 20-minute intervals even after the user account has been explicitly blocked by the administrator.
Before you start

Ensure you have global administrator or security reader permissions in your Microsoft Entra ID (formerly Azure AD) portal to view detailed sign-in logs and user statuses.

Solution 1Recommended

Analyze the Authentication Log Status

Review the log entries to confirm whether the blocked status is successfully preventing unauthorized access.

Blocking a user account does not stop external devices or automated scripts from attempting to log in; it only ensures that Microsoft Entra ID denies the request. Continuous log entries simply record these incoming attempts.

1
Access Sign-in Logs

Log in to the Microsoft Entra admin center, navigate to 'Identity', and select 'Sign-in logs' under the Monitoring section.

2
Filter for the Specific User

Use the search or filter options to isolate the log entries specifically for the blocked user experiencing the 20-minute interval attempts.

3
Verify the Authentication Status

Check the 'Status' column for these entries. If the status is 'Failure', the system is successfully rejecting the access attempt because the account is blocked. No further immediate security action is needed for failures.

4
Investigate Success Statuses

If you see a 'Success' status, the user may have authenticated through a pre-existing active session or cached token. You must immediately revoke active sessions for this user in their profile settings.

Analyze the Authentication Log Status
Identifying Automated Attempts: Repeated attempts at exact intervals (e.g., every 20 minutes) usually indicate an automated script, a scheduled task, or a legacy email client continuously trying to authenticate with outdated credentials.
Free Microsoft Office alternative

Discover WPS Office for Your Organization

While managing complex IT environments and Microsoft Entra ID security, you might be looking for cost-effective productivity tools for your users. WPS Office provides a free, lightweight, and highly compatible alternative to Microsoft Office, ensuring seamless document creation without high licensing costs.

  1. 1. Download the Installer: Visit the official WPS Office website and download the free installer for your operating system.
  2. 2. Install WPS Office: Run the downloaded file and follow the straightforward prompts to install the software.
  3. 3. Open Your Documents: Launch WPS Office and instantly open your existing Microsoft Office files without losing any formatting.
Highly compatible with Microsoft Word, Excel, and PowerPoint file formatsLightweight desktop application that requires fewer system resourcesCost-effective productivity suite with a familiar user interface for easy migrationRobust offline editing capabilities to keep local documents secure
microsoft office alternative - wps office

Frequently Asked Questions

Why do I see successful sign-ins for an Azure AD user I just blocked?

If you see a 'Success' status after blocking a user, they might have authenticated using an active session token that hasn't expired yet. You should immediately revoke their active sessions in the Microsoft Entra admin center to ensure complete access removal.

Can I stop Azure AD from logging failed sign-in attempts?

No, Microsoft Entra ID records all authentication attempts for security, compliance, and auditing purposes. You cannot disable logging for failed attempts, as this information is critical for identifying potential brute-force attacks or compromised devices.

What causes repeated failed sign-ins at exact intervals like 20 minutes?

Regularly timed failed attempts are typically caused by automated processes. This includes scripts, background sync services on mobile devices, legacy email clients, or scheduled tasks on a machine that still hold the user's old credentials and are attempting to connect to Microsoft services.