Entra ID Non-Passkey Sign-In with Unusual Browser and OS

Last updated a month ago on 2026-10-21
Created a month ago on 2026-10-21

About

Identifies a successful Microsoft Entra ID sign-in from a browser and operating system combination not previously seen for the user, without a phishing-resistant method and not from an Entra-joined or registered device. Adversary-in-the-middle proxies often present a spoofed client fingerprint, including impossible pairings such as Safari on Windows, to suppress the passkey prompt and force a phishable fallback. A genuinely new client also triggers this rule, so corroborate with source and authentication context.
Tags
Domain: CloudDomain: IdentityPlatform: Entra IDPlatform: AzureData Source: Entra ID Sign-In LogsUse Case: Identity and Access AuditUse Case: Threat DetectionTactic: Credential AccessThreat: AiTM PhishingRule Type: New TermsProfile: BetaLanguage: kuery
Severity
medium
Risk Score
47
MITRE ATT&CK™

Credential Access (TA0006)(external, opens in a new tab or window)

False Positive Examples
A legitimate new or rare client (a new operating system, a newly adopted browser, a privacy-hardened or developer browser, or a corporate kiosk/appliance) produces a new browser/OS combination the first time the user is seen on it. The device-trust filter already excludes the user's Entra-joined and registered endpoints, so the residual false positives are first sign-ins from genuinely unmanaged personal devices (BYOD, a home laptop, a new phone). Baseline the browser and OS families that are normal for the user and add exceptions for sanctioned clients, and correlate the source IP, ASN, and the authentication methods completed in the session before escalating.
License
Elastic License v2(external, opens in a new tab or window)

Definition

Rule Type
New Terms Rule
Integration Pack
Prebuilt Security Detection Rules
Index Patterns
logs-azure.signinlogs-*
Related Integrations

azure(external, opens in a new tab or window)

Query
text code block:
data_stream.dataset: "azure.signinlogs" and azure.signinlogs.category: "SignInLogs" and azure.signinlogs.properties.authentication_details.authentication_method: (* and not ( "Passkey (synced)" or "Passkey (device-bound)" or "FIDO2 security key" or "Windows Hello for Business" or "Previously satisfied" )) and not azure.signinlogs.properties.device_detail.trust_type: * and user.name: * and user_agent.name: * and azure.signinlogs.properties.device_detail.operating_system: * and event.outcome: "success"

Install detection rules in Elastic Security

Detect Entra ID Non-Passkey Sign-In with Unusual Browser and OS in the Elastic Security detection engine by installing this rule into your Elastic Stack.

To setup this rule, check out the installation guide for Prebuilt Security Detection Rules(external, opens in a new tab or window).