The NHSmail team are pleased to announce the release of this feature to Local Organisations on the hybrid platform.
The following update is relevant to both ‘hybrid tracks:
- Hybrid Join – Devices Hybrid Joining to NHS.net Azure AD
- Cloud+SSO – AAD-Joined devices with User Identity enhancements
The synchronization engine pre-stages devices, which are provided by the Local organization, into Azure AD using the NHSmail IAAS services. Additionally, the sync engine prepares custom attributes for users and devices, making them ready for synchronization with NHS.net Azure AD.
Currently, the Sync Engine is restricted to searching a specific OU, set by local organizations, for devices and users. This update will enable Local Administrators (LAs) to conduct searches across multiple OU locations, with the added capability to recursively explore each sub-OU under multiple OUs selected by an LA.
This change will also add the capability to mark a hybrid organisation from being “Active” or “Inactive”. This will stop the hybrid join process for an organisation individually, so that the hybrid join operation isn’t stopped for all organisations onboarded.
Key Changes for Local Admins
Local Admins will be able to give Accenture / Avanade multiple OU location paths to expand the hybrid sync. After sending the OU paths, LAs can arrange the sub-OUs as required.
Before going ahead with OU configuration, local organisations must define the OUs needed and notify the EMS Hybrid Run team (Via ServiceNow) so that the required Sync Engine configuration can be applied. Organisations may further change / add to the OU configuration via a service request.
For more information about this feature, please refer to the Operations Guide.
| Last Reviewed Date | 29/02/2024 |
