As you probably say in my previous blog post, Microsoft recently had a big update to Azure AD Connect.
NOTE: Since then, they have released 220.127.116.11 here
As of that revision, they have moved the Scheduler function into the sync engine from scheduled tasks. So that begs the question, what if I need to force a sync due to testing or other reasons?
Well, let’s go find out.
First let’s open up PowerShell and check what modules are installed
Now let’s run a get-command to see what functions I can perform with that module. Looks like there are quite a few!
Looks like there’s a cmdlet for starting a sync cycle, let’s try it out
Let’s see if anything happened
Looks like our sync worked!