Azure Sign-In Logs: Device Registration or Join Success Without MFA

Flags successful device registration/join attempts in Azure when MFA was not performed per Conditional Access.

FreeReviewedSigma · Medium · v5
Product
azure
Service
signinlogs
Author
Michael Epping, '@mepples21' (SigmaHQ), DRL 1.1
Published
2022-06-28
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 identifies successful device registration or device join events in Azure sign-in logs where MFA was not performed. Attackers can use device registration without MFA to establish persistence or initial access while reducing friction from authentication controls. The detection relies on sign-in log fields indicating a successful device registration/join service and the absence of multiFactorAuthentication in the authentication requirement telemetry.

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 Sign-In Logs: Device Registration or Join Success Without MFA
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.