Forum Discussion
Evaluating Azure Cross-Tenant Synchronization: Benefits and Concerns
Please try the below steps.
1. Device Compliance and CAPs - Users from a child tenant must meet the primary tenant's CAPs. If devices are not Intune-enrolled, access might be denied unless trust settings are configured to accept compliance claims from the child tenant.
2. Guest User Access - B2B guest access is unaffected, but cross-tenant access settings need to align with policies to avoid unintended access.
3. SharePoint/OneDrive Sharing - Existing sharing settings remain intact, but ensure external domains are included in collaboration settings to avoid invite issues.
4. Granular Control - You can control which users and attributes sync, ensuring only necessary data is shared.
5. Special Characters - Sync issues may occur with special characters in user attributes. Test with sample accounts and check Microsoft’s known issues for updates.
Reference URL:
https://learn.microsoft.com/en-us/entra/external-id/cross-tenant-access-settings-b2b-collaboration
https://learn.microsoft.com/en-us/entra/identity/multi-tenant-organizations/cross-tenant-synchronization-configure/
https://learn.microsoft.com/en-us/entra/external-id/authentication-conditional-access/
https://learn.microsoft.com/en-us/entra/external-id/cross-tenant-access-overview
Shared channels appear to work as expected, but how about direct chat post MTO? User A in tenant A can find User B in tenant B inside Teams, User B has the correct synced details etc.
However, User B must switch tenants to reply to the chat message, is this expected ?
