Unexpected mappings in the Active Roles Synchronization Service with Azure objects using rules created by the Azure Back Sync configuration wizard (312981)

The Azure Back Sync configuration wizard creates a User to User mapping pair with two mapping rules:

Active Roles userPrincipalName = Azure userPrincipalName

OR

Active Roles displayName = Azure displayName

This can result in unexpected mappings and/or ambiguity errors due to the fact that displayName does not have a uniqueness constraint.

WORKAROUND

1. Perform an UnMap in the Active Roles Synchronization Service console
2. Delete the existing mapping pairs and enter a new mapping:

Active Roles objectGUID = Azure immutableID

STATUS

An enhancement request has been created to modify this existing functionality in Active Roles.

Product Management will evaluate the request and this feature may become available in a future release of the product.There are no guarantees that this specific enhancement request will be implemented in a future release. For more information regarding our Enhancement Request policy, refer to our Global Support Guide on the Support Portal at: https://support.oneidentity.com/essentials/support-guide/