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

Recon
Resource Dev
Initial Access
- T1078.004Cloud Accounts
Execution
Persistence
- T1078.004Cloud Accounts
Priv Esc
- T1078.004Cloud Accounts
Defense Evasion
- T1078.004Cloud Accounts
Cred Access
Discovery
Lateral Movement
Collection
C2
Exfiltration
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.

Reporting behind it

Related detections9 linkedT1078.004 — drag to rearrange

Suspicious Google Cloud Function Create or Update Triggering Build

Possible Credential Stuffing Blocked by Conditional Access in Microsoft 365

Suspicious SES Account Sending Enablement and Identity Verification via CloudTrail

Possible Stolen AWS Credential Validation via STS GetCallerIdentity

Suspicious AWS Federated Console Login From Programmatic Credentials

Suspicious M365 Legacy Authentication via BAV2ROPC Client via m365

Suspicious STS AssumeRole With Exfil Session Name via CloudTrail (via cloudtrail)

Suspicious AWS Console Login Without MFA

Suspicious Cloud Sign-In From an Anonymizer or High-Risk Session (via signinlogs)

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

Pivot detection · T1078.004 · 9 related

Changelog

v5
Candidate ingested via manual entry.2026-07-31
v4
Candidate ingested via manual entry.2026-07-31
v3
Candidate ingested via manual entry.2026-07-31
v2
Candidate ingested via manual entry.2026-07-31
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.

azure-entra-sign-in-logs-account-disabled-or-blocked-on-failed-login-attempts-4afac85c

title: Azure AD Account Disabled or Blocked Login Attempt Failures (Sign-in Logs)
id: f0dbd13b-4444-43f8-9a1e-f48d260bc0c1
status: test
description: 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.
references:
  - https://learn.microsoft.com/en-gb/entra/architecture/security-operations-privileged-accounts
  - https://github.com/SigmaHQ/sigma/blob/master/rules/cloud/azure/signin_logs/azure_blocked_account_attempt.yml
author: Yochana Henderson, '@Yochana-H', Huntrule Team
date: 2022-06-17
tags:
  - attack.privilege-escalation
  - attack.persistence
  - attack.initial-access
  - attack.stealth
  - attack.t1078.004
logsource:
  product: azure
  service: signinlogs
detection:
  selection:
    ResultType: 50057
    ResultDescription: Failure
  condition: selection
falsepositives:
  - Account disabled or blocked in error
  - Automation account has been blocked or disabled
level: medium
license: DRL-1.1
related:
  - id: 4afac85c-224a-4dd7-b1af-8da40e1c60bd
    type: derived

Convert

This rule as a query you can run. Uses no unlock credit.

SplunkSPL