Malicious Azure AD Application Consent Granted with Mail Permissions

PremiumReviewedSigma · High · v1
Product
azure
Service
auditlogs
Author
HuntRule
Published
2026-11-02
Updated
2026-11-02

ATT&CK techniques

Defense Evasion → Lateral Movement
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Discovery

  8. Collection

  9. C2

  10. Exfiltration

  11. Impact

What it detects

This rule detects an Azure AD consent grant to an application that requests mailbox permissions such as Mail.Read, Mail.Send or offline_access. It maps to illicit consent phishing where an attacker tricks a user into authorising a malicious OAuth application for persistent mailbox access. Detecting it exposes token-based access to corporate mail without credential theft.

Related detections9 linkedT1528 — drag to rearrange
Possible Illicit Consent Grant to OAuth Application via Azure AD
Malicious PRT Token Forging via AADInternals (via ps_script)
Suspicious Entra Device Code Authentication with Office Client and Automated User Agent
Suspicious AWS SSO Token Creation and Role Credential Retrieval (via cloudtrail)
Suspicious Device Code Authentication via Microsoft Authentication Broker
Suspicious Microsoft 365 OAuth Authorization to Visual Studio Code Client
Suspicious Microsoft Entra Device Code Authentication Flow
Suspicious Google Workspace OAuth Authorization for Chrome Web Store Scope via Token Audit
Suspicious Federated Identity Credential On-Behalf-Of Token Flow via Sign-In Logs
Malicious Azure AD Application Consent Granted with Mail Permissions
Pivot detection · T1528 · 9 related

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.