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.

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.
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.
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
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
Solutions
Start Azure AD Sync Service Manually
This is the quickest method to resolve the immediate issue and restore synchronization.
- Press Windows + R to open the Run dialog
- Type
services.mscand press Enter - In the Services console, scroll down and locate Microsoft Azure AD Sync
- Check the service status - it should show as Stopped
- Right-click on Microsoft Azure AD Sync and select Properties
- Verify the Startup type is set to Automatic. If not, change it to Automatic
- Click Apply, then click Start to start the service
- Wait for the service status to change to Running
- Click OK to close the Properties dialog
Start-Service ADSyncVerification: Open Azure AD Connect wizard and confirm the "Sync Service not running" error no longer appears. Check the service status shows as Running.
Configure Service Recovery Options
Configure automatic recovery to prevent future service failures from causing extended downtime.
- Open Services console (
services.msc) - Right-click Microsoft Azure AD Sync and select Properties
- Click the Recovery tab
- Set the following recovery options:
- First failure: Restart the Service
- Second failure: Restart the Service
- Subsequent failures: Restart the Service
- Set Reset fail count after: 1 days
- Set Restart service after: 2 minutes
- Click Apply and OK
- Restart the service to test the configuration
Verification: Stop the service manually and wait 2 minutes to confirm it automatically restarts.
Reset Service Dependencies and Permissions
Fix service dependencies and permissions that may prevent the ADSync service from starting properly.
- Open an elevated Command Prompt as Administrator
- Stop the Azure AD Sync service:
net stop ADSync - Reset service dependencies:
sc config ADSync depend= RpcSs/EventLog - Verify the service account permissions:
Get-WmiObject -Class Win32_Service -Filter "Name='ADSync'" | Select-Object Name, StartName - Grant the service account "Log on as a service" right:
- Open Local Security Policy (secpol.msc)
- Navigate to Local Policies → User Rights Assignment
- Double-click Log on as a service
- Add the ADSync service account if not present
- Start the service:
net start ADSync - Check service status:
Get-Service ADSync
Verification: Run Get-Service ADSync and confirm the status shows as "Running". Test Azure AD Connect wizard functionality.
Repair Azure AD Connect Installation
Use the Azure AD Connect repair function to fix corrupted service configurations and restore proper functionality.
- Download the latest Azure AD Connect installer from the Microsoft Download Center
- Run the installer as Administrator
- On the welcome screen, select Repair or reinstall an existing Azure AD Connect installation
- Click Next and accept the license terms
- On the repair options screen, select Repair
- The installer will:
- Repair service configurations
- Reset registry entries
- Restore default permissions
- Update service dependencies
- Wait for the repair process to complete
- Click Finish when the repair is successful
- Restart the server to ensure all changes take effect
Verification: After restart, check that the Microsoft Azure AD Sync service starts automatically and Azure AD Connect wizard opens without errors.
Advanced Troubleshooting with Event Logs and Registry
Perform advanced diagnostics to identify and resolve underlying issues preventing service startup.
- 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*"} - Examine Azure AD Connect specific logs:
Get-ChildItem "C:\ProgramData\AADConnect\trace-*.log" | Sort-Object LastWriteTime -Descending | Select-Object -First 5 - Verify registry entries for the ADSync service:
Get-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Services\ADSync" - Check database connectivity:
Test-NetConnection -ComputerName localhost -Port 1433 - 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 - Restart the Windows Management Instrumentation service:
net stop winmgmt /y net start winmgmt - Start the ADSync service and monitor for errors
Verification: Monitor Event Viewer for successful service startup events and confirm synchronization resumes in Azure AD Connect Health portal.
Verification
To confirm the Azure AD Sync service is working properly:
- Open Services console and verify Microsoft Azure AD Sync shows status as Running
- Launch Azure AD Connect wizard - it should open without the "Sync Service not running" error
- Run a manual synchronization test:
Start-ADSyncSyncCycle -PolicyType Delta - Check synchronization status:
Get-ADSyncScheduler - Verify in Azure AD portal that recent synchronization activity appears in the Azure AD Connect Health section
- Monitor for 24-48 hours to ensure automatic synchronization cycles complete successfully
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?+
How often should the Azure AD Sync service synchronize data?+
Can I safely restart the Azure AD Sync service during business hours?+
What should I do if the service keeps stopping automatically?+
How can I monitor Azure AD Sync service health proactively?+
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.
Further Intelligence
Deepen your knowledge with related resources
Discussion
Share your thoughts and insights
Sign in to join the discussion


