Azure Sign-in Logs: OAuth Device Code Flow Usage Detected

Alerts on Azure sign-in events showing "Device Code" usage by applications outside expected input-constrained device contexts.

FreeReviewedSigma · Medium · v5

Product: azure
Service: signinlogs
Author: Mark Morowczynski '@markmorow', Bailey Bercik '@baileybercik' (SigmaHQ), DRL 1.1
Published: 2022-06-01
Updated: 2026-07-31

Analysis Detection

ATT&CK techniques

Initial Access → Defense Evasion

Recon
Resource Dev
Initial Access
- T1078Valid Accounts
Execution
Persistence
- T1078Valid Accounts
Priv Esc
- T1078Valid Accounts
Defense Evasion
- T1078Valid Accounts
Cred Access
Discovery
Lateral Movement
Collection
C2
Exfiltration
Impact

What it detects

This rule flags Azure sign-in events where the authentication flow indicates "Device Code." Device code flow is typically expected only for input-constrained devices, so observing it outside that context may indicate a misconfigured application or malicious authentication attempts. It relies on telemetry from Azure sign-in logs that include the message field containing the "Device Code" indicator.

Reporting behind it

Related detections9 linkedT1078 — drag to rearrange

Possible Next.js Middleware Auth Bypass via X-Middleware-Subrequest Header (CVE-2025-29927)

Suspicious Brutforce with Denied Access Due to Account Restrictions Policies (via security)

Suspicious Success Login Attempt on a Windows OpenSSH Server (via security)

Suspicious SQL Server - Connection Attempt Using a Disabled Account (via application)

Suspicious Lateral Movement Detection - Based on "special Groups" Feature (via security)

Suspicious Snowflake Anomalous Client Application Associated With UNC5537 (via cloud)

Malicious Network Login Performed to Multiple Targets (via security)

Malicious RDP Reconnaissance with Valid Credentials Performed on Multiple Hosts (via security)

Malicious Local Administrator Added by Atera RMM Agent

Azure Sign-in Logs: OAuth Device Code Flow Usage Detected

Pivot detection · T1078 · 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-sign-in-logs-application-using-device-code-authentication-flow-248649b7

title: "Azure Sign-in Logs: OAuth Device Code Flow Usage Detected"
id: 837c6264-6610-49da-a547-fd2dd7d62abf
status: test
description: This rule flags Azure sign-in events where the authentication flow indicates "Device Code." Device code flow is typically expected only for input-constrained devices, so observing it outside that context may indicate a misconfigured application or malicious authentication attempts. It relies on telemetry from Azure sign-in logs that include the message field containing the "Device Code" indicator.
references:
  - https://learn.microsoft.com/en-us/entra/architecture/security-operations-applications#application-authentication-flows
  - https://github.com/SigmaHQ/sigma/blob/master/rules/cloud/azure/signin_logs/azure_app_device_code_authentication.yml
author: Mark Morowczynski '@markmorow', Bailey Bercik '@baileybercik', Huntrule Team
date: 2022-06-01
tags:
  - attack.stealth
  - attack.t1078
  - attack.persistence
  - attack.privilege-escalation
  - attack.initial-access
logsource:
  product: azure
  service: signinlogs
detection:
  selection:
    properties.message: Device Code
  condition: selection
falsepositives:
  - Applications that are input constrained will need to use device code flow and are valid authentications.
level: medium
license: DRL-1.1
related:
  - id: 248649b7-d64f-46f0-9fb2-a52774166fb5
    type: derived

Convert

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

SplunkSPL