O365 Privileged Role Assigned
The following analytic identifies the assignment of sensitive and privileged Azure Active Directory roles to an Azure AD user. Adversaries and red teams alike may assign these roles to a compromised account to…
Description
The following analytic identifies the assignment of sensitive and privileged Azure Active Directory roles to an Azure AD user. Adversaries and red teams alike may assign these roles to a compromised account to establish Persistence in an Azure AD environment. This detection leverages the O365 Universal Audit Log data source.
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
- office_365_universal_audit_log
Known benign triggers
- Administrators will legitimately assign the privileged roles users as part of administrative tasks. Microsoft Privileged Identity Management (PIM) may cause false positives / less accurate alerting.
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 |
|---|---|
| attack.mitre.org/techniques/T1098/003/ | 11 |
| learn.microsoft.com/en-us/azure/active-directory/roles/permissions-reference | 5 |
| learn.microsoft.com/en-us/microsoft-365/admin/add-users/about-exchange-online-admin-role?view=o365-worldwide | 3 |
From the source
- At source
- Open at source
- Upstream identifier
- db435700-4ddc-4c23-892e-49e7525d7d39
- Tagged by the source as
- Azure Active Directory PersistenceScattered Lapsus$ HuntersO365 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
- Oct 6, 2026
- Version
- 2