ANAVEM
Languagefr
Fix Azure AD Connect Sync Service Not Running – Windows Server 2016/2019/2022 2026
Fix GuideADSync Service StoppedAzure AD Connect

Fix Azure AD Connect Sync Service Not Running – Windows Server 2016/2019/2022 2026

Azure AD Connect sync service fails to start automatically, preventing directory synchronization between on-premises Active Directory and Azure AD. Fix by starting the ADSync service manually and configuring proper startup settings.

Evan MaelEvan Mael
March 27, 2026 12 min
ADSync Service StoppedAzure AD Connect 5 methods 12 min
Instant Solution

Open Services console, locate Microsoft Azure AD Sync service, right-click and select Start. Verify startup type is set to Automatic to prevent future occurrences.

Understanding Azure AD Connect Sync Service Issues

Azure AD Connect serves as the critical bridge between on-premises Active Directory and Azure Active Directory, enabling seamless identity synchronization across hybrid environments. The Microsoft Azure AD Sync service (ADSync) is the core component responsible for this synchronization process, running continuously to ensure user accounts, groups, and password hashes remain synchronized between your local domain and the cloud.

When the ADSync service fails to start or stops unexpectedly, organizations face immediate disruption to their hybrid identity infrastructure. Users may experience authentication issues, new accounts won't synchronize to Azure AD, and password changes in on-premises AD won't replicate to the cloud. This service failure typically manifests when launching the Azure AD Connect configuration wizard, which displays the error "Sync Service not running" and prevents any synchronization management tasks.

The issue commonly occurs after system reboots, Windows updates, or configuration changes that affect service startup behavior. While the service is configured to start automatically by default, various factors including permission changes, dependency failures, or corrupted configurations can prevent proper initialization. Understanding the root cause and implementing the appropriate fix ensures reliable directory synchronization and maintains the integrity of your hybrid identity environment.

Diagnostic

Symptoms

  • Azure AD Connect wizard displays "Sync Service not running" error
  • Cannot proceed with synchronization configuration
  • Error message: "Cannot proceed because the sync service is not running. Start the ADSync service and restart the AADConnect Wizard to continue"
  • No directory synchronization occurring between on-premises AD and Azure AD
  • Email notifications about missed synchronization cycles in the last 24 hours
  • Azure AD Connect Health shows service as offline
Analysis

Root Causes

  • Microsoft Azure AD Sync service failed to start automatically after system reboot
  • Service startup type incorrectly configured as Manual or Disabled
  • Insufficient permissions for the ADSync service account
  • Corrupted service configuration or registry entries
  • Windows Update or system changes affecting service dependencies
  • Antivirus software blocking the ADSync service executable
  • Database connectivity issues preventing service startup
Resolution Methods

Solutions

01

Start Azure AD Sync Service Manually

This is the quickest method to resolve the immediate issue and restore synchronization.

  1. Press Windows + R to open the Run dialog
  2. Type services.msc and press Enter
  3. In the Services console, scroll down and locate Microsoft Azure AD Sync
  4. Check the service status - it should show as Stopped
  5. Right-click on Microsoft Azure AD Sync and select Properties
  6. Verify the Startup type is set to Automatic. If not, change it to Automatic
  7. Click Apply, then click Start to start the service
  8. Wait for the service status to change to Running
  9. Click OK to close the Properties dialog
Pro tip: You can also start the service using PowerShell with the command Start-Service ADSync

Verification: Open Azure AD Connect wizard and confirm the "Sync Service not running" error no longer appears. Check the service status shows as Running.

02

Configure Service Recovery Options

Configure automatic recovery to prevent future service failures from causing extended downtime.

  1. Open Services console (services.msc)
  2. Right-click Microsoft Azure AD Sync and select Properties
  3. Click the Recovery tab
  4. Set the following recovery options:
    • First failure: Restart the Service
    • Second failure: Restart the Service
    • Subsequent failures: Restart the Service
  5. Set Reset fail count after: 1 days
  6. Set Restart service after: 2 minutes
  7. Click Apply and OK
  8. Restart the service to test the configuration
Warning: Ensure the service account has sufficient privileges before configuring automatic restart options.

Verification: Stop the service manually and wait 2 minutes to confirm it automatically restarts.

03

Reset Service Dependencies and Permissions

Fix service dependencies and permissions that may prevent the ADSync service from starting properly.

  1. Open an elevated Command Prompt as Administrator
  2. Stop the Azure AD Sync service:
    net stop ADSync
  3. Reset service dependencies:
    sc config ADSync depend= RpcSs/EventLog
  4. Verify the service account permissions:
    Get-WmiObject -Class Win32_Service -Filter "Name='ADSync'" | Select-Object Name, StartName
  5. Grant the service account "Log on as a service" right:
    • Open Local Security Policy (secpol.msc)
    • Navigate to Local PoliciesUser Rights Assignment
    • Double-click Log on as a service
    • Add the ADSync service account if not present
  6. Start the service:
    net start ADSync
  7. Check service status:
    Get-Service ADSync

Verification: Run Get-Service ADSync and confirm the status shows as "Running". Test Azure AD Connect wizard functionality.

04

Repair Azure AD Connect Installation

Use the Azure AD Connect repair function to fix corrupted service configurations and restore proper functionality.

  1. Download the latest Azure AD Connect installer from the Microsoft Download Center
  2. Run the installer as Administrator
  3. On the welcome screen, select Repair or reinstall an existing Azure AD Connect installation
  4. Click Next and accept the license terms
  5. On the repair options screen, select Repair
  6. The installer will:
    • Repair service configurations
    • Reset registry entries
    • Restore default permissions
    • Update service dependencies
  7. Wait for the repair process to complete
  8. Click Finish when the repair is successful
  9. Restart the server to ensure all changes take effect
Pro tip: Before running repair, export your current Azure AD Connect configuration using the synchronization service manager.

Verification: After restart, check that the Microsoft Azure AD Sync service starts automatically and Azure AD Connect wizard opens without errors.

05

Advanced Troubleshooting with Event Logs and Registry

Perform advanced diagnostics to identify and resolve underlying issues preventing service startup.

  1. Check Windows Event Logs for service startup errors:
    Get-EventLog -LogName System -Source "Service Control Manager" -After (Get-Date).AddDays(-1) | Where-Object {$_.Message -like "*ADSync*"}
  2. Examine Azure AD Connect specific logs:
    Get-ChildItem "C:\ProgramData\AADConnect\trace-*.log" | Sort-Object LastWriteTime -Descending | Select-Object -First 5
  3. Verify registry entries for the ADSync service:
    Get-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Services\ADSync"
  4. Check database connectivity:
    Test-NetConnection -ComputerName localhost -Port 1433
  5. If registry corruption is detected, restore from backup or recreate service entry:
    sc delete ADSync
    sc create ADSync binPath= "C:\Program Files\Microsoft Azure AD Sync\Bin\miiserver.exe" start= auto
  6. Restart the Windows Management Instrumentation service:
    net stop winmgmt /y
    net start winmgmt
  7. Start the ADSync service and monitor for errors
Warning: Registry modifications can cause system instability. Always backup the registry before making changes.

Verification: Monitor Event Viewer for successful service startup events and confirm synchronization resumes in Azure AD Connect Health portal.

Validation

Verification

To confirm the Azure AD Sync service is working properly:

  1. Open Services console and verify Microsoft Azure AD Sync shows status as Running
  2. Launch Azure AD Connect wizard - it should open without the "Sync Service not running" error
  3. Run a manual synchronization test:
    Start-ADSyncSyncCycle -PolicyType Delta
  4. Check synchronization status:
    Get-ADSyncScheduler
  5. Verify in Azure AD portal that recent synchronization activity appears in the Azure AD Connect Health section
  6. Monitor for 24-48 hours to ensure automatic synchronization cycles complete successfully
If it still fails

Advanced Troubleshooting

If the above methods didn't resolve the issue, try these advanced troubleshooting steps:

  • Check SQL Server LocalDB: The ADSync service depends on SQL Server LocalDB. Verify it's installed and running with sqllocaldb info
  • Antivirus Exclusions: Add Azure AD Connect installation directory and processes to antivirus exclusions
  • Network Connectivity: Test connectivity to Azure AD endpoints using Test-NetConnection login.microsoftonline.com -Port 443
  • Certificate Issues: Check for expired certificates that might prevent secure connections to Azure AD
  • Disk Space: Ensure adequate disk space on system drive for log files and temporary data
  • Windows Updates: Install latest Windows updates and restart the server
  • Complete Reinstall: As a last resort, uninstall Azure AD Connect completely, clean registry entries, and perform a fresh installation

Frequently Asked Questions

What is the Microsoft Azure AD Sync service and why is it critical?+
The Microsoft Azure AD Sync service (ADSync) is the core component of Azure AD Connect that handles directory synchronization between on-premises Active Directory and Azure Active Directory. It runs continuously in the background, synchronizing user accounts, groups, contacts, and password hashes according to configured schedules. Without this service running, no synchronization occurs, which can lead to authentication issues, outdated user information in Azure AD, and disrupted access to cloud services for hybrid environments.
How often should the Azure AD Sync service synchronize data?+
By default, Azure AD Connect performs delta synchronization every 30 minutes, which synchronizes only changes since the last sync cycle. Full synchronization occurs less frequently and can be triggered manually or by configuration changes. You can check the current synchronization schedule using the PowerShell command Get-ADSyncScheduler. The service must be running continuously to maintain this schedule and ensure timely synchronization of directory changes.
Can I safely restart the Azure AD Sync service during business hours?+
Yes, restarting the Azure AD Sync service during business hours is generally safe and won't disrupt user authentication or access to cloud services. The service only handles synchronization of directory changes, not real-time authentication. However, any synchronization in progress will be interrupted and will resume with the next scheduled cycle. For large environments, consider restarting during maintenance windows to avoid potential delays in synchronizing critical changes like password resets or new user accounts.
What should I do if the service keeps stopping automatically?+
If the Azure AD Sync service repeatedly stops, first check Windows Event Logs for specific error messages that indicate the root cause. Common issues include insufficient disk space, database connectivity problems, corrupted configuration files, or antivirus software interference. Configure service recovery options to automatically restart the service, but also address the underlying cause. Check that the service account has proper permissions, verify SQL Server LocalDB is functioning, and ensure adequate system resources are available.
How can I monitor Azure AD Sync service health proactively?+
Monitor the service using multiple approaches: Enable Azure AD Connect Health for cloud-based monitoring and alerts, set up Windows Performance Monitor counters for the ADSync service, configure Event Log monitoring for service startup/shutdown events, and use PowerShell scripts to check service status regularly. Additionally, monitor synchronization cycles using Get-ADSyncScheduler and review Azure AD Connect Health reports in the Azure portal for synchronization errors or warnings that might indicate impending service issues.
Evan Mael
Written by

Evan Mael

Microsoft MCSA-certified Cloud Architect | Fortinet-focused. I modernize cloud, hybrid & on-prem infrastructure for reliability, security, performance and cost control - sharing field-tested ops & troubleshooting.

Discussion

Share your thoughts and insights

Sign in to join the discussion