1. Resources
  2. Detection rules
  3. Cross-Tenant Access Settings Changed

Cross-Tenant Access Settings Changed detection rules

An attacker loosens cross-tenant access settings (trusting another tenant's MFA and device claims, opening B2B access, or allowing a tenant to sync users in) to keep access through an external tenant they control.

Platform
Microsoft Entra ID
Severity
High
Log source
Microsoft Entra ID audit logs
Last updated
Rule formats
Sigmaand queries for: SplunkMicrosoft SentinelIBM QRadar
What an attacker needs
The Security Administrator or Global Administrator role in your tenant, and an external Microsoft Entra tenant that the attacker controls.
Impact
A persistent, trusted path from an attacker-controlled tenant into yours, with external accounts whose MFA is accepted without challenge.
Response
Remove the partner entry for the tenant nobody recognizes, then block sign-in for the accounts that came from it and revoke their sessions.
Mitigation
Protect cross-tenant access policy changes as protected actions, and trust MFA and device claims only for named, verified partner tenants.
Audit activities
Create a partner cross-tenant identity sync settingUpdate a partner cross-tenant identity sync settingCreate a MultiTenantOrgAdd MultiTenantOrg tenantTenant joining MultiTenantOrg tenant

How the attack works

Cross-tenant access settings define the trust between your Microsoft Entra tenant and other tenants: which external users and applications may come in (inbound), where your users may go (outbound), whether your Conditional Access policies accept MFA and compliant-device claims issued by the other tenant, and whether that tenant may provision users into yours through cross-tenant synchronization.

An attacker with Security Administrator or Global Administrator rights can add a partner entry for a tenant they control and configure it to trust that tenant's MFA claims, auto-redeem invitations and accept synchronized users. Accounts created or authenticated in the attacker's tenant then satisfy your MFA requirements without ever using your authentication methods, and they survive the cleanup of compromised internal accounts. Changes are logged in the CrossTenantAccessSettings and CrossTenantIdentitySyncSettings audit categories. Creating or joining a multitenant organization sets up the same trust in one step, because Microsoft generates the partner configuration and the user synchronization setting for every pair of its tenants and applies the organization's templates to them. A third rule reads those activities, which are written in the MultiTenantOrg and MultiTenantOrgTenant categories.

What an attacker needs

  • A compromised identity with Security Administrator or Global Administrator, or an application allowed to update the cross-tenant access policy.
  • An external Microsoft Entra tenant controlled by the attacker.

Impact

A persistent, trusted path from an attacker-controlled tenant into yours: external accounts whose MFA is accepted without challenge and, with inbound synchronization allowed, member-like users created by the attacker's tenant.

Detection rules

Cross-Tenant Access Partner or Default Setting Changed

Detects a change in the CrossTenantAccessSettings audit category: a partner tenant added, updated or deleted, or the default inbound and outbound settings updated or reset. The automatic migration of settings to the new storage model is excluded.

LevelMediumStatusExperimentalLog sourceMicrosoft Entra ID audit logs
title: Cross-Tenant Access Partner or Default Setting Changed
id: 71256d24-0f3c-4ee5-a75a-a7fd83bdb063
status: experimental
description: >-
  Detects a change in the CrossTenantAccessSettings audit category: a partner
  tenant added, updated or deleted, or the default inbound and outbound
  settings updated or reset. The automatic migration of settings to the new
  storage model is excluded.
references:
  - https://learn.microsoft.com/en-us/entra/external-id/cross-tenant-access-overview
  - https://learn.microsoft.com/en-us/entra/identity/monitoring-health/reference-audit-activities
author: Forestall
date: 2026-11-10
tags:
  - attack.privilege-escalation
  - attack.t1484.002
logsource:
  product: azure
  service: auditlogs
detection:
  selection:
    Category: CrossTenantAccessSettings
  filter_migration:
    OperationName: Migrated partner cross-tenant access settings to the scalable model
  filter_failed:
    Result: failure
  condition: selection and not 1 of filter_*
falsepositives:
  - Onboarding of partner organizations and sister tenants; confirm the partner tenant ID and a change record, then filter approved administrators in InitiatedBy if volume is high.
level: medium

False positives

  • Onboarding of partner organizations and sister tenants; confirm the partner tenant ID and a change record, then filter approved administrators in InitiatedBy if volume is high.

Cross-Tenant Identity Synchronization Setting Created or Updated

Detects a partner cross-tenant identity sync setting being created or updated. Allowing inbound synchronization lets the partner tenant create and update users in this tenant.

LevelHighStatusExperimentalLog sourceMicrosoft Entra ID audit logs
title: Cross-Tenant Identity Synchronization Setting Created or Updated
id: 1a55c97b-5310-43a9-86d8-d01b881affc2
status: experimental
description: >-
  Detects a partner cross-tenant identity sync setting being created or
  updated. Allowing inbound synchronization lets the partner tenant create
  and update users in this tenant.
references:
  - https://learn.microsoft.com/en-us/entra/identity/monitoring-health/reference-audit-activities
  - https://learn.microsoft.com/en-us/entra/external-id/cross-tenant-access-settings-b2b-collaboration
author: Forestall
date: 2026-11-10
tags:
  - attack.privilege-escalation
  - attack.t1484.002
logsource:
  product: azure
  service: auditlogs
detection:
  selection:
    OperationName:
      - Create a partner cross-tenant identity sync setting
      - Update a partner cross-tenant identity sync setting
  filter_failed:
    Result: failure
  condition: selection and not filter_failed
falsepositives:
  - Multitenant organizations configuring synchronization between their own tenants; confirm the partner tenant is one of yours.
level: high

False positives

  • Multitenant organizations configuring synchronization between their own tenants; confirm the partner tenant is one of yours.

Multitenant Organization Created, Tenant Added or Tenant Joined

Detects the audit activities written when a multitenant organization is created, when a tenant is added to it and when a tenant joins it. Microsoft states that cross-tenant access partner configurations and user synchronization settings are required between all tenant pairs of a multitenant organization and are generated automatically, in an unconfigured state, when a pending tenant joins. The optional templates of the multitenant organization then modify them. When a tenant is joined through the Microsoft 365 admin center, the templates are set to allow users to sync into the tenant and to redeem invitations automatically. A tenant can create or join only one multitenant organization, so the event is rare. The existing rules of this page read the categories CrossTenantAccessSettings and CrossTenantIdentitySyncSettings. These activities are in the categories MultiTenantOrg and MultiTenantOrgTenant.

LevelMediumStatusExperimentalLog sourceMicrosoft Entra ID audit logs
title: Multitenant Organization Created, Tenant Added or Tenant Joined
id: b658ce46-dcbf-4e31-aae4-1cab0cd57858
status: experimental
description: >-
  Detects the audit activities written when a multitenant organization is
  created, when a tenant is added to it and when a tenant joins it. Microsoft
  states that cross-tenant access partner configurations and user
  synchronization settings are required between all tenant pairs of a
  multitenant organization and are generated automatically, in an
  unconfigured state, when a pending tenant joins. The optional templates of
  the multitenant organization then modify them. When a tenant is joined
  through the Microsoft 365 admin center, the templates are set to allow
  users to sync into the tenant and to redeem invitations automatically. A
  tenant can create or join only one multitenant organization, so the event
  is rare. The existing rules of this page read the categories
  CrossTenantAccessSettings and CrossTenantIdentitySyncSettings. These
  activities are in the categories MultiTenantOrg and MultiTenantOrgTenant.
references:
  - https://learn.microsoft.com/en-us/entra/identity/monitoring-health/reference-audit-activities
  - https://learn.microsoft.com/en-us/entra/identity/multi-tenant-organizations/multi-tenant-organization-overview
  - https://learn.microsoft.com/en-us/graph/api/resources/multitenantorganization-overview
  - https://learn.microsoft.com/en-us/microsoft-365/enterprise/join-leave-multi-tenant-org
  - https://attack.mitre.org/techniques/T1484/002/
author: Forestall
date: 2026-11-18
tags:
  - attack.privilege-escalation
  - attack.t1484.002
logsource:
  product: azure
  service: auditlogs
detection:
  selection:
    OperationName:
      - Create a MultiTenantOrg
      - Add MultiTenantOrg tenant
      - Tenant joining MultiTenantOrg tenant
  filter_failed:
    Result: failure
  condition: selection and not filter_failed
falsepositives:
  - An organization that sets up its own multitenant organization. This happens once per tenant and is planned, so confirm the tenant IDs with the project that owns it.
level: medium

False positives

  • An organization that sets up its own multitenant organization. This happens once per tenant and is planned, so confirm the tenant IDs with the project that owns it.

Triage

  • Identify the partner tenant ID in TargetResources and confirm it belongs to a known partner or to your own organization.
  • Compare old and new values for inbound trust (MFA, compliant and hybrid-joined device claims), automatic redemption, B2B collaboration scope and the inbound sync setting.
  • Confirm the actor (InitiatedBy) and a change record; review sign-ins and newly created users from the partner tenant after the change.
  • If unauthorized, remove the partner configuration, delete users provisioned from the tenant and investigate the actor.

Response

Once the attack is confirmed:

  1. Remove the partner entry for the tenant nobody recognizes, or restore its previous values for inbound trust, automatic redemption, B2B collaboration and inbound synchronization. Reset the default settings if they were changed.
  2. Block sign-in for the accounts that came from that tenant and revoke their sessions. Delete the users it provisioned through synchronization and the guests invited from it, and remove their group memberships and role assignments.
  3. Revoke the sessions and reset the credentials of the identity that changed the settings, and remove its Security Administrator or Global Administrator role.
  4. Review the sign-ins and the audit log for what accounts from the external tenant did while the trust was in place, and undo their changes.
  5. Compare the remaining partner entries and the default settings with your list of known partners.

Mitigation

  • Protect cross-tenant access policy changes as protected actions that require phishing-resistant MFA.
  • Keep default inbound trust settings off; trust MFA and device claims only for named, verified partner tenants.
  • Allow inbound cross-tenant synchronization only for tenants that belong to your organization, and review partner entries regularly.

Frequently asked questions

Why is trusting the MFA claims of another tenant a risk?

With inbound trust, your Conditional Access policies accept MFA and compliant-device claims issued by the other tenant. If the attacker controls that tenant, their accounts satisfy your MFA requirements without ever using your authentication methods.

Does cleaning up the compromised internal accounts end this access?

No. The accounts the attacker uses live in the external tenant, or were created in yours by inbound synchronization, so they survive the cleanup of compromised internal accounts. The access ends when the partner configuration is removed and the users that came from that tenant are deleted.

Why is the synchronization rule rated higher than the partner settings rule?

Allowing inbound cross-tenant synchronization lets the partner tenant create and update users in your tenant. That is expected only between tenants of the same organization. A partner entry or a default setting changes more often, for example when a partner organization is onboarded.

References

We respect your privacy

We use cookies to keep this site secure and working properly. With your permission, we also use optional cookies to understand usage and improve the experience. Cookie Policy

You can change your choice at any time.