Azure Audit Logs: User Elevated to User Access Administrator Across Azure Subscriptions

Flags Azure AuditLogs events where a user is assigned to User Access Administrator, enabling full subscription management.

FreeReviewedSigma · High · v7
Product
azure
Service
auditlogs
Author
Austin Songer @austinsonger (SigmaHQ), DRL 1.1
Published
2021-11-26
Updated
2026-10-03

ATT&CK techniques

Initial Access → Defense Evasion
  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 cases in Azure Audit Logs where an activity indicates a user elevated their access to the User Access Administrator role for their Azure resources. Because this permission level can grant broad management capabilities, unexpected elevation may allow an attacker to gain or maintain access to Azure subscriptions. Detection relies on the audit log fields Category and ActivityDisplayName indicating the specific RBAC elevation event.

Related detections9 linkedT1078 — drag to rearrange
Suspicious SonicWall NetExtender VPN Command-Line Authentication with Always-Trust (via process_creation)
Suspicious Self-Hosted GitHub Actions Runner Started As Root via Shell (via process_creation)
Suspicious Login Shell Assigned to Service Account games on Linux
Suspicious SSH Daemon Configuration Change Enabling Root Login
Suspicious NTLM Network Logon From Attacker Controlled Workstation Names (via security)
Suspicious dMSA Object Access with Migration AccessMask
Malicious ESX Admins Group Added to Privileged Directory Group
Malicious ESX Admins Group Creation via WinRM Host
Suspicious BrightMetricAgent Remote Tool Execution Associated With Volt Typhoon
Azure Audit Logs: User Elevated to User Access Administrator Across Azure Subscriptions
Pivot detection · T1078 · 9 related

Changelog

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