M365 Identity OAuth Phishing via First-Party Microsoft Application

Last updated 2 months ago on 2025-12-17
Created 9 months ago on 2025-04-23

About

Detects potentially suspicious OAuth authorization activity in Microsoft 365 where first-party Microsoft applications from the FOCI (Family of Client IDs) group request access to Microsoft Graph or legacy Azure AD resources. Developer tools like Azure CLI, Visual Studio Code, and Azure PowerShell accessing these resources are flagged, as they are commonly abused in phishing campaigns like ConsentFix. Additionally, any FOCI family application accessing the deprecated Windows Azure Active Directory resource is flagged since this API is rarely used legitimately and attackers target it for stealth. First-party apps are trusted by default in all tenants and cannot be blocked, making them ideal for OAuth phishing attacks.
Tags
Domain: CloudDomain: SaaSData Source: Microsoft 365Data Source: Microsoft 365 Audit LogsUse Case: Identity and Access AuditTactic: Initial AccessLanguage: kuery
Severity
medium
Risk Score
47
MITRE ATT&CK™

Initial Access (TA0001)(external, opens in a new tab or window)

License
Elastic License v2(external, opens in a new tab or window)

Definition

Rule Type
Query (Kibana Query Language)
Integration Pack
Prebuilt Security Detection Rules
Index Patterns
logs-o365.audit-*
Related Integrations

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

Query
text code block:
event.dataset: "o365.audit" and event.action: "UserLoggedIn" and o365.audit.ExtendedProperties.RequestType: "OAuth2:Authorize" and o365.audit.ExtendedProperties.ResultStatusDetail: "Redirect" and o365.audit.UserType: ("0" or "2" or "3" or "5" or "6" or "10") and ( ( o365.audit.ApplicationId: ( "aebc6443-996d-45c2-90f0-388ff96faa56" or "04b07795-8ddb-461a-bbee-02f9e1bf7b46" or "1950a258-227b-4e31-a9cf-717495945fc2" ) and o365.audit.Target.ID: ( "00000003-0000-0000-c000-000000000000" or "00000002-0000-0000-c000-000000000000" ) ) or ( o365.audit.ApplicationId: ( "00b41c95-dab0-4487-9791-b9d2c32c80f2" or "1fec8e78-bce4-4aaf-ab1b-5451cc387264" or "26a7ee05-5602-4d76-a7ba-eae8b7b67941" or "27922004-5251-4030-b22d-91ecd9a37ea4" or "4813382a-8fa7-425e-ab75-3b753aab3abb" or "ab9b8c07-8f02-4f72-87fa-80105867a763" or "d3590ed6-52b3-4102-aeff-aad2292ab01c" or "872cd9fa-d31f-45e0-9eab-6e460a02d1f1" or "af124e86-4e96-495a-b70a-90f90ab96707" or "2d7f3606-b07d-41d1-b9d2-0d0c9296a6e8" or "844cca35-0656-46ce-b636-13f48b0eecbd" or "87749df4-7ccf-48f8-aa87-704bad0e0e16" or "cf36b471-5b44-428c-9ce7-313bf84528de" or "0ec893e0-5785-4de6-99da-4ed124e5296c" or "22098786-6e16-43cc-a27d-191a01a1e3b5" or "4e291c71-d680-4d0e-9640-0a3358e31177" or "57336123-6e14-4acc-8dcf-287b6088aa28" or "57fcbcfa-7cee-4eb1-8b25-12d2030b4ee0" or "66375f6b-983f-4c2c-9701-d680650f588f" or "9ba1a5c7-f17a-4de9-a1f1-6178c8d51223" or "a40d7d7d-59aa-447e-a655-679a4107e548" or "a569458c-7f2b-45cb-bab9-b7dee514d112" or "b26aadf8-566f-4478-926f-589f601d9c74" or "c0d2a505-13b8-4ae0-aa9e-cddd5eab0b12" or "d326c1ce-6cc6-4de2-bebc-4591e5e13ef0" or "e9c51622-460d-4d3d-952d-966a5b1da34c" or "eb539595-3fe1-474e-9c1d-feb3625d1be5" or "ecd6b820-32c2-49b6-98a6-444530e5a77a" or "f05ff7c9-f75a-4acd-a3b5-f4b6a870245d" or "f44b1140-bc5e-48c6-8dc0-5cf5a53c0e34" or "be1918be-3fe3-4be9-b32b-b542fc27f02e" or "cab96880-db5b-4e15-90a7-f3f1d62ffe39" or "d7b530a4-7680-4c23-a8bf-c52c121d2e87" or "dd47d17a-3194-4d86-bfd5-c6ae6f5651e3" or "e9b154d0-7658-433b-bb25-6b8e0a8a7c59" ) and o365.audit.Target.ID: "00000002-0000-0000-c000-000000000000" ) )

Install detection rules in Elastic Security

Detect M365 Identity OAuth Phishing via First-Party Microsoft Application 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).