Azure Sign-in Auth Interruption: DeviceAuthenticationRequired/Failed and External Security Challenge

Alerts on Azure sign-in authentication interruptions tied to device authentication and external security challenge failures.

FreeReviewedSigma · Medium · v5
Product
azure
Service
signinlogs
Author
Austin Songer @austinsonger (SigmaHQ), DRL 1.1
Published
2021-11-26
Updated
2026-07-31

ATT&CK techniques

Initial Access → Defense Evasion
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Defense Evasion

  6. Cred Access

  7. Discovery

  8. Lateral Movement

  9. Collection

  10. C2

  11. Exfiltration

  12. Impact

What it detects

This rule flags Azure sign-in events where authentication is interrupted or not completed, including cases indicating device authentication is required, device authentication failure, or an unsatisfied external security challenge. Attackers may force or exploit authentication breakpoints to evade access controls or disrupt sign-in flows before continuing with privilege escalation or persistence attempts. Detection relies on Azure sign-in log fields capturing specific ResultType values and their associated ResultDescription text.

Related detections9 linkedT1078 — drag to rearrange
Suspicious Self-Hosted GitHub Actions Runner Started As Root via Shell (via process_creation)
Suspicious Login Shell Assigned to Service Account games on Linux
Suspicious SSH Daemon Configuration Change Enabling Root Login
Suspicious NTLM Network Logon From Attacker Controlled Workstation Names (via security)
Suspicious dMSA Object Access with Migration AccessMask
Malicious ESX Admins Group Added to Privileged Directory Group
Malicious ESX Admins Group Creation via WinRM Host
Suspicious BrightMetricAgent Remote Tool Execution Associated With Volt Typhoon
Suspicious SmarterMail Force Password Reset API Request Indicating Account Takeover
Azure Sign-in Auth Interruption: DeviceAuthenticationRequired/Failed and External Security Challenge
Pivot detection · T1078 · 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.