Azure AD Sign-in Success Without MFA (Single-Factor Authentication)

Alerts on successful Azure AD sign-ins where MFA was not required and only single-factor authentication was used.

FreeReviewedSigma · Low · v5
Product
azure
Service
signinlogs
Author
MikeDuddington, '@dudders1' (SigmaHQ), DRL 1.1
Published
2022-07-27
Updated
2026-07-31

ATT&CK techniques

Initial Access → Cred Access
  1. Recon

  2. Resource Dev

  3. Execution

  4. Discovery

  5. Lateral Movement

  6. Collection

  7. C2

  8. Exfiltration

  9. Impact

What it detects

This rule identifies successful Azure AD sign-ins where the authentication requirement is single-factor authentication, indicating MFA was not required for the attempt. Attackers may use weaker authentication paths to reduce friction and maintain stealth, especially if conditional access or policies are misconfigured or bypassed. Detection relies on Azure sign-in log fields indicating successful status and the reported authentication requirement.

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 Sign-in Success Without MFA (Single-Factor Authentication)
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.