Configuring User Mapping

User Mapping unifies different user identities belonging to the same data owner under their unique User Principal Name (UPN), which is provided by Azure or Windows Active Directory.

User Mapping requires synchronization with Azure or Windows Active Directory.

User Mapping requires access to the Identity Management Cache in order to map the users in the Active Directory to the people of interest available for selection in the audit. To successfully configure User Mapping, the following steps must be completed:

  • Integrate the application with Office 365. Register the SyncAD application with the Microsoft Identity Platform to populate the Identity Management Cache - the User Identity Cache in Azure - with Platform User Objects.

  • Create an Identity Management Cache (IMC) job. The IMC job will connect to Active Directory for OnPremise and Azure Active Directory for O365. When the IMC job is configured, objects are created in the IMC stored in LDAP. The objects have attributes pulled from the Active Directory. To learn more about the objects created in LDAP—see LDAP Object Details.

  • NOTE
    If IMC is disabled, SyncAB will automatically populate the Platform Users in sync with the User Cache. See step for details.
  • If there are users who still exist in a Legacy Email Archive but are no longer in the Active Directory, the Archive2Identity tool must be run—see Configuring Legacy Email Archives.

  • Perform the User Mapping. If you have connected only to data sources within the same Microsoft ecosystem, you can apply automatic User Mapping. If you have connected to additional data sources, you must perform manual User Mapping.