This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(92.8, 93%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJ%3C/text%3E%3C/svg%3E)
Hello.
A question is regarding Cross-Tenant Synchronization functionality.
Currently, there is an interest in using Microsoft's tenant-to-tenant synchronization feature to receive user information from an external tenant (Tenant B) within Tenant A.
The one-way synchronization setup for Tenant B has been completed, and the following configuration has been made:
Tenant-to-Tenant Synchronization > Configuration > Provisioning > Mapping Settings: userType has been set to Guest.
Is it possible to control the synchronization mapping setting in Tenant A so that the userType for Tenant B cannot be changed from Guest to Member?
Additionally, if Tenant B attempts to change the userType to Member during synchronization, can Tenant A refuse or filter that user?
The goal is to ensure that Tenant A only receives users from Tenant B with the userType set as Guest, not Member.
Is it possible for an administrator in Tenant A to control or filter the synchronization mapping configuration of Tenant B?
Recommendations received include:
However, is there a way to prevent this proactively rather than dealing with it afterward?
Thank you.
No, mapping configuration is done entirely on the "receiving" side. You can only prevent which users/groups can be synchronized from the "home" tenant.