Upgrading Previous Version of Azure AD Connect

In this post, we are upgrading an existing Azure AD Connect installation from version 1.0.9131.0 to (published 16 Feb 2016).

NOTE: The existing scheduled task (created with versions prior to AD Connect 1.1) will be removed and replaced with an integrated scheduling tool that will be managed through PowerShell. Also, the default sync schedule will change from every 3 hours to every 30 minutes.



First, let’s download the latest version here; as of 16 Feb 2016.



After downloading, we will upgrade our existing installation by double clicking on the downloaded AzureADConnect.msi file.



The setup will detect an existing installation and we will review the information given in the wizard so we understand what is going to occur before proceeding. Click Upgrade to proceed.





Enter Office 365 credentials to connect to Azure AD.



Enter on premise credentials to connect to Active Directory. Personally, I recommend creating an on premise service account specifically for this application. It wouldn’t hurt to create a service account in Office 365 as well for this.



For our scenario, I chose not to enable “Start the synchronization…” and complete the upgrade.





Upon completion, we are notified that the synchronization is disabled (per my previous selection) and it must be enabled before syncing will start.



From Programs and Features, we see Microsoft Azure AD Connect installed.



Additionally, from Task Scheduler, we see there is no longer a scheduled task for Active Directory synchronization to Office 365.



Let’s know take a look at our synchronization schedule with this command from an elevated PowerShell console … “Get-ADSyncScheduler”

We will see that if “Start the synchronization…” was disabled during the upgrade process, the SyncCycleEnabled parameter for the scheduler is set to False. If this is the case, automatic synchronizations will not occur on the predefined, default 30 minute interval.



To manually sync Active Directory to Office 365, we will use this command from PowerShell … “Start-ADSyncSyncCycle -PolicyType Delta”


NOTE: The results of a manual “delta” sync will synchronize recent changes.


After manually starting a synchronization, we can monitor the progress in the Azure AD Synchronization Service Manager.



To enable the scheduler to run every 30 minutes (default), we use this command from PowerShell … “Set-ADSyncScheduler -SyncCycleEnabled $True”



After enabling the built-in sync scheduler, we can run Get-ADSyncScheduler again to confirm the value for SyncCycleEnabled is set to True.



One last thing to note is that after SyncCycleEnabled is set to true and the first scheduled synchronization completes, the NextSyncCyclePolicyStartType parameter value of Initial is automatically changed to Delta going forward.


NOTE: The results of the “initial” sync will perform a full synchronization of on premise AD objects to Office 365. In the case where a filter has been configured, only those objects will be synchronized from AD to O365.


After the initial sync, a delta sync will be performed until changed by the administrator.



Good luck and have fun!



Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s