How to manually match objects in ODM AD, when standard matching criteria is not suitable? (4370330)

How to manually match objects in ODM AD, when standard matching criteria is not suitable?

There's a need to map source AD objects to target, but standard matching rules, like userPrincipalName, samAccountName or email will not work. Is there a way to map such accounts?

Unfortunately, there's no way currently to map specific AD objects using an import file, like CSV. Enhancement Request ODMAD-I-41 has been created for this purpose.

It's possible to map specific source accounts to target ones, if target accounts are pre-populated using an unused attribute, that is the same as another attribute in the source domain.
For example, using unused target extensionAttribute5:
1. Create a CSV file with source and target samAccountName attributes
2. Write a PowerShell script, which will open target object using its target samAccountName, then populate its extensionAttribute5 with the source samAccountName from CSV file.
This way, it's possible to create a new Read&Match workflow in ODM AD, that will use samAccountName<->extensionAttribute5 matching criteria.

Note: please make sure that matching attributes from source and target are having same format. It's not possible to match String to Integer.

ODM ADexpress matching is done only by using CSV file. ODM ADexpress does not use any matching criteria like in full ODMAD. For best results, please download an example CSV file and populate it with necessary parameters, leaving headers only. Note: when target environment is Entra tenant, please make sure to populate both, ObjectID and UPN in the CSV file.