huntrule

Azure AD Sign-In Logs: Account Locked After Too Many Failed Password/User ID Attempts

Flags Azure sign-in events where accounts are locked due to excessive failed logons from wrong user ID or password.

FreeReviewedSigma · Medium · v5
Product
azure
Service
signinlogs
Author
AlertIQ (SigmaHQ), DRL 1.1
Published
2021-10-10
Updated
2026-07-31
AnalysisDetection

ATT&CK techniques

Cred Access

  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Cred Access

  9. Discovery

  10. Lateral Movement

  11. Collection

  12. C2

  13. Exfiltration

  14. Impact

What it detects

This rule flags sign-in events where a user account becomes locked after repeated failed authentication attempts due to an incorrect user ID or password. Lockouts are a common attacker impact mechanism during credential guessing because they can be used to force account state changes and disrupt access. It relies on Azure sign-in telemetry indicating the ResultType associated with account lockout (50053).

Reporting behind it

Related detections9 linkedT1110 — drag to rearrange
Malicious SQL Server - Brutforce Enumeration with Non Existing Users - Login (via application)
Malicious Brutforce Enumeration with Non Existing Users - Login (via security)
Malicious Brutforce Enumeration on Windows OpenSSH Server with Non Existing User (via security)
Malicious Brutforce on Windows OpenSSH Server with Valid Users (via security)
Malicious RDP Discovery Performed on Multiple Hosts (via rdp)
Possible SonicWall Credential Testing via userLogin Endpoint
Malicious Brutforce Enumeration with Unexisting Users - Kerberos (via security)
Suspicious JumpCloud Password Brute Force Followed by Success
AWS CloudTrail ConsoleLogin Failed authentication
Azure AD Sign-In Logs: Account Locked After Too Many Failed Password/User ID Attempts
Pivot detection · T1110 · 9 related

Changelog

v5
  1. v5
    Candidate ingested via manual entry.2026-07-31
  2. v4
    Candidate ingested via manual entry.2026-07-31
  3. v3
    Candidate ingested via manual entry.2026-07-31
  4. v2
    Candidate ingested via manual entry.2026-07-31
  5. v1
    No changelog recorded for this version.2026-07-30

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.