SOLVED
Home

User object not synchronized anymore

%3CLINGO-SUB%20id%3D%22lingo-sub-878127%22%20slang%3D%22en-US%22%3EUser%20object%20not%20synchronized%20anymore%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-878127%22%20slang%3D%22en-US%22%3E%3CP%3EHey%20guys%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ewe%20have%20one%20user%20object%20which%20seems%20not%20to%20sync%20anymore.%20Some%20days%20ago%20the%20sync%20was%20fine%20for%20the%20mailbox%20marketing%40contoso.com%3CBR%20%2F%3EThen%20we%20migrated%20the%20mailbox%20from%20OnPrem%20to%20EOL.%20Now%20we%20recognized%20that%20the%20default%20onmicrosoft%20email%20address%20changed%2C%20it%20is%20now%20marketing1234%40contoso.onmicrosoft.com%3CBR%20%2F%3EI%20wondered%20about%20it%20so%20I%20added%20marketing%40contoso.onmicrosoft.com%20and%20marketing1234%40contoso.onmicrosoft.com%20OnPrem.%20I%20hoped%20it%20would%20sync%20and%20afterwards%20I%20can%20remove%20the%20unwanted%20address.%3C%2FP%3E%3CP%3EThe%20AAD%20Connect%20shows%20no%20errors%2C%20the%20user%20object%20is%20still%20in%20the%20OU%20which%20is%20activated%20for%20sync.%3C%2FP%3E%3CP%3EWhat%20would%20be%20the%20smoothest%20way%20to%20fix%20this%3F%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EKind%20regards%2C%3C%2FP%3E%3CP%3Ewoelki%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-878127%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EExchange%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EHybrid%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EIdentity%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMigration%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOn%20Premise%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-878602%22%20slang%3D%22en-US%22%3ERe%3A%20User%20object%20not%20synchronized%20anymore%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-878602%22%20slang%3D%22en-US%22%3E%3CP%3EMost%20likely%20you%20have%20a%20duplicate%20object%2C%20which%20explains%20both%20the%20renaming%20of%20the%20alias%2C%20and%20the%20fact%20that%20the%20object%20doesn't%20seem%20to%20sync%20anymore.%20Read%20here%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Factive-directory%2Fhybrid%2Ftshoot-connect-objectsync%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Factive-directory%2Fhybrid%2Ftshoot-connect-objectsync%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Foffice365%2Ftroubleshoot%2Fadministration%2Fduplicate-attributes-prevent-dirsync%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Foffice365%2Ftroubleshoot%2Fadministration%2Fduplicate-attributes-prevent-dirsync%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-880592%22%20slang%3D%22en-US%22%3ERe%3A%20User%20object%20not%20synchronized%20anymore%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-880592%22%20slang%3D%22en-US%22%3EI%20didn't%20thought%20that%20you%20might%20be%20right%2C%20but%20you%20are.%20I%20always%20looked%20for%20OnPrem%2C%20but%20somebody%20created%20a%20distribution%20group%20in%20the%20cloud%20with%20the%20same%20proxyadress.%3CBR%20%2F%3E%3CBR%20%2F%3EUnfortunately%20a%20simple%20cleanup%20did%20not%20help.%20Even%20not%20with%20initial%20sync.%20Troubleshooting%20in%20AAD%20Connect%20shows%20no%20errors.%20Very%20odd.%3CBR%20%2F%3E%3CBR%20%2F%3EAny%20further%20ideas%3F%3CBR%20%2F%3E%3CBR%20%2F%3EKind%20regards%2C%3CBR%20%2F%3EChristian%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-880762%22%20slang%3D%22en-US%22%3ERe%3A%20User%20object%20not%20synchronized%20anymore%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-880762%22%20slang%3D%22en-US%22%3E%3CP%3EIf%20you%20have%20removed%20the%20duplicate%20object%2C%20the%20issue%20should%20be%20solved%20after%20the%20next%20sync.%20In%20case%20the%20original%20object's%20attributes%20were%20replaced%20via%20the%20%22resiliency%22%20feature%20as%20detailed%20in%20the%20article%20above%2C%20you%20might%20need%20to%20replace%20them%20back.%20Other%20than%20that%2C%20you%20can%20ignore%20any%20errors%20showing%20in%20the%20O365%20portal%20-%20it's%20known%20to%20have%20latency%20issues.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-880765%22%20slang%3D%22en-US%22%3ERe%3A%20User%20object%20not%20synchronized%20anymore%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-880765%22%20slang%3D%22en-US%22%3EI%20could%20recognize%2C%20that%20the%20issue%20did%20appeared%20for%20other%20accounts%20as%20well.%20The%20solution%20was%20to%20restart%20the%20AAD%20Connect%20and%20Exchange%20Hybrid%20server.%20Now%20attribute%20changes%20are%20successfully%20synced%20again.%3CBR%20%2F%3E%3CBR%20%2F%3EThanks%20anyway.%3CBR%20%2F%3E%3CBR%20%2F%3EKind%20regards%2C%3CBR%20%2F%3EChristian%3C%2FLINGO-BODY%3E
woelki
Contributor

Hey guys,

 

we have one user object which seems not to sync anymore. Some days ago the sync was fine for the mailbox marketing@contoso.com
Then we migrated the mailbox from OnPrem to EOL. Now we recognized that the default onmicrosoft email address changed, it is now marketing1234@contoso.onmicrosoft.com
I wondered about it so I added marketing@contoso.onmicrosoft.com and marketing1234@contoso.onmicrosoft.com OnPrem. I hoped it would sync and afterwards I can remove the unwanted address.

The AAD Connect shows no errors, the user object is still in the OU which is activated for sync.

What would be the smoothest way to fix this?


Kind regards,

woelki

4 Replies

Most likely you have a duplicate object, which explains both the renaming of the alias, and the fact that the object doesn't seem to sync anymore. Read here: https://docs.microsoft.com/en-us/azure/active-directory/hybrid/tshoot-connect-objectsync

 

https://docs.microsoft.com/en-us/office365/troubleshoot/administration/duplicate-attributes-prevent-...

I didn't thought that you might be right, but you are. I always looked for OnPrem, but somebody created a distribution group in the cloud with the same proxyadress.

Unfortunately a simple cleanup did not help. Even not with initial sync. Troubleshooting in AAD Connect shows no errors. Very odd.

Any further ideas?

Kind regards,
Christian

If you have removed the duplicate object, the issue should be solved after the next sync. In case the original object's attributes were replaced via the "resiliency" feature as detailed in the article above, you might need to replace them back. Other than that, you can ignore any errors showing in the O365 portal - it's known to have latency issues.

Solution
I could recognize, that the issue did appeared for other accounts as well. The solution was to restart the AAD Connect and Exchange Hybrid server. Now attribute changes are successfully synced again.

Thanks anyway.

Kind regards,
Christian