Cross-Tenant Synchronization is a Microsoft Entra feature that automates creating, updating, and deleting B2B identities across multiple tenants.
Simple definition
Cross-Tenant Synchronization is a Microsoft Entra feature that automates creating, updating, and deleting B2B identities across multiple tenants. It belongs to the Microsoft 365 / Entra / Intune vocabulary and is useful when reading architecture diagrams, product documentation, logs, or administration procedures.
What is it used for?
Its main purpose is to keep user populations consistent across tenants in an organization or partner setup without manual provisioning. The practical value depends on the surrounding architecture, security model, and operational requirements.
How does it work?
A synchronization configuration selects source users/groups and maps their attributes to B2B objects in the target tenant, with automated lifecycle handling.
Key points
- Scope: A Microsoft Entra feature that automates creating, updating, and deleting B2B identities across multiple tenants.
- Operational goal: Keep user populations consistent across tenants in an organization or partner setup without manual provisioning.
- Implementation: A synchronization configuration selects source users/groups and maps their attributes to B2B objects in the target tenant, with automated lifecycle handling.
Points to watch
Define scope and compliance obligations; overly broad synchronization can replicate unnecessary identities or personal data.
In short
Cross-Tenant Synchronization = a Microsoft Entra feature that automates creating, updating, and deleting B2B identities across multiple tenants. Use it when you need to keep user populations consistent across tenants in an organization or partner setup without manual provisioning.