Summary


A customer has sent in numerous Azure DirSync error emails like the ones below.



Nazeefah Nadeem

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: [Mail NNadeem13@stdamians.co.uk;]. Correct or remove the duplicate values in your local directory. Please refer to http://support.microsoft.com/kb/2647098 for more information on identifying objects with duplicate attribute values.

ppnXJA+Hg6ASEeaAwwANOrCXWQ==

Light Speed

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: [ProxyAddresses SMTP:lightspeed@stdamians.co.uk;Mail lightspeed@stdamians.co.uk;]. Correct or remove the duplicate values in your local directory. Please refer to http://support.microsoft.com/kb/2647098 for more information on identifying objects with duplicate attribute values.

JNBfKFr4LZYNEeaAwwANOrCXWQ==

Margaret Mackenzie

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: [Mail MMackenzie@stdamians.co.uk;]. Correct or remove the duplicate values in your local directory. Please refer to http://support.microsoft.com/kb/2647098 for more information on identifying objects with duplicate attribute values.

ip1YYkYVSYlyEeaAwwANOrAWbQ==

Hussam Haj-Mustafa

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: [Mail HHaj-Mustafa13@stdamians.co.uk;]. Correct or remove the duplicate values in your local directory. Please refer to http://support.microsoft.com/kb/2647098 for more information on identifying objects with duplicate attribute values.




Cause


If it were a couple of accounts then this would probably be an individual problem with the accounts. However a large number of them indicate a wide problem, which is what happened here. St Damians were receiving hundreds of these. This was caused by an outage which removed all their accounts from IAM Cloud, de provisioning wasn't on for them so they accounts were left in 365.


When we resynced them they were each given 2 Office 365 connectors:


2f7Ak7UWv49gESV1avaVdLoh7XKVXtwipg.png






Solution


You can individually fix these accounts by running a preview and committing it:


Before preview:


745cnr0nZHmepeH0UN_hQRMOOgoC9Ly5NA.png


After preview:


mn1-yAtjOohZjmHnMJ1sQLFiP4tjUNp97A.png


Or to bulk fix you can run a full import full sync on the customers Office 365 MA on HFIM:


Pl6F2k4RfNx5-RQFSVOUwADBfE_jIa7G2Q.png


Before full import full sync:


s67Ve74LZVTaP0l2PEqZT7Y1adFjb35eJw.png


After full import full sync:


uvuni5Cm7dW6pRdRyP7-a3nHSnJKtZ-U0A.png



Please note if the customer has a large number of users (over 10,000) check with senior members of the support team before running the sync as it can take some time so it may have to be done out of hours.