Azure audit logs: Delegated highly privileged permissions granted for all users

Alerts on Azure audit log events where delegated permissions are granted to all users.

FreeReviewedSigma · High · v5
Product
azure
Service
auditlogs
Author
Bailey Bercik '@baileybercik', Mark Morowczynski '@markmorow' (SigmaHQ), DRL 1.1
Published
2022-07-28
Updated
2026-07-31

ATT&CK techniques

Cred Access
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule flags events where an application is granted a delegated permission grant for all users with highly privileged scope. Such grants can enable broad access under the app’s identity, increasing the impact of credential theft or malicious OAuth consent. It relies on Azure audit log entries with the message indicating a delegated permission grant.

Related detections9 linkedT1528 — drag to rearrange
Suspicious Microsoft Entra Device Code Authentication Flow
Suspicious Google Workspace OAuth Authorization for Chrome Web Store Scope via Token Audit
Suspicious OAuth Application Consent Grant via Azure Audit Logs
Suspicious OAuth Application Consent Granted High Privilege Mail Scopes (via m365)
Suspicious Token Request Using Microsoft Authentication Broker Client to Obtain Primary Refresh Token (via azure)
Suspicious Salesforce Connected App OAuth Authorization from VPN Egress
Suspicious M365 Device Code Authentication Flow via m365
Possible Illicit Consent Grant to OAuth Application via Azure AD
Suspicious Device Code Authentication via Microsoft Authentication Broker
Azure audit logs: Delegated highly privileged permissions granted for all users
Pivot detection · T1528 · 9 related

Changelog

v5
  1. v5
    Candidate ingested via manual entry.2026-07-31
  2. v4
    Candidate ingested via manual entry.2026-07-31
  3. v3
    Candidate ingested via manual entry.2026-07-31
  4. v2
    Candidate ingested via manual entry.2026-07-31
  5. 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.