![](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(57.599999999999994, 73%, 15%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EKY%3C/text%3E%3C/svg%3E)
Microsoft Security | Microsoft Entra | Microsoft Entra ID
A cloud-based identity and access management service for securing user authentication and resource access
![](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(259.20000000000005, 50%, 35%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ED%3C/text%3E%3C/svg%3E)
When configuring remote tenant user synchronization, SSO (Single Sign-On) should generally function correctly as long as the necessary configurations are in place. However, issues can arise if the synchronization settings are not properly configured or if there are problems with the cross-tenant access policies. It is important to ensure that both the source and target tenants have the appropriate settings enabled for automatic user consent and inbound synchronization to avoid any SSO-related issues.
If you encounter specific problems with SSO after setting up remote tenant user synchronization, it would be advisable to check the provisioning logs and verify that all configurations are correctly applied according to the guidelines provided by Microsoft.
References: