---
title: "How to Leverage Azure AD Connect Delta Sync For Faster Syncs"
description: "Keeping your on-premise AD domain and Azure AD perfectly synchronized is difficult but learn to use Azure AD Connect Delta Sync to make this even faster!"
canonical: "https://adamtheautomator.com/delta-sync/"
---

# How to Leverage Azure AD Connect Delta Sync For Faster Syncs

> Keeping your on-premise AD domain and Azure AD perfectly synchronized is difficult but learn to use Azure AD Connect Delta Sync to make this even faster!

Source: https://adamtheautomator.com/delta-sync/

---

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/)

![How to Leverage Azure AD Connect Delta Sync For Faster Syncs](https://adamtheautomator.com/wp-content/uploads/2022/08/How-to-Leverage-Azure-AD-Connect-Delta-Sync-For-Faster-Syncs.jpg)

# How to Leverage Azure AD Connect Delta Sync For Faster Syncs

[![](https://secure.gravatar.com/avatar/9a14f10ff1b1ec7d790d34f5b559e4d3de2d31b172e6ef266dfd8b479174d97b?s=192&d=mm&r=g)June Castillote](https://adamtheautomator.com/author/june/)16 August 20227 min. read

Categories: [IT Ops](/category/it-ops/)

Tags:[Microsoft Azure AD](/tag/microsoft-azure-ad/)

Table of Contents

*   [Prerequisites](#prerequisites)
*   [Inspecting the Current Delta Sync Schedule](#inspecting-the-current-delta-sync-schedule)
*   [Forcing a Delta Sync using the ADSync PowerShell](#forcing-a-delta-sync-using-the-adsync-powershell)
*   [Forcing a Delta Sync using the Synchronization Service Manager](#forcing-a-delta-sync-using-the-synchronization-service-manager)
*   [Customizing the Delta Sync Interval](#customizing-the-delta-sync-interval)
*   [Checking the Synchronization Status in Azure Active Directory](#checking-the-synchronization-status-in-azure-active-directory)
*   [Check the Azure AD Connect Sync Status in the Azure AD Portal](#check-the-azure-ad-connect-sync-status-in-the-azure-ad-portal)
*   [Check the Azure AD Connect Sync Status using MSOnline PowerShell](#check-the-azure-ad-connect-sync-status-using-msonline-powershell)
*   [Conclusion](#conclusion)

When you make changes to a user account in Active Directory (AD), do you wonder how long before the changes reflect in Azure Active Directory (AAD)? Or perhaps can you force the synchronization to happen faster? Yes, you can, with Delta Sync.

Azure AD Connect ensures that object synchronization happens at least every 30 minutes by default. But what if you’re working on a task that requires immediate synchronization of changes from your on-premises AD?

Continue reading, and this tutorial will show you how to leverage the Azure AD Connect delta sync to force an out-of-cycle synchronization.

## Prerequisites

This tutorial will be a hands-on demonstration. If you’d like to follow along, be sure you have the following:

*   An Azure AD tenant. Register a [free account](https://azure.microsoft.com/en-us/free//) if you don’t have one.
    
*   An on-premises Active Directory environment already configured with the latest Azure AD Connect. This tutorial uses a Windows Server 2019 Datacenter with Azure AD Connect 2.1.15.0.
    

Related:[How To Connect Azure AD to Office 365 with Azure AD Connect](https://adamtheautomator.com/connect-azure-ad-to-office-365/)

*   This tutorial assumes that you have installed the [MSOnline](https://docs.microsoft.com/en-us/powershell/azure/active-directory/install-msonlinev1?view=azureadps-1.0) PowerShell module on your Azure AD Connect server. The latest version as of this writing is 1.1.183.66.

> _Note: The MSOnline and ADSync modules are not compatible with PowerShell Core. For best results, use only Windows PowerShell 5.1._

## Inspecting the Current Delta Sync Schedule

By default, Azure AD Connect sets up a regular synchronization schedule during installation. The sync interval is every 30 minutes.

To inspect the current delta sync schedule, follow these steps:

1\. Open a PowerShell window on your computer.

Related:[Discover How to Run PowerShell as Administrator](https://adamtheautomator.com/powershell-run-as-administrator/)

2\. Import the ADSync module into your PowerShell session. This command doesn’t provide output, but you’ll verify the module in the following step.

```powershell
Import-Module ADSync
```

3\. Next, run the cmdlet below to display the current sync schedule.

```powershell
Get-ADSyncScheduler
```

You should see a similar output to the screenshot below. Based on the result, the current schedule is to run a Delta Sync with an interval of 30 minutes.

![Getting the current delta sync schedule](https://adamtheautomator.com/wp-content/uploads/2022/08/image.png)

Getting the current delta sync schedule

What do these properties mean?

*   `AllowedSyncCycleInterval` – Is the minimum interval allowed between (scheduled) synchronization cycles. This value means that even if you customize the sync schedule to a lower interval, the `AllowedSyncCycleInterval` value still prevails.
    
*   `CurrentlyEffectiveSyncCycleInterval` – The current sync cycle interval in effect. This value should be the same as the `CustomizedSyncCycleInterval` if the value is not higher than the `AllowedSyncCycleInterval`.
    
*   `CustomizedSyncCycleInterval` – The customized sync interval. This value is default blank or null, which automatically follows the `AllowedSyncCycleInterval`. If you set this value to lower than `AllowedSyncCycleInterval`, the sync schedule will not take effect. Only the same or higher interval is acceptable.
    
*   `NextSyncCyclePolicyType` – The next sync cycle’s policy type. The two valid values are `Delta` (sync changes since the last cycle) and `Initial` (sync everything).
    
*   `NextSyncCycleStartTimeInUTC` – Shows when’s the next scheduled sync.
    
*   `PurgeRunHistoryInterval` – The duration to keep the operations logs. You can view the logs in the _Synchronization Service Manager_. The default duration is seven days.
    
*   `SyncCycleEnabled - Indicates whether the scheduler is enabled.`
    
*   `MaintenanceEnabled` – Indicates whether the scheduler is maintenance enabled. During maintenance, the scheduler renews the certificates and purges the operations logs.
    
*   `StagingModeEnabled - Indicates whether the Azure AD Connect is in [staging mode](https://docs.microsoft.com/en-us/azure/active-directory/hybrid/how-to-connect-sync-staging-server).`
    
*   `SchedulerSuspended` – Determines if the scheduler is currently suspended from running. Only Azure AD Connect can set this status.
    
*   `SyncCycleInProgress` – Indicates whether the synchronization cycle is in progress.
    

## Forcing a Delta Sync using the ADSync PowerShell

When you install Azure AD Connect, the `ADSync` PowerShell Module comes with it. This module provides you with cmdlets when interacting with AD Connect in PowerShell. One of these cmdlets is the `Start-ADSyncSyncCycle`, which forces the delta sync on demand.

To run a delta sync immediately, run the below command in PowerShell. The `-PolicyType Delta` parameter tells the cmdlet to run a delta sync.

```powershell
Start-ADSyncSyncCycle -PolicyType Delta
```

If the Azure AD Connect application is open, synchronization cannot run, and you will get the error below.

![Getting an error as you’re unable to start the scheduler because Azure AD Connect is open](https://adamtheautomator.com/wp-content/uploads/2022/08/image-1.png)

Getting an error as you’re unable to start the scheduler because Azure AD Connect is open

What’s the solution? Run the below command to force-close the `AzureADConnect` process.

```powershell
Get-Process AzureADConnect | Stop-Process -Force -PassThru
```

The result should be similar to the screenshot below.

![Terminating the AzureADConnect process](https://adamtheautomator.com/wp-content/uploads/2022/08/image-2.png)

Terminating the AzureADConnect process

Another possible error is that the `Connector: <domain> is busy`, where `<domain>` is the domain name. This error means that another synchronization is already in progress. All you can do is wait for the current sync to finish.

![Getting an error as you’re unable to start the scheduler because the connector is busy.](https://adamtheautomator.com/wp-content/uploads/2022/08/image-3.png)

Getting an error as you’re unable to start the scheduler because the connector is busy.

Finally, if the delta sync execution is successful, you will only get a `Successful` result on the screen.

![Confirming successful delta sync](https://adamtheautomator.com/wp-content/uploads/2022/08/image-4.png)

Confirming successful delta sync

## Forcing a Delta Sync using the Synchronization Service Manager

Another way to force a deal sync is through the Synchronization Service Manager, a GUI application that came with the Azure AD Connect installation.

Forcing a delta sync in the Synchronization Service Manager requires six actions. These actions are what the scheduler executes within the sync cycle or by running the `Start-ADSyncSyncCycle` cmdlet.

*   Local Connector – Delta Import
*   AAD Connector – Delta Import
*   Local Connector – Delta Sync
*   AAD Connector – Delta Sync
*   AAD Connector – Export
*   Local Connector – Export

There are many steps, but each allows you to inspect the changes before executing the synchronization.

1\. Open the Active Directory Users and Computers console. Right click Start → Run → type dsa.msc → press Enter.

![Open the Active Directory Users and Computers console](https://adamtheautomator.com/wp-content/uploads/2022/08/image-5.png)

Open the Active Directory Users and Computers console

2\. Next, look for a user and change its display name. This example shows changing the display name for user _Josh Carson_ to _Josh Carson (Network Engineer)._

Once changed, click OK to save the change.

![Changing the user display name](https://adamtheautomator.com/wp-content/uploads/2022/08/image-6.png)

Changing the user display name

3\. Now, open the Synchronization Service Manager by clicking on Start → Azure AD Connect → Synchronization Service.

![Opening the Synchronization Service Manager](https://adamtheautomator.com/wp-content/uploads/2022/08/image-7.png)

Opening the Synchronization Service Manager

4\. Click the Connectors tab to see your AAD and Local connectors. When you do, click the local connector → Run → Delta Import → OK.

![Running the local connector delta import](https://adamtheautomator.com/wp-content/uploads/2022/08/image-8.png)

Running the local connector delta import

As you can see below, the sync manager picked up one update.

![Viewing the Delta import captures one object update](https://adamtheautomator.com/wp-content/uploads/2022/08/image-9.png)

Viewing the Delta import captures one object update

5\. Now, click the AAD connector → Run → Delta import → OK.

![Running the AAD connector delta import](https://adamtheautomator.com/wp-content/uploads/2022/08/image-10.png)

Running the AAD connector delta import

At the confirmation prompt, click Yes.

![Confirming AAD delta import](https://adamtheautomator.com/wp-content/uploads/2022/08/image-11.png)

Confirming AAD delta import

The AAD connector also picked up one update, as you can see below.

![Confirming the AAD Delta import captures one object update](https://adamtheautomator.com/wp-content/uploads/2022/08/image-12.png)

Confirming the AAD Delta import captures one object update

6\. Next, click the local connector → Run → Delta synchronization → OK to run the delta sync step on the local connector.

![Running the local connector delta sync](https://adamtheautomator.com/wp-content/uploads/2022/08/image-13.png)

Running the local connector delta sync

7\. Perform the delta sync step on the AAD Connector. Click the AAD connector → Run → Delta synchronization → OK.

![Running the AAD connector delta sync](https://adamtheautomator.com/wp-content/uploads/2022/08/image-14.png)

Running the AAD connector delta sync

8\. Now, run the Export step on the AAD connector. Click the AAD Connector → Run → Export → OK.

![Running the AAD connector export](https://adamtheautomator.com/wp-content/uploads/2022/08/image-15.png)

Running the AAD connector export

9\. Lastly, run the Export step on the local connector. Click the local connector → Run → Export → OK.

![Running the local connector export](https://adamtheautomator.com/wp-content/uploads/2022/08/image-16.png)

Running the local connector export

10\. Now, open your web browser and log in to the [Azure Active Directory admin center](https://aad.portal.azure.com/).

On the AAD admin center, click Users → All users. Look for the user account you modified and confirm that it now reflects the display name change.

![Verifying the delta sync change in Azure Active Directory.](https://adamtheautomator.com/wp-content/uploads/2022/08/image-17.png)

Verifying the delta sync change in Azure Active Directory.

## Customizing the Delta Sync Interval

You’re now aware of the current delta sync schedule and how to run the delta sync on-demand. Suppose, for some reason, you require the delta sync schedule to run at a custom interval. How would you do it?

The answer depends on whether you want the interval longer than 30 minutes. If so, then yes, you can increase the sync cycle interval. In contrast, you can set the interval below 30 minutes, but the scheduler will ignore it and honor the lowest interval possible of 30 minutes.

> _You may experiment with creating a scheduled task in the Windows Task scheduler that runs Start-ADSyncSyncCycle -PolicyType Delta with a shorter interval. But remember that Microsoft does not officially support any sync schedule outside the scheduler._

If you wish to increase the delta sync interval (31 minutes and above), run the `Set-ADSyncScheduler` command with the `-CustomizedSyncCycleInterval HH:mm:ss` parameter. This example changes the sync cycle interval to 45 (`00:45:00`) minutes.

```powershell
Set-ADSyncScheduler -CustomizedSyncCycleInterval 00:45:00
```

You’ll get a warning saying that the new schedule will not take effect until after the next scheduled delta sync happens. You can ignore this warning.

![Changing the delta sync interval to 45 minutes](https://adamtheautomator.com/wp-content/uploads/2022/08/image-18.png)

Changing the delta sync interval to 45 minutes

Confirm that your intended change in the schedule reflects in the scheduler.

![Confirming the new custom sync cycle interval](https://adamtheautomator.com/wp-content/uploads/2022/08/image-19.png)

Confirming the new custom sync cycle interval

## Checking the Synchronization Status in Azure Active Directory

So you’ve executed the delta sync. How do you verify that the sync status is healthy in Azure Active Directory? Here are two ways.

### Check the Azure AD Connect Sync Status in the Azure AD Portal

If you like a fancy GUI to check the Azure AD Connect sync status, turn to Azure AD Portal, as follows:

1\. Open your browser and log in to the [Azure Active Directory center](https://aad.portal.azure.com/).

2\. Click on Azure Active Directory → Azure AD Connect.

3\. Lastly, look for the Azure AD Connect sync section and confirm that the Sync Status is Enabled and the Last Sync was Less than 1 hour ago.

![Check the Azure AD Connect Sync Status in the Azure AD Portal](https://adamtheautomator.com/wp-content/uploads/2022/08/image-20.png)

Check the Azure AD Connect Sync Status in the Azure AD Portal

### Check the Azure AD Connect Sync Status using MSOnline PowerShell

If you’re more into working on a command-line environment to check the Azure AD Connect sync status, MSOnline PowerShell is up for the task:

1\. Open a PowerShell window and import the MSOnline module.

```powershell
Import-Module MSOnline
```

2\. Next, run the below command to get the tenant details, including the last sync time.

```powershell
# UTC
(Get-MsolCompanyInformation).LastDirSyncTime

# Local Time
(Get-MsolCompanyInformation).LastDirSyncTime.ToLocalTime()
```

![Get the last sync timestamp](https://adamtheautomator.com/wp-content/uploads/2022/08/image-21.png)

Get the last sync timestamp

3\. Run the below command to determine if the last sync time is within the scheduled cycle (which means recent). Compare the previous sync time with the current time.

```powershell
Get-Date
```

As you can see below, the current date and the last sync time are within 45 minutes, which is the delta sync cycle schedule.

![Comparing the last sync time with the current time](https://adamtheautomator.com/wp-content/uploads/2022/08/image-22.png)

Comparing the last sync time with the current time

4\. Now, run the code below as your starting point if you plan to automate the sync schedule and status monitoring.

This code calculates the elapsed time since the last sync and compares it you the CurrentlyEffectiveSyncCycleInterval value in the scheduler.

```powershell
$now = Get-Date
$syncCycleInterval = [int](Get-ADSyncScheduler).CurrentlyEffectiveSyncCycleInterval.TotalMinutes
$lastSync = (Get-MsolCompanyInformation).LastDirSyncTime.ToLocalTime()
$totalMinutesSinceLastSync = [int](New-TimeSpan -Start $lastSync -End $now).TotalMinutes

if ($totalMinutesSinceLastSync -lt $syncCycleInterval ) {
    "Sync is GOOD (within [$totalMinutesSinceLastSync] minutes of the [$syncCycleInterval] minute interval)"
} else {
    "Sync is BAD (last sync was [$totalMinutesSinceLastSync] minutes ago, which is beyond the [$syncCycleInterval] minute interval)"
}
```

Below is the sample result, but you can still improve this script by adding a notification system and scheduling it to run using the Task Scheduler.

Related:[PowerShell Scheduled Task : Amazing Way to Manage Tasks](https://adamtheautomator.com/powershell-scheduled-task/)

![Monitoring the delta sync status with a PowerShell script](https://adamtheautomator.com/wp-content/uploads/2022/08/image-23.png)

Monitoring the delta sync status with a PowerShell script

## Conclusion

Whenever you’re changing AD object properties, you can wait for the changes to reflect in Azure AD, or you trigger a delta sync immediately. Delta sync is helpful in troubleshooting, maintenance, or reconfiguration in Azure AD Connect.

When customizing the synchronization schedule, always consider that a delta sync must happen within seven days after the last sync cycle, whether the previous cycle was a delta sync or full sync.

Thank you for reading, and enjoy learning!

Share this article

[Share on X](https://twitter.com/intent/tweet?url=https%3A%2F%2Fadamtheautomator.com%2Fdelta-sync%2F&text=How%20to%20Leverage%20Azure%20AD%20Connect%20Delta%20Sync%20For%20Faster%20Syncs)[Share on Facebook](https://www.facebook.com/sharer/sharer.php?u=https%3A%2F%2Fadamtheautomator.com%2Fdelta-sync%2F)[Share on LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fadamtheautomator.com%2Fdelta-sync%2F)

## Related Posts

![](https://adamtheautomator.com/wp-content/uploads/publisher/2e05d9c85b2b8184bb24f8beaeb7f165/85751120c0fb4909afa44fc19e072a60152e0de73a44e1bba3c2dc4f2c71b424.webp)

### [SQL Server 2025 Upgrades: Avoid These Breaking Changes](/sql-server-upgrade-breaking-changes/)

Avoid SQL Server 2025 upgrade failures. Master the breaking changes in encryption, TDS, and replication before you plan your migration.

![](https://adamtheautomator.com/wp-content/uploads/2026/07/featured_image-4.png)

### [Migrate from EWS to Microsoft Graph API](/migrate-ews-microsoft-graph-api/)

Move EWS mailbox automation to Microsoft Graph with a practical inventory, permissions, PowerShell SDK, and cutover validation checklist.

![](https://adamtheautomator.com/wp-content/uploads/2026/06/featured_image-21.png)

### [Automate SOC 2 Compliance with PowerShell](/automate-soc-2-compliance-powershell/)

A comprehensive walkthrough on using PowerShell and Azure Policy as Code to automate evidence collection and enforce SOC 2 compliance controls across enterprise cloud environments.

## 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/)