Guess what? This is no different for the recently released version 1.1 of the Azure AD Connect (AAD Connect) tool, which by the way brings several significant changes and improvement with it as you can read in the blog post, I link to.
In previous blog posts here on MSExchange.org (more specifically here and here), I explain how you perform a forced synchronization with previous sync tools and tool versions. With AAD Sync and version 1.0 of the AAD Connect tool, you could also simply run the scheduled task manually to achieve your goal.
With AAD Connect 1.1, we no longer have a Windows scheduled task running every 3 hour. Now the tool has a built-in scheduler, which by default performs a delta sync every 30 minutes. You can change this interval schedule, however bear in mind that 30 minutes is the lowest interval supported.
Although a synchronization now runs every 30 minutes, there may be occasions, where you still want to force a sync. To do so, you launch Windows PowerShell on the respective server on which AAD Connect has been installed and type the following to import the AAD Connect PowerShell module:
You check the current settings for the new scheduler, you can use the new Get-ADSyncScheduler as shown below.
To force a delta sync, you the following PowerShell command:
Start-ADSyncSyncCycle -PolicyType Delta
If you want to force an initial (full) sync, use this command:
Start-ADSyncSyncCycle -PolicyType Initial