Azure AD Account Disabled or Blocked Login Attempt Failures (Sign-in Logs)

Alerts when Azure sign-in attempts fail because the target account is disabled or blocked.

FreeReviewedSigma · Medium · v5
Product
azure
Service
signinlogs
Author
Yochana Henderson, '@Yochana-H' (SigmaHQ), DRL 1.1
Published
2022-06-17
Updated
2026-07-31

ATT&CK techniques

Initial Access → Defense Evasion
  1. Recon

  2. Resource Dev

  3. Execution

  4. Cred Access

  5. Discovery

  6. Lateral Movement

  7. Collection

  8. C2

  9. Exfiltration

  10. Impact

What it detects

This rule flags sign-in attempts in Azure AD sign-in logs that fail with the specific result code indicating the target account is disabled or blocked for sign-in. Attackers may trigger these events when trying compromised or pre-disabled accounts to test access paths or probe identity controls. It relies on sign-in log telemetry fields that capture the failure ResultType and ResultDescription for the attempted authentication.

Related detections9 linkedT1078.004 — drag to rearrange
Malicious AWS Cross-Account AssumeRole With Suspicious Session Names via CloudTrail (via aws)
Suspicious Okta SSO Access to Many Applications in Short Window
Suspicious Microsoft Entra Device Code Authentication Flow
Suspicious M365 Password Spraying via Azure PowerShell AppId from Quad7 Botnet
Suspicious AWS Instance Access or Export via SSH Key or Export Task
Suspicious Azure OpenAI Model Enumeration and Deployment Creation (via azure)
Suspicious Azure Cognitive Services Account Key Enumeration via ListKeys (via azure)
Malicious Business Email Compromise OAuth Application Sign-In via Entra ID Service Principal (via azure)
Suspicious AWS API Call from TruffleHog Credential Scanner User Agent
Azure AD Account Disabled or Blocked Login Attempt Failures (Sign-in Logs)
Pivot detection · T1078.004 · 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.