Quantcast
Channel: Azure Active Directory forum
Viewing all articles
Browse latest Browse all 16000

AD Connect sync errors generated consistently for objects no longer in scope

$
0
0
Hi,
 We've setup a custom mail routing scenario whereby we have contacts on premise setup with external addresses pointing to our O365 distribution groups. The external addresses are already in place on distribution groups within O365. Mail routing works fine.

We accidentally placed our contacts in an OU that's synced to O365, we've since removed the OU from AD Connect sync scope, but within Synchronization Service Manager we have 569 export errors to AAD. The errors occur because the email addresses on the AD contacts are already present within O365 distribution groups. These errors are also present in the Azure Portal under AD Connect Health.

Simply removing the OU out of the synchronisation scope did not stop the errors being generated at every synchronisation cycle. If I search the AAD connector space for export errors, I can see the contact errors on the attempted add operation as 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: [ProxyAddresses"

Given that the contacts are no longer in scope for OU sync, how can I stop these errors from being generated?

We're using AD Connect 1.2.70.0 on Windows 2012 R2.

Thanks

IT Support/Everything


Viewing all articles
Browse latest Browse all 16000

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>