Home

Office 365 Admin Center: False Azure AD Connect Sync Error Summary

%3CLINGO-SUB%20id%3D%22lingo-sub-308943%22%20slang%3D%22en-US%22%3EOffice%20365%20Admin%20Center%3A%20False%20Azure%20AD%20Connect%20Sync%20Error%20Summary%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-308943%22%20slang%3D%22en-US%22%3E%3CP%3EOffice%20365%20Admin%20Center%3A%20False%20Azure%20AD%20Connect%20Sync%20Error%20Summary%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAAD%20Connect%20Status%20is%20showing%20%22DirSync%20errors%22%20%22We%20found%20DirSync%20object%20errors%201%2F4%2F19%208%3A54%20AM%22.%26nbsp%3B%3C%2FP%3E%3CP%3ENo%20errors%20are%20listed%20in%20the%20details%20screen%20linked%20to%20the%20error%20message.%3C%2FP%3E%3CP%3EThis%20message%20is%20not%20present%20in%20Office%20365%20Admin%20Center%20Preview%20or%20anywhere%20in%20the%20Azure%20AD%20Portal.%3C%2FP%3E%3CP%3ENo%20errors%20appear%20in%20the%20Azure%20AD%20Connect%20process%20details%20reviewed%20through%20the%20miis%20client%20on%20the%20active%20Azure%20AD%20Connect%20processing%20server.%3C%2FP%3E%3CP%3EI%20submitted%20a%20Feedback%20entry%2C%20but%20for%20all%20of%20our%20technicians%20who%20still%20use%20the%20new%20classic%26nbsp%3B%3CSPAN%3EOffice%20365%20Admin%20Center%2C%20this%20type%20of%20apparent%20false%20negative%20immediately%20sounds%20an%20alarm%20of%20something%20more%20problematic%20deeper%20within%20the%20system.%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EHas%20anyone%20seen%20a%20data%20stagnation%20communication%20that%20would%20explain%20this%20disconnect%20between%20the%20facts%20and%20the%20summary%3F%26nbsp%3B%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-308943%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAdmin%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EAzure%20AD%20Connect%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESummary%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-313143%22%20slang%3D%22en-US%22%3ERe%3A%20Office%20365%20Admin%20Center%3A%20False%20Azure%20AD%20Connect%20Sync%20Error%20Summary%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-313143%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSTRONG%3EUpdate%3A%20No%20change%20in%20symptoms.%20%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3EMicrosoft%20Case%20%23%2012660901%3C%2FP%3E%3CP%3EUpgraded%26nbsp%3Bfrom%20Azure%20AD%20Connect%20from%20%3CSPAN%3Ev%201.1.882.0%20to%20v%201.2.70.0%20per%20Microsoft%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EError%20message%20date%2Ftime%20just%20updates%20to%20the%20date%2Ftime%20of%20last%20successful%20sync.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Deleted
Not applicable

Office 365 Admin Center: False Azure AD Connect Sync Error Summary

 

AAD Connect Status is showing "DirSync errors" "We found DirSync object errors 1/4/19 8:54 AM". 

No errors are listed in the details screen linked to the error message.

This message is not present in Office 365 Admin Center Preview or anywhere in the Azure AD Portal.

No errors appear in the Azure AD Connect process details reviewed through the miis client on the active Azure AD Connect processing server.

I submitted a Feedback entry, but for all of our technicians who still use the new classic Office 365 Admin Center, this type of apparent false negative immediately sounds an alarm of something more problematic deeper within the system. 

Has anyone seen a data stagnation communication that would explain this disconnect between the facts and the summary?  

1 Reply
Highlighted

Update: No change in symptoms.

Microsoft Case # 12660901

Upgraded from Azure AD Connect from v 1.1.882.0 to v 1.2.70.0 per Microsoft

Error message date/time just updates to the date/time of last successful sync.