← Back to SOC feed Coverage →

Phish Detections by Threat Classification

kql MEDIUM Azure-Sentinel
T1566
EmailEvents
huntingmicrosoftofficialphishing
This rule was pulled from an open-source repository and enriched with AI. Validate in a test environment before deploying to production.
View original rule at Azure-Sentinel →
Retrieved: 2026-09-03T23:00:00Z · Confidence: medium

Hunt Hypothesis

This hypothesis targets adversaries leveraging T1566 to deliver phishing payloads, specifically identifying inbound emails classified by Microsoft Defender for Office 365 LLM content analysis as high-risk intents such as invoice or gift requests. Proactively hunting for these detections allows the SOC to isolate and investigate suspicious communications before users interact with them, thereby reducing the likelihood of credential theft or malware execution within the Azure Sentinel environment.

KQL Query

EmailEvents
| where Timestamp > ago(30d)
| where OrgLevelPolicy != "Phishing simulation" and OrgLevelPolicy != "SecOps Mailbox"
| extend Key = strcat(NetworkMessageId, "-", RecipientEmailAddress)
| summarize arg_max(Timestamp, *) by Key
| where ThreatTypes has "Phish" and ThreatClassification has_any("Business intelligence","Contact establishment","Gift card","Invoice","Payroll","PII gathering","Task")
| summarize Count = count() by ThreatClassification
| sort by Count desc
| render piechart

Analytic Rule Definition

id: a636bbbd-c6d0-4319-ae10-a06e809ba18f
name: Phish Detections by Threat Classification
description: |
  This query summarises inbound email phishing detections grouped by the message-intent threat classification produced by Microsoft Defender for Office 365 LLM content analysis (for example Invoice, Gift card, Payroll, PII gathering).
description-detailed: |
  Microsoft Defender for Office 365 uses LLM content analysis to classify the intent of phishing messages, and these threat classifications are used in filtering decisions. This query summarises inbound phishing detections grouped by that intent classification (for example Business intelligence, Contact establishment, Gift card, Invoice, Payroll, PII gathering, Task).
  Messages are de-duplicated to the latest record per NetworkMessageId and recipient, and deliveries to the SecOps mailbox and by the phishing simulation system are excluded.
requiredDataConnectors:
- connectorId: MicrosoftThreatProtection
  dataTypes:
  - EmailEvents
tactics:
  - InitialAccess
relevantTechniques:
  - T1566
query: |
  EmailEvents
  | where Timestamp > ago(30d)
  | where OrgLevelPolicy != "Phishing simulation" and OrgLevelPolicy != "SecOps Mailbox"
  | extend Key = strcat(NetworkMessageId, "-", RecipientEmailAddress)
  | summarize arg_max(Timestamp, *) by Key
  | where ThreatTypes has "Phish" and ThreatClassification has_any("Business intelligence","Contact establishment","Gift card","Invoice","Payroll","PII gathering","Task")
  | summarize Count = count() by ThreatClassification
  | sort by Count desc
  | render piechart
version: 1.0.0

Required Data Sources

Sentinel TableNotes
EmailEventsEnsure this data connector is enabled

MITRE ATT&CK Context

References

False Positive Guidance

Original source: https://github.com/Azure/Azure-Sentinel/blob/main/Hunting Queries/Microsoft 365 Defender/Email and Collaboration Queries/Phish/Phish Detections by Threat Classification.yaml