Forum Discussion
Having Soft Match Problem with Azure AD Connect
Do all users who exist in cloud fail to match from on-premises??
Have any users been sync before?
Have you checked so there is not any mail aliases that conflicting?
Checked the info in the synchronization manager or event viewer for more information?
Please read this also:
https://support.microsoft.com/en-us/help/2647098/duplicate-or-invalid-attributes-prevent-directory-synchronization-in-o
If for some reason it doesn’t work you could do a hard match instead on the immutableID but this must be populated
There are lot of documentation about this
Cheers adam
Hey Adam,
Thanks for the quick reply.
The STMP and UPN's are exactly the same. I'm only testing this feature with one account at the moment before I take it organization wide. I deleted all the aliases from the profile while troubleshooting. I checked the event viewer but did not see any events. I deleted my office365 account and ran a sync again and it created a new one and worked correctly, but I already have an organization with established office365 accounts and data and would hate to have to delete all of them just to have to transfer over the data.
I checked the article you sent, and it suggests that I try soft matching which I'm not able to get working. I will try hard matching though, I read you have to manually convert the GUID though so it seems troublesome for an entire organization to be synced.
Hi there
I'm facing same troubles as you did, I'm in migration preparation to sync local AD with AzureAD.
Could you tell me how you solved the issue ?
Brano
I realized that my conflicts in synchronization are caused by user objects in Deleted users. Once I hard delete then synchronization does not detected any other issue and works well since than.
BR, Brano
- Please try to sync another account instead! Either create one on each side or try an existing one Which lives on both sides
