Azure Audit Logs: Admin-initiated App Role Assignments and Privileged Delegated Permissions

Alerts on Azure audit events where an admin grants app roles to a service principal, enabling privileged application access.

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

Persistence → Priv Esc
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Defense Evasion

  6. Cred Access

  7. Discovery

  8. Lateral Movement

  9. Collection

  10. C2

  11. Exfiltration

  12. Impact

What it detects

This rule flags administrator actions granting application permissions by adding an app role assignment to a service principal. Such changes can enable apps to access protected resources with elevated privileges, which attackers may abuse for persistence or privilege escalation. It relies on Azure audit log events containing the specific message text indicating the app role assignment operation.

Related detections9 linkedT1098.003 — drag to rearrange
Suspicious Service Principal Creation via Azure Audit Logs
Malicious IAM Group Creation for SES Abuse by JavaGhost (via cloudtrail)
Malicious Administrator Policy Attachment for Privilege Escalation in AWS
Suspicious Azure Contributor Role Assignment to Identity
Malicious GCP Service Account Backdoor via serviceAccountTokenCreator Grant
Suspicious GCP Service Account Impersonation via GenerateAccessToken
Malicious Azure Elevate Access to User Access Administrator
Suspicious Azure Policy Definition or Assignment Modification
Suspicious AWS IAM Role Creation With Cross-Account Trust Policy
Azure Audit Logs: Admin-initiated App Role Assignments and Privileged Delegated Permissions
Pivot detection · T1098.003 · 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.