Azure AD Service Principal Privilege Escalation
This detection identifies when an Azure Service Principal elevates privileges by adding themself to a new app role assignment.
Detection logic
Detection requirements
- Platform
- IaaSIdentity ProviderOffice SuiteSaaS
The rule states no platform. This is derived from the ATT&CK technique it maps to.
- Log source category
- azure_active_directory_add_app_role_assignment_to_service_principal
Known benign triggers
- No false positives have been identified at this time.
MITRE ATT&CK mappings
0 exclusive techniques.This is coverage no other published rule has; it is not this rule's total technique count.
References
| Reference | Cited by |
|---|---|
| github.com/mvelazc0/BadZure | 2 |
| posts.specterops.io/microsoft-breach-what-happened-what-should-azure-admins-do-da2b7e674ebc | 2 |
| splunk.github.io/splunk-add-on-for-microsoft-cloud-services/Install/ | 3 |
| splunkbase.splunk.com/app/3110 | 3 |
| www.splunk.com/en_us/blog/security/hunting-m365-invaders-navigating-the-shadows-of-midnight-blizzard.html | 2 |
From the source
- At source
- Open at source
- Upstream identifier
- 29eb39d3-2bc8-49cc-99b3-35593191a588
- Tagged by the source as
- Azure Active Directory Privilege EscalationAzure TenantcloudSplunk CloudSplunk EnterpriseSplunk Enterprise Securityidentity
Licence
- Published under
- Apache License 2.0Read the licence
- Attribution
- Required
- Obtained under
- Apache-2.0Read the origin licence
Authorship
- Written by
- Published
- Aug 26, 2026
- Version
- 1