Ad connect - duplicate smtp proxy addresses sync issue

%3CLINGO-SUB%20id%3D%22lingo-sub-819489%22%20slang%3D%22en-US%22%3EAd%20connect%20-%20duplicate%20smtp%20proxy%20addresses%20sync%20issue%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-819489%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20have%20an%20hybrid%20Exchange%20setup%20at%20the%20moment.%3CBR%20%2F%3EA%20mailbox%20was%20mistakenly%20given%20a%20wrong%20alias%20already%20attached%20to%20another%20mailbox.%3C%2FP%3E%3CP%3EThus%2C%20we%20had%20a%20syncronization%20error%20displayed%20on%20the%20admin%20center%20saying%20%3A%22We%20detected%20a%20duplicate%20Proxy%20address%20conflict%20on%20the%20value%20.%20All%20attribute%20values%20need%20to%20be%20unique%20across%20objects.%20To%20resolve%20this%20conflict%2C%20first%20determine%20which%20object%20should%20be%20using%20the%20conflicting%20value.%20Then%2C%20update%20or%20remove%20the%20conflicting%20value%20from%20the%20other%20object(s).%20This%20error%20was%20detected%20on%20.%22%3C%2FP%3E%3CP%3EWhen%20we%20cliked%20on%20the%20error%20details%20we%20could%20see%20the%20two%20mailboxes%20(%20the%20correct%20one%20and%20the%20wrong%20one)%20displaying%20the%20duplicated%20alias.%3CBR%20%2F%3ESo%20we%20removed%20the%20alias%20from%20the%20wrong%20mailbox%20on%20the%20exchange%20Online%20but%20the%20error%20was%20still%20showing%20up%20because%20the%20wrong%20alias%20was%20still%20attached%20to%20the%20mailbox%20on%20the%20%22local%20Exchange%20Console%22.%3CBR%20%2F%3ESo%20we%20removed%20the%20alias%20on%20the%20%22local%20Exchange%20Console%22.%3CBR%20%2F%3ENow%20the%20we%20have%20one%20remaining%20error%20refering%20only%20with%20the%20correct%20mailbox.%20The%20wrong%20mailbox%20is%20not%20showing%20up%20anymore%20on%20AD%20sync%20error%20details%20.%3CBR%20%2F%3EI've%20checked%20all%20the%20AD%20objects%20either%20on%20Ad%20or%20Exchange%20or%20O365%20and%20everything%20should%20be%20all%20good%20but%20still%20we%20have%20this%20error.%3CBR%20%2F%3EIs%20this%20an%20expected%20behavior%20or%20do%20I%20have%20to%20do%20something%20or%20wait%20before%20the%20error%20disappear%20%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-819489%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EOffice%20365%20Administration%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-819985%22%20slang%3D%22en-US%22%3ERe%3A%20Ad%20connect%20-%20duplicate%20smtp%20proxy%20addresses%20sync%20issue%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-819985%22%20slang%3D%22en-US%22%3E%3CP%3EShould%20I%20consider%20this%20topic%20as%20an%20answer%20to%20my%20question%20%3A%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fanswers.microsoft.com%2Fen-us%2Fmsoffice%2Fforum%2Fmsoffice_o365admin-mso_other-mso_o365b%2Fhow-to-clear-dirsync-error-report%2F97b43be7-5155-4a75-b69e-9782efdd161b%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fanswers.microsoft.com%2Fen-us%2Fmsoffice%2Fforum%2Fmsoffice_o365admin-mso_other-mso_o365b%2Fhow-to-clear-dirsync-error-report%2F97b43be7-5155-4a75-b69e-9782efdd161b%3C%2FA%3E%3C%2FP%3E%3CP%3EI%20hope%20not%20...%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-820021%22%20slang%3D%22en-US%22%3ERe%3A%20Ad%20connect%20-%20duplicate%20smtp%20proxy%20addresses%20sync%20issue%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-820021%22%20slang%3D%22en-US%22%3EI've%20had%20duplicates%20before%2C%20but%20they%20usually%20will%20just%20clear%20themselves%20as%20long%20as%20you%20removed%20the%20duplicate%20on%20the%20on-prem%20side%20of%20the%20fence.%20But%20it's%20usually%20on%20the%20next%20sync.%20You%20might%20try%20preforming%20a%20start-adsyncsynccycle%20-policytype%20initial%20to%20do%20a%20full%20sync%2C%20that%20might%20clear%20it%20up%20instead%20of%20relying%20on%20the%20delta.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-820512%22%20slang%3D%22en-US%22%3ERe%3A%20Ad%20connect%20-%20duplicate%20smtp%20proxy%20addresses%20sync%20issue%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-820512%22%20slang%3D%22en-US%22%3E%3CP%3EWhere%20are%20you%20seeing%20the%20error%20currently%3F%20If%20it's%20only%20in%20the%20O365%20Admin%20Center%2C%20you%20can%20ignore%20it%20-%20it's%20known%20to%20show%20outdated%20info.%20If%20you%20are%20seeing%20it%20in%20the%20MIIS%20Client%20or%20in%20the%20email%20notifications%20you%20are%20receiving%20for%20sync%2C%20then%20you%20have%20to%20double-check%20the%20attributes.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

We have an hybrid Exchange setup at the moment.
A mailbox was mistakenly given a wrong alias already attached to another mailbox.

Thus, we had a syncronization error displayed on the admin center saying :"We detected a duplicate Proxy address conflict on the value . All attribute values need to be unique across objects. To resolve this conflict, first determine which object should be using the conflicting value. Then, update or remove the conflicting value from the other object(s). This error was detected on ."

When we cliked on the error details we could see the two mailboxes ( the correct one and the wrong one) displaying the duplicated alias.
So we removed the alias from the wrong mailbox on the exchange Online but the error was still showing up because the wrong alias was still attached to the mailbox on the "local Exchange Console".
So we removed the alias on the "local Exchange Console".
Now the we have one remaining error refering only with the correct mailbox. The wrong mailbox is not showing up anymore on AD sync error details .
I've checked all the AD objects either on Ad or Exchange or O365 and everything should be all good but still we have this error.
Is this an expected behavior or do I have to do something or wait before the error disappear ?

3 Replies

Should I consider this topic as an answer to my question :
https://answers.microsoft.com/en-us/msoffice/forum/msoffice_o365admin-mso_other-mso_o365b/how-to-cle...

I hope not ...

I've had duplicates before, but they usually will just clear themselves as long as you removed the duplicate on the on-prem side of the fence. But it's usually on the next sync. You might try preforming a start-adsyncsynccycle -policytype initial to do a full sync, that might clear it up instead of relying on the delta.

Where are you seeing the error currently? If it's only in the O365 Admin Center, you can ignore it - it's known to show outdated info. If you are seeing it in the MIIS Client or in the email notifications you are receiving for sync, then you have to double-check the attributes.