Content reviewed: 12 October 2026
After an acquisition, the first identity request is usually immediate: employees need to find colleagues and open Teams or SharePoint resources in the other company, while mailboxes, devices and data are not ready to move. Entra cross-tenant synchronization can make that interim state manageable. It does not create one tenant and it is not a migration engine. It automates the lifecycle of B2B identities between a source and a target. Missing that boundary can produce a better people search while quietly creating a second directory with unclear attribute ownership, Exchange address-list defects and dangerous offboarding behavior.
Decide whether the outcome is collaboration or consolidation
Cross-tenant synchronization is designed for organizations that own multiple tenants and need automated creation, update and deletion of B2B collaboration objects. The person still authenticates in the home tenant and data stays where it is. Microsoft explicitly says the service does not migrate a mailbox, OneDrive or SharePoint and that the source tenant remains necessary for authentication. If the acquisition requires one directory, one mailbox and one device-management plane, synchronization is a coexistence mechanism within the migration program, not the end state.
What actually runs between source and target
Sync is a one-way push from the source. The source defines scope, mappings and transformations; the target permits inbound sync. Configure automatic redemption for the relationship as source outbound and target inbound. The opposite switches do not cover that direction. The documented start interval is 40 minutes; runtime depends on volume and the initial cycle can take longer. This is not a guaranteed completion time.
A multitenant organization adds Microsoft 365 context
A multitenant organization, or MTO, sits above tenant relationships and cross-tenant synchronization. For Teams it provisions external users with a Member user type rather than the familiar Guest type so Microsoft 365 can offer a more coherent cross-tenant experience. The Microsoft 365 admin center synchronizes the same selected users to every MTO tenant; different scopes per destination require Entra ID configuration. MTO can improve collaboration and people discovery, but it does not centrally manage Exchange, Intune or Conditional Access for every tenant.
| Need | Mechanism | What it does not solve |
|---|---|---|
| Application access in another owned tenant | Cross-tenant synchronization | Data and device migration |
| Improved Teams experience across owned tenants | Multitenant organization | A single global tenant |
| A shared channel without broad B2B membership | B2B direct connect | General application access |
| Governed partner access outside the group | Entitlement management | Internal consolidation |
| A definitive post-merger end state | Tenant-to-tenant migration | Long-term coexistence on its own |
User and group synchronization have different license floors
For same-cloud user sync, each synchronised user needs P1 in the home/source tenant. Sync itself requires no target licence, but services used there can have separate requirements. Group sync and supported cross-cloud scenarios require Entra ID Governance or Entra Suite in the source. MTO has its own rule: Microsoft specifies one P1 per employee across the MTO and at least one P1 in every tenant. A blanket claim that an MTO target never needs P1 is therefore incorrect.
Matching existing objects is the highest-risk pilot task
Entra matches an internal source account to an external target object through an internal alternativeSecurityIdentifier. It can bring an existing B2B object under management, but cannot merge two internal Member accounts that already exist in both tenants. Default mappings also do not necessarily change a historic Guest to Member unless userType is deliberately mapped. Before starting, create a matrix of home account, target object, mailbox, UPN, primary SMTP, object ID and intended result. Without that evidence, a duplicate may first become visible in a people picker or Teams rather than in the provisioning wizard.
Exchange attributes need a separate design
The subtle failures often live in Exchange. Cross-tenant synchronization creates a B2B user, not a mail contact, and it cannot generally write every Exchange attribute. proxyAddresses can be read-only in the target, targetAddress is not a normal mapping target and address-list visibility is not governed like an ordinary Entra property. showInAddressList can support people search, but it does not prove mail routing, free/busy or a coherent GAL. Test those outcomes separately; never infer the mail design from the presence of an Entra object.
Scope by target resource, not only by the org chart
Group sync supports static and dynamic security groups and Microsoft 365 groups as sources, but creates static security groups in the target. It does not create a corresponding Team or distribution group. Nested and role-assignable groups are unsupported; scope must be Sync only assigned users and groups. Cross-cloud group sync is unsupported. A pre-existing group created outside sync is not taken under management. Choose scope by the required resources and verify which members are in scope.
A target-only sign-in block can be overwritten
A block applied only to the target B2B object can persist until the source user changes. When that change is detected, sync can enable the target user again. For an incident, identify the authority for accountEnabled and test the outcome after a real source change. A green job or a manual target block is not that test.
Severing the sync relationship does not delete previously managed target users. Keep inbound sync enabled until controlled deprovisioning completes and check remaining objects. A 40-minute cadence is not a guarantee of immediate access removal.
The overview describes restoration when the source user returns to scope within 30 days of soft deletion. The configuration guide also warns about restoration after on-demand soft deletion and possible duplicate users. Do not treat these scenarios as interchangeable: identify how deletion occurred, record object IDs and pilot the specific restoration path.
MTO has separate operational limits
The current Microsoft 365 plan supports up to 100 MTO tenants; larger organisations need support involvement. That is not a limit on cross-tenant sync itself. A person can take up to seven days to appear in search after provisioning, rather than one sync cycle. Teams Rooms is not supported in this MTO scenario.
MTO can create Exchange Online Organization Relationships for calendar availability, but does not automatically unify mailboxes or every Exchange attribute. Teams shared channels still need B2B direct connect and Teams configuration. A B2B-synchronised external Member does not replace that identity model.
Deprovisioning changes access; it is not directory housekeeping
Removing assignments or falling out of scope normally soft-deletes the target user. However, the reference documents an exception: a user added through an assigned group, then blocked in the source and synchronised with accountEnabled=false, may not be soft-deleted when removed from that group. Blocking, removing access and deleting are different outcomes. Record the target object’s state and verify each offboarding step.
| Area | Test | Evidence |
|---|---|---|
| Identity | One correctly matched target object | Source and target object IDs; matching outcome in provisioning logs |
| Sign-in | No invitation or unexpected consent | Sign-in log in both tenants |
| Attributes | Name, UPN, manager and extensions | Provisioning log before and after |
| Microsoft 365 | Teams, SharePoint and people search | Role-based user tests |
| Messaging | GAL, routing and free/busy | A separate Exchange test pack |
| Leaver | Blocking and soft deletion in the intended order | Timestamped deprovisioning trail |
Hub-and-spoke and mesh topologies carry different operating costs
Every source-to-target direction is a separate configuration. A three-tenant mesh is therefore several trust relationships, mapping sets and log streams, not one service. Hub-and-spoke reduces the connection count but makes the hub critical to application access. Count configurations, owners, break-glass procedures and deprovisioning flows in each direction. External objects are not forwarded again, which prevents loops but also means an identity does not transit automatically through a middle tenant.
| Topology | Three tenants | Five tenants | What to check |
|---|---|---|---|
| Full bidirectional mesh | 3 × 2 = 6 | 5 × 4 = 20 | Each tenant pushes its own internal users to every destination. |
| Bidirectional hub and spokes | 2 × 2 = 4 | 2 × 4 = 8 | A spoke identity is not forwarded through the hub to another spoke. |
The model counts all stated directions, not licences or service prices. Fewer configurations do not establish access to every required application. A hub does not automatically provide a full mesh.
Both user and manager must be in scope for the manager attribute. The current overview does not support manager sync in US Government or cross-cloud scenarios. Removing a manager in the source without a replacement does not automatically clear manager in the target. Test this change as well as assigning a new manager.
A six-step rollout
- 01
Define identity home
Assign one authoritative tenant per person and prohibit parallel internal accounts
- 02
Inventory collisions
Locate historic guests, members, contacts, mailboxes and duplicate addresses
- 03
Design minimum scope
Select the pilot by target resources and risk rather than department alone
- 04
Configure bilateral trust
Verify inbound sync, automatic redemption, MFA trust and Conditional Access
- 05
Exercise the lifecycle
Test create, update, manager change, block, remove, restore and hard deletion
- 06
Expand with telemetry
Track provisioning errors, sign-ins, duplicates and experience in Teams, SharePoint and the directory
Measure three independent layers after launch
An operating dashboard should separate provisioning health, Microsoft 365 usability and the security outcome. Monitor scope size, success and error counts per cycle, age of the latest change, duplicates, unexpected re-enablement and soft deletions. From the employee view, test sign-in, people discovery, Teams entry and SharePoint access. Security validation must test actual authorization and Conditional Access in the target. A green provisioning job proves neither a secure design nor correct mail flow.
When cross-tenant synchronization is the wrong tool
For suppliers or partners outside one corporate group, Microsoft points toward entitlement management and standard B2B governance; cross-organization synchronization can create additional privacy, legal and consent responsibilities. It is also a poor shortcut around a migration plan or an attempt to manage a subsidiary’s devices from headquarters without an Intune design. It works best when tenant ownership, identity home and offboarding accountability are unambiguous.
Frequently asked questions
Is cross-tenant synchronization a migration tool?
No. Authentication remains in the home tenant and it does not move data, mailboxes or devices.
Do synchronized users need a target-tenant license?
User sync itself requires Entra ID P1 for each synchronized user in the source. Services consumed in the target can have separate requirements.
Does an existing Guest automatically become Member?
Not in every default configuration. userType must be mapped deliberately and validated in the pilot.
Does MTO solve the global address list and mail flow?
It can improve people search and Microsoft 365 experiences, but Exchange routing, free/busy and mail attributes still require their own design.
Does ending the relationship delete every target user?
No. Severing it does not remove the target objects. Run controlled deprovisioning and verify the target result.
Is blocking sign-in in the target sufficient?
Not as a permanent assumption. A source-user change can overwrite the target block. Identify the accountEnabled authority and test a source change.








