Cross-tenant synchronisation streamlines the process of creating, updating, and deleting Microsoft Entra B2B collaboration users across different tenants. On the NHSmail platform, it can be used to facilitate seamless collaboration and access to resources or applications on an organisation’s own Azure tenant using their user’s centrally secured NHS.net identity.
Key Objectives of Cross-Tenant Synchronisation
- Seamless Collaboration: Smooth collaboration ensuring that users can work together seamlessly across different tenant boundaries without having multiple identities to access Microsoft and non-Microsoft applications securely.
- Automated Lifecycle Management: Automated lifecycle management (Joiners, Leavers and Movers) of synced identities based on the synced rules
How to request for Cross-tenant synchronisation with an external organisation?
The process to request the configuration for Cross-tenant synchronisation with an external organisation (domain) is administered via the Helpdesk Self-Service (HSS) route. NHSmail organisation’s Local Administrators can create a new HSS request to configure a new cross-tenant synchronisation by selecting the “configure a cross-tenant synchronisation” option.
Local Administrators from the requesting NHSmail organisation will need to meet the necessary prerequisite by ensuring that Teams Shared Channels has been configured with the external organisation before requesting for cross-tenant synchronisation. For more information, please refer to the Teams Shared Channels LA Guide article.
The Cross-tenant synchronisation support on the NHSmail platform is for unidirectional synchronisation to allow NHS.net identities to be synchronised from NHSmail tenant to external tenant. The Cross-tenant from the external tenant to the NHSmail tenant is not supported.
| Last Reviewed Date | 16/08/2024 |
