---
title: "Master Azure AD Connect: Sync Scheduling and Forcing"
description: "Use Azure Active Directory Connect to schedule or force sync between on-prem AD and Azure AD."
canonical: "https://adamtheautomator.com/azure-ad-connect/"
---

# Master Azure AD Connect: Sync Scheduling and Forcing

> Use Azure Active Directory Connect to schedule or force sync between on-prem AD and Azure AD.

Source: https://adamtheautomator.com/azure-ad-connect/

---

ATA Learning

Tap to hide

[

ATA Learning

](/)

*   [Home](/)
*   [Tutorials](/tutorials/)
*   [Instructors](/author/)
*   [Advertising](/advertising/)
*   [Recommended Resources](/resources/)
*   [About Adam](/about-adam/)

Search for:  

*   [](https://twitter.com/adbertram)
*   [](https://github.com/Adam-the-Automator)
*   [](https://www.linkedin.com/company/adam-the-automator-llc)
*   [](/feed/)

![Master Azure AD Connect: Sync Scheduling and Forcing](https://adamtheautomator.com/wp-content/uploads/2019/08/How-to-Force-Azure-AD-Connect-to-Sync-Walkthrough.jpg)

# Master Azure AD Connect: Sync Scheduling and Forcing

[![](https://secure.gravatar.com/avatar/87bec6692789c9e784a6c804c8730a8abc91f68609fc222eeb1068fb8d51acf8?s=192&d=mm&r=g)Jeff Christman](https://adamtheautomator.com/author/jeff/)23 August 20195 min. read

Categories: [Cloud](/category/cloud/)

Tags:[Active Directory](/tag/active-directory/)[Azure Active Directory](/tag/azure-active-directory/)[PowerShell](/tag/powershell/)

Table of Contents

*   [Install Azure AD Connect](#install-azure-ad-connect)
*   [Downloading from the Azure Portal](#downloading-from-the-azure-portal)
*   [Sync Tools](#sync-tools)
*   [Setting up the ADSync PowerShell Module](#setting-up-the-adsync-powershell-module)
*   [Default Azure AD Sync Schedule](#default-azure-ad-sync-schedule)
*   [Forcing an Azure AD Connect Sync](#forcing-an-azure-ad-connect-sync)
*   [Forcing a Sync with the Synchronization Service Manager](#forcing-a-sync-with-the-synchronization-service-manager)
*   [Getting Sync Status with PowerShell](#getting-sync-status-with-powershell)
*   [Forcing an Sync with PowerShell](#forcing-an-sync-with-powershell)
*   [Stopping a Sync](#stopping-a-sync)
*   [Summary](#summary)

Integrating your on-premises [Active Directory](https://adamtheautomator.com/tag/active-directory/) Domain Services (AD) (and syncing) with Azure AD is done using the Synchronization Service Manager GUI or via PowerShell.

There are two ways to use Azure AD on-prem – pass through authentication (sends the authentication request directly to Azure AD) or directory synchronization that syncs password hashes between on-prem AD and Azure AD. In this blog post, we’re going to cover how to get the Azure Active Directory Connect software set up to sync password hashes.

> Remove Exchange on-premises without compromising ease of management. [Use EasyEntra](https://easyentra.com/easyentra-ad-manager-freemium-edition/?utm_source=adam&utm_medium=paid&utm_campaign=easyentra&utm_content=freemiumarticle) instead of AD Users & Computers – Completely Free!

We’ll cover how to get a recurring sync running and also how to use Azure AD Connect to force a password hash synchronization.

In a nutshell, to force Azure AD to sync with PowerShell requires the following steps:

1.  Install Azure Active Directory Connect
2.  Import the ADSync [PowerShell module](https://adamtheautomator.com/powershell-modules/ "PowerShell module")
3.  Run the `Start-AdSyncSchedule` cmdlet with reads a domain controller’s password hashes and syncs with Azure AD.

If you’re more into learning via video, be sure to check out this informative TechSnips video.

## Install Azure AD Connect

To sync on-prem Active Directory to an Azure AD tenant, you’ll first need need to download and install the Azure AD connect software. To do that, you’ve got two options. You can either download it from the Azure Portal or by going directly to the [software package](https://www.microsoft.com/en-us/download/details.aspx?id=47594).

### Downloading from the Azure Portal

If you’ve chosen not to download the package from the Microsoft site, you’ll need to get the package from the Azure Portal.

Search for “Azure Active Directory” in the portal. In the _Azure Active Directory_ section, click on _Azure AD Connect_. Here you will find a _Sync Status_ section with a link to _Download Azure AD Connect_.

![Azure Portal - Azure AD Connect](/wp-content/uploads/2019/08/azure-ad-connect.png "image_tooltip")

Azure Portal – Azure AD Connect

## Sync Tools

When you install Azure AD Connect, it will install two primary tools you can use to schedule a sync or force a sync.

*   The ADSync PowerShell module
*   The Synchronization Service Manager

Using these two tools, you can setup a recurring (scheduled) sync to routinely perform an Azure AD sync. Or, you can use either to force a sync ad-hoc. Both tools perform the same behavior. The only difference is one is via the command-line (PowerShell) and one is a GUI application.

## Setting up the ADSync PowerShell Module

When you install Azure AD Connect, it will install a PowerShell module called _ADSync_. This module contains that allow you to manage the sync process using PowerShell.

> _Note that in this article, I am using Windows PowerShell 5.1. Your mileage may vary if you’re using an older version._

As with all [PowerShell](https://adamtheautomator.com/tag/powershell/) modules, importing the module is straight forward. However, the module is _not_ located in a known Windows PowerShell modules folder. The installation installs the PowerShell module in the _C:\\Program Files\\Microsoft Azure AD Connect Sync\\Bin_ folder.

To import the module, open a PowerShell console and enter the following:

```powershell
PS51> Import-Module –Name "C:\Program Files\Microsoft Azure AD Sync\Bin\ADSync" -Verbose
```

To verify that the module has imported, use `Get-Module`. You should see the _ADSync_ module listed.

![ADSync PowerShell Module](/wp-content/uploads/2019/08/az-connect-powershell.png "image_tooltip")

ADSync PowerShell Module

## Default Azure AD Sync Schedule

By default, Azure AD Connect creates a scheduled task that runs a delta (syncing only differing objects) sync every 30 minutes. You can find the schedule by opening up Task Scheduler. You should notice a scheduled task under _Microsoft_ –> _Windows_ called _Azure AD Sync Scheduler_.

![Azure AD Sync Scheduler scheduled task](/wp-content/uploads/2019/08/stop-azure-ad-sync-scheduler.png)

Azure AD Sync Scheduler scheduled task

You can change this schedule, but, bear in mind that 30 minutes is the lowest interval supported.  The goal is to set the synchronization interval so that it happens often enough to pick up changes. If the synchronization is too short, you run the risk of saturating your network.

The scheduler handles two tasks:

*   **Synchronization cycle** – The process to import, sync, and export changes.
*   **Maintenance tasks** –  Renews keys and certificates for password resets and the [Device Registration Service (DRS)](https://docs.microsoft.com/en-us/azure/active-directory/devices/device-management-azure-portal). It also purges old entries in the [operations log](https://docs.microsoft.com/en-us/azure/active-directory/hybrid/tshoot-connect-object-not-syncing).

The scheduler itself is always running but it can be configured to only run one or none of these tasks.

## Forcing an Azure AD Connect Sync

There may be times where you would need to force synchronization of your objects. For example, if you need to have your own synchronization cycle process, you can disable this task in the scheduler but still run the maintenance task.

To use Azure Active Directory Connect to force a password sync and other information, you can either use the Synchronization Service Manager or PowerShell.

### Forcing a Sync with the Synchronization Service Manager

On a server with Azure AD Connect installed, navigate to the Start menu and select _AD Connect_, then _Synchronization Service_.

At first glance it looks overwhelming, but you are only concerned with the _Connectors_ tab and the right hand selection pane. Looking at the right hand pane, you can see options to stop (_Stop_) and start (_Run_) the sync.

![Synchronization Service Manager](/wp-content/uploads/2019/08/sync-service-manager.png)

Synchronization Service Manager

> _Note that when a synchronization cycle is running, you cannot make configuration changes. Stopping the current cycle is not harmful and pending changes are processed with the next run._

### Getting Sync Status with PowerShell

Before you force a sync, it is a good idea to get the status of the current sync cycle. If you force sync during a currently running sync, you could be setting yourself up for some issues later on.

To see the current settings, open up a PowerShell console on the server Azure Active Directory Connect is installed on and run `Get-ADSyncScheduler`. You’ll see a few properties each providing useful information.

![Get-AdSyncScheduler](/wp-content/uploads/2019/08/get-adsyncscheduler.png)

`Get-AdSyncScheduler`

There is quite a bit of information to parse through. Let us go through line by line:

*   **`AllowedSyncCycleInterval`** – This is the shortest time between synchronization. By default it is set at 30 minutes, the shortest time allowed.
*   **`CurrentlyEffectiveSyncCycleInterval` –** The schedule currently in effect. It has the same value as `CustomizedSyncInterval` (if set) if it is not more frequent than `AllowedSyncInterval`. If you use a build before 1.1.281 and you change `CustomizedSyncCycleInterval`, this change takes effect after the next synchronization cycle. From build 1.1.281 the change takes effect immediately.
*   **`CustomizedSyncCycleInterval` –** This is set if you want to run the scheduler to run at a frequency other than the default 30 minutes.
*   **`NextSyncCyclePolicyType` –** This parameter defines the next run what the next run should process.  If the next run is full synchronization, it will display initially.
*   **`NextSyncCycleStartTimeInUTC` –** This is the time the scheduler starts the next sync cycle.
*   **`PurgeRunHistoryInterval` –** Set how long the operation logs are kept.  The default is to keep the logs for 7 days.
*   **`SyncCycleEnabled` –** Indicates if the scheduler is running the import, sync, and export processes as part of its operation.
*   **`MaintenanceEnabled` –** Maintenance enabled updates the certificates/keys and purges the operations log.
*   **`StagingModeEnabled`** – If enabled, it suppresses the exports from running.  synchronization.
*   **`SchedulerSuspended`** – Set to temporarily block the scheduler from running.

### Forcing an Sync with PowerShell

> _Find leaked & unsafe passwords in your Active Directory by checking against [the NCSC Password list](https://specopssoft.com/product/specops-password-auditor/?utm_source=ATA&utm_medium=referral&utm_campaign=ATA%20promo%202021&utm_content=SPA%20in-article%20link)._

You have a couple of options when forcing a synchronization. You can either force a full sync or a delta sync. A full sync checks all objects across AD. A delta sync only checks and syncs changes since the last run.

To start a full sync, you can use the `Start-AdSyncSyncCycle` cmdlet. Use the `PolicyType` parameter to choose either `Full` or `Delta` depending on the sync you’d like to initiate. Either method will force an AD sync for Office 365, user identity accounts and all other attributes.

> With EasyEntra, first-level support teams can focus on what instead of where! [Manage AD, Entra ID, and Exchange Online](https://easyentra.com/?utm_source=adam&utm_medium=paid&utm_campaign=easyentra&utm_content=standardarticle) from a consolidated, intuitive console.

```powershell
PS51> Start-ADSyncSyncCycle -PolicyType Full
PS51> Start-ADSyncSyncCycle -PolicyType Delta
```

### Stopping a Sync

If you’d like to stop a sync in process, you can also use the `Stop-ADSyncSyncCycle` cmdlet.

```powershell
PS51> Stop-ADSyncSyncCycle
```

## Summary

Whether you choose to use the GUI or PowerShell, you should now know various ways to use the Azure Active Directory Connect tool to schedule or force a sync with your on-prem Active Directory environment with Azure AD.

Share this article

[Share on X](https://twitter.com/intent/tweet?url=https%3A%2F%2Fadamtheautomator.com%2Fazure-ad-connect%2F&text=Master%20Azure%20AD%20Connect%3A%20Sync%20Scheduling%20and%20Forcing)[Share on Facebook](https://www.facebook.com/sharer/sharer.php?u=https%3A%2F%2Fadamtheautomator.com%2Fazure-ad-connect%2F)[Share on LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fadamtheautomator.com%2Fazure-ad-connect%2F)

## Related Posts

![](https://adamtheautomator.com/wp-content/uploads/2026/08/featured_image-3.webp)

### [Build an Azure Home Lab for Certs Without Overspending](/azure-home-lab-certification-practice/)

Build a nested Azure Hyper-V home lab with budget alerts, a domain controller, and Azure Arc mapped to AZ-900, AZ-104, and AZ-305 exams.

![](https://adamtheautomator.com/wp-content/uploads/2026/04/featured_image-20.webp)

### [How to Secure Azure Service Accounts with Managed Identities](/secure-azure-managed-identities/)

Learn how to replace secret-based Azure service accounts with managed identities, grant least-privilege Azure RBAC access, validate token-based authentication,

![](https://adamtheautomator.com/wp-content/uploads/2026/05/featured_image-3.webp)

### [Survive the Azure AD B2C Sunset with Entra External ID](/azure-ad-b2c-entra-migration/)

Learn how to migrate Azure AD B2C to Microsoft Entra External ID—covering JIT credential migration, custom policy translation, HSC mode decisions, and phased cutover strategies.

## Categories

*   [IT Ops](/category/it-ops/)
*   [Cloud](/category/cloud/)
*   [DevOps](/category/devops/)
*   [Home Ops](/category/home-ops/)
*   [Information Security](/category/infosec/)
*   [Software Development](/category/software-development/)

## Site

*   [Home](/)
*   [Tutorials](/tutorials/)
*   [Instructors](/author/)
*   [Advertising](/advertising/)
*   [Recommended Resources](/resources/)
*   [About Adam](/about-adam/)

Copyright 2026© ATA Learning | [Privacy Policy](/privacy/)
