Azure Connect duplicate attributes

Question

We currently have AZ Connect synchronising one-way; I am making preparations for two-way as we go hybrid in the lead up to cloud migration.

We have a handful of duplicate attribute errors outstanding - conflicting proxyaddresses. The problem is that the existing objects with conflicting address no longer have those proxyaddresses assigned in our AD. I cannot remove it from Azure AD directly, and making changes to the local accounts does not instigate an update that refreshes the proxy addresses.

I can't remove the addresses using Exchange online because we are not yet using exchange online and those objects don't exist. What's the best way forward in this scenario?

Answer 1

Hi @Russell Morris ,

Could following links help you to the right direction?

https://learn.microsoft.com/en-us/azure/active-directory/hybrid/how-to-connect-health-diagnose-sync-errors

https://learn.microsoft.com/en-us/answers/questions/92433/azure-ad-connect-sync-error-duplicate-attribute.html

Answer 2

Hi TKujala,

So the problem was a lack of understanding how proxyaddresses were created in Azure AD (https://learn.microsoft.com/en-us/troubleshoot/azure/active-directory/proxyaddresses-attribute-populate).

I thought that the old records were not updating after removing the conflicting address on-site, but Azure was creating a new SMTP address to match the user's UPN. By changing the old UPNs I was able to resolve the problem.

Thanks for your links, they set me down the right path.

Russell.