Synchronization Service lets you create flexible rules for generating the distinguished names (DNs) of objects being created. These rules allow you to ensure that created objects are named in full compliance with the naming conventions existing in your organization.
You can schedule the execution of data synchronization operations and automatically perform them on a regular basis to satisfy your company’s policy and save time and effort.
To access external data systems Synchronization Service employs special connectors. A connector enables Synchronization Service to read and synchronize the identity data contained in a particular data system. Out of the box, Synchronization Service includes connectors that allow you to connect to the following data systems:
In any hybrid environment, on-premises Active Directory objects are synchronized to Azure AD using some means such as Azure AD Connect. When Active Roles is deployed in such a hybrid environment, the existing users and groups' information, such as Azure objectID, must be synchronized back from Azure AD to on-premises AD to continue using the functionality. To synchronize existing AD users and groups from Azure AD to Active Roles we must use the back-synchronization operation.
Back Synchronization is performed by leveraging the existing functionality of Active Roles Synchronization Service. Synchronization workflows are configured to identify the Azure AD unique users or groups and map them to the on-premises AD users or groups. After the back-synchronization operation is completed, Active Roles displays the configured Azure attributes for the synchronized objects.
The Azure Backsync Configuration feature allows you to configure the backsync operation in Azure with on-premises Active Directory objects through the Synchronization Service Web interface. The required connections, mappings, and sync workflow steps are created automatically.
When you configure the back-synchronization, the Azure App registration is done automatically with the default app ActiveRoles_AutocreatedAzureBackSyncApp_V2.
- In case of an application not found error, please try the configure back- synchronization operation again after some time, since the Azure App synchron- ization may take some time.
If you use the existing back-synchronization configuration settings, then the existing default app ActiveRoles_AutocreatedAzureBackSyncApp is used to run the back-synchronization workflow. However, it is recommended to use the default app ActiveRoles_AutocreatedAzureBackSyncApp_V2 since it requires reduced administrator privileges. To use the latest Azure App, configure the back-synchronization again. For information to configure the back-synchronization, see Step 3: Configuring Azure BackSync.
For the back-synchronization to work as expected, the user in ARS must have write permissions for edsvaAzureOffice365Enabled, edsaAzureContactObjectId, edsvaAzureObjectID, and edsvaAzureAssociatedTenantId. The user must also have a local administrator privileges where the ARS synchronization service is running.