Microsoft Entra External ID

Cross Tenant Synchronization Overview

3 July 2026Updated+3 / −1 lines

In brief

Documentation change

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

diff --git a/docs/identity/multi-tenant-organizations/cross-tenant-synchronization-overview.md b/docs/identity/multi-tenant-organizations/cross-tenant-synchronization-overview.md
index 09aaf3af7f6..6640432bb24 100644
--- a/docs/identity/multi-tenant-organizations/cross-tenant-synchronization-overview.md
+++ b/docs/identity/multi-tenant-organizations/cross-tenant-synchronization-overview.md
@@ -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