O365 Cross-Tenant Access Change
The following analytic identifies when cross-tenant access/synchronization policies are changed in an Azure tenant. Adversaries have been observed altering victim cross-tenant policies as a method of lateral movement…
Description
The following analytic identifies when cross-tenant access/synchronization policies are changed in an Azure tenant. Adversaries have been observed altering victim cross-tenant policies as a method of lateral movement or maintaining persistent access to compromised environments. These policies should be considered sensitive and monitored for changes and/or loose configuration.
Detection logic
Detection requirements
- Platform
- Identity ProviderWindows
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
- Business approved changes by known administrators.
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/T1484/002/ | 3 |
| cyberaffairs.com/news/emerging-attacker-exploit-microsoft-cross-tenant-synchronization/ | Only this detection cites it |
| thehackernews.com/2023/08/emerging-attacker-exploit-microsoft.html | Only this detection cites it |
| www.crowdstrike.com/blog/crowdstrike-defends-against-azure-cross-tenant-synchronization-attacks/ | Only this detection cites it |
From the source
- At source
- Open at source
- Upstream identifier
- 7c0fa490-12b0-4d0b-b9f5-e101d1e0e06f
- Tagged by the source as
- Azure Active Directory PersistenceO365 TenantcloudSplunk CloudSplunk EnterpriseSplunk Enterprise Securitythreat
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