Microsoft Entra External IDCross Tenant Synchronization Overview
In brief
What Entra admins need to know
Review the documentation change to determine whether it affects tenant configuration, security posture, or rollout plans.
This editorial summary was generated by AI from the documentation changes. Verify important details in the full Microsoft Learn article.
Documentation change
Open on Microsoft Learn ↗The comparison below is an extract of the Microsoft Learn article showing only the changed content. Open the full article for complete context.
For example, if a group is synchronized from tenant A to tenant B and an administrator makes a change to the group in tenant B, that change persists in tenant B. The synchronization engine doesn't detect the change made to the group in the target tenant, so it doesn't override the change.
If a group is created outside cross-tenant synchronization, it isn't included in cross-tenant synchronization.
Synchronization performance depends on the total number of objects (users, groups) and references (such as group memberships and manager relationships) being processed by a sync job. As the overall volume of objects and references increases, the time required to evaluate and synchronize changes can also increase. In environments with high scale, this can result in longer synchronization cycles and increased latency for updates to be reflected in the target tenant. To optimize performance, scope synchronization to only the users, groups, and relationships that are necessary.
Structure
@@ -283,7 +283,9 @@ If a group exists in the target tenant (created outside cross-tenant synchroniza For example, if a group is synchronized from tenant A to tenant B and an administrator makes a change to the group in tenant B, that change persists in tenant B. The synchronization engine doesn't detect the change made to the group in the target tenant, so it doesn't override the change. -- If a group is created outside cross-tenant synchronization, it isn't included in cross-tenant synchronization. +- If a group is created outside cross-tenant synchronization, it isn't included in cross-tenant synchronization.++- Synchronization performance depends on the total number of objects (users, groups) and references (such as group memberships and manager relationships) being processed by a sync job. As the overall volume of objects and references increases, the time required to evaluate and synchronize changes can also increase. In environments with high scale, this can result in longer synchronization cycles and increased latency for updates to be reflected in the target tenant. To optimize performance, scope synchronization to only the users, groups, and relationships that are necessary. ### Structure