Dirsync Error Attribute value must be unique

Question

We migrated to Office365 about a year ago and now we are implementing Dirsync.  The UPN is the same on both counts (*** Email address is removed for privacy ***).  When I enabled DirSync I received 567 errors for attribute value must be unique.

The error information is below:

Unable to update this object because the following attributes associated with this object have values that may already be associated with another object in your local directory services: [UserPrincipalName *** Email address is removed for privacy ***;].  Correct or remove the duplicate values in your local directory.  Please refer to support.microsoft.com/.../2647098 for more information on identifying objects with duplicate attribute values.

Tracking Id: <alphaNumeric>

Any Ideas?

Thank you

Answer 1

Hey Henry,

Thank you for getting back to me.  Yes, the users already exist in both Local AD and Office 365.

I have tried to add the proxyaddresses but that has seemed to help.  I am showing two users in Office 365.  The first one is the users correct account and has an email address attached to it.  It also says that it's status is in cloud.  The 2nd account is *** Email address is removed for privacy *** and its status is synced with active directory.  These accounts do not have an email address or license associated with it.

Answer 2

Hi ProvidynAdmin,

When you performed the Soft match Henry mentioned above, did you cope the cloud user’s primary SMTP address and past into corresponding AD user’s E-mail Attribute? This is the key in soft match. Please send us the screenshots of AD user’s E-mail attribute and corresponding cloud user’s email address filed?

Meanwhile, have you tried the Hard Match method and what are the results?

Thanks for your time.

Best regards,

Ran

Answer 3

Hi ProvidynAdmin,

Based on your description, I want to confirm whether the user account already exists in both local AD and Office 365 since you mentioned "The UPN is the sam eon both counts". If yes, simply running DirSync will cause this error. It's an expected behavior.

For this situation, you will need to use Soft Match or Hard Match to match the on-premise user with the exsiting Cloud user. If you are already trying to match the user accounts, please notice that DirSync uses primary SMTP address but not the UPN to do the match. It can be configured with the proxyAddresses attribute in AD. Or you can use Hard Match, which uses ImmutableID to match users.

If anything is misunderstood, just let me know.

Thanks,

Henry