SOLVED

DirSync Status's Last Directory Sync

%3CLINGO-SUB%20id%3D%22lingo-sub-56934%22%20slang%3D%22en-US%22%3EDirSync%20Status's%20Last%20Directory%20Sync%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-56934%22%20slang%3D%22en-US%22%3E%3CP%3EHello%2C%3C%2FP%3E%3CP%3EI'm%20using%20Azure%20AD%20Connect%20to%20sync%20my%20local%20Active%20Directory%20with%20Office%20365.%20For%20the%20past%20few%20days%20I've%20started%20to%20receive%20the%20following%20message%20i.e.%20the%20directory%20is%20no%20longer%20syncing.%20As%20a%20test%20I%20added%20new%20objects%20i.e.%20users%20in%20my%20local%20on-premises%20active%20directory%2C%20ran%20the%20ADSync%20PS%20manually%20and%20they%20are%20not%20showing%20up%20in%20my%20Office%20365%20users.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20290px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F12405iE460F1CAE79788C7%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22Capture.JPG%22%20title%3D%22Capture.JPG%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20did%20run%20the%20'%3CSPAN%3EGet-ADSyncScheduler%3C%2FSPAN%3E'%20and%20confirmed%20the%20Sync%20Cycle%20is%20enabled.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20421px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F12408i06473AC1CDE11432%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22Capture.JPG%22%20title%3D%22Capture.JPG%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20also%20ran%20the%20'%3CSPAN%3EStart-ADSyncSyncCycle%20-PolicyType%20Initial%3C%2FSPAN%3E'%20but%20that%20hasn't%20helped.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFinally%2C%20I%20downloaded%20and%20ran%20the%20IdFix%26nbsp%3B-%20Directory%20Error%20Remediation%20tool%26nbsp%3Band%20ran%20it%2C%20however%2C%20it%20did%20not%20yield%20any%20errors.%20Hence%2C%20i'm%20running%20out%20of%20ideas%20to%20fix%20this%20issue%20and%20welcome%20any%20thoughts%2C%20ideas%20to%20resolve%20this%20issue.%3C%2FP%3E%3CP%3EThanks%20in%20advance!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-56934%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAdmin%20Center%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-56956%22%20slang%3D%22en-US%22%3ERe%3A%20DirSync%20Status's%20Last%20Directory%20Sync%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-56956%22%20slang%3D%22en-US%22%3E%3CP%3EAwww%20shucks...how%20could%26nbsp%3BI%20forget%20the%20cardinal%20rule%20of%20IT%20trouble%20shooting...When%20in%20doubt%2C%20reboot!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20Michelle!!%20That%20seems%20to%20have%20fixed%20the%20problem.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20313px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F12412iFF8A05F11694BB05%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22Capture.JPG%22%20title%3D%22Capture.JPG%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-56947%22%20slang%3D%22en-US%22%3ERe%3A%20DirSync%20Status's%20Last%20Directory%20Sync%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-56947%22%20slang%3D%22en-US%22%3E%3CP%3EHave%20you%20tried%20rebooting%20the%20Azure%20server%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-56942%22%20slang%3D%22en-US%22%3ERe%3A%20DirSync%20Status's%20Last%20Directory%20Sync%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-56942%22%20slang%3D%22en-US%22%3EI%20would%20say%20your%20next%20step%20is%20communication.%20Firewall%2C%20certificates%20and%20the%20like.%20You%20could%20even%20wireshark%20the%20link%20for%20errors.%3CBR%20%2F%3E%3CBR%20%2F%3EI%20am%20not%20an%20expert%20on%20this%20but%20I%20think%20communication%20is%20next.%3C%2FLINGO-BODY%3E
Highlighted
MVP

Hello,

I'm using Azure AD Connect to sync my local Active Directory with Office 365. For the past few days I've started to receive the following message i.e. the directory is no longer syncing. As a test I added new objects i.e. users in my local on-premises active directory, ran the ADSync PS manually and they are not showing up in my Office 365 users.

 

Capture.JPG

 

I did run the 'Get-ADSyncScheduler' and confirmed the Sync Cycle is enabled.

 

Capture.JPG

 

I also ran the 'Start-ADSyncSyncCycle -PolicyType Initial' but that hasn't helped.

 

Finally, I downloaded and ran the IdFix - Directory Error Remediation tool and ran it, however, it did not yield any errors. Hence, i'm running out of ideas to fix this issue and welcome any thoughts, ideas to resolve this issue.

Thanks in advance!

3 Replies
Highlighted
I would say your next step is communication. Firewall, certificates and the like. You could even wireshark the link for errors.

I am not an expert on this but I think communication is next.
Highlighted
Best Response confirmed by Daniel Christian (MVP)
Solution

Have you tried rebooting the Azure server?

Highlighted

Awww shucks...how could I forget the cardinal rule of IT trouble shooting...When in doubt, reboot!

 

Thanks Michelle!! That seems to have fixed the problem.

 

Capture.JPG