Skip to content

TechDirectArchive

Hands-on IT, Cloud, Security & DevOps Insights

  • Home
  • About
  • Advertise With US
  • Reviews
  • Contact
  • Toggle search form
Home » AWS/Azure/OpenShift » AD Connect Sync Service Not Running: Start ADSync to Continue
  • Veeam Plugin update for Proxmox
    Update Veeam Backup for Proxmox Plugin to support PVE 9.0 Backup
  • defdfd
    The password has expired, update your password and try again AWS/Azure/OpenShift
  • ansible 1
    How to fix no Python interpreters found for the host Configuration Management Tool
  • BdeHdCfg
    Fix System Partition not available or large enough on Microsoft BitLocker Administration and Monitoring [Part 1] Windows Server
  • How to Disable Windows Startup Sound in Windows 11 banner
    How to Disable and Enable Startup Sound in Windows 11 Windows
  • Windows Server
    Migrate Roles and Features to Windows Server 2022 using WSMT Windows
  • 1 WeXxkEX0JG3oB781HD8Hrg
    Error 0x204: Unable to Connect to Remote PC [Part 1] Windows Server
  • images
    Query MBAM to display the BitLocker Recovery report Network | Monitoring

AD Connect Sync Service Not Running: Start ADSync to Continue

Posted on 13/07/202001/10/2024 Christian By Christian No Comments on AD Connect Sync Service Not Running: Start ADSync to Continue
AD Connect Sync Service

The Azure Active Directory Connect synchronization services (now called Entra ID Connect sync) serve as a key component in the identity synchronization process. This service efficiently manages all operations related to synchronizing identity data between your on-premises environment and Azure Active Directory (Entra ID). In this article, we shall discuss how to fix AD Connect Sync Service Not Running: Start ADSync to Continue. Please see Fix the Synchronization service scheduler is suspended, and How to Sync Data in Cloud Drives to Synology NAS.

Also, see How to sync on-premises AD with Azure AD via Azure AD Connect, How to use the built-in Azure Active Directory Connect tool, and how to fix “Azure AD Connect Permission issue: Error 8344 insufficient access rights to perform the operation.

Why is the error prompted “AD Connect Sync Service not running”?

You may get the following errors below if you wish to launch (re-configure) the AD-Connect tool or start the synchronization service when the AD Connect Sync Service is not running: Start ADSync to Continue.

AD Connect Sync Service not running: Cannot proceed because the sync service is not running, start the ADSync service and restart the AD Connect Wizard to continue.

start ADSync service
sync service not running

Fix to “Start ADSync to Continue”

To resolve this issue, launch the Windows Services. From the “run” command, type services.msc or from the Server Manager, under tools, search for services. If the AD Connect Sync Service is not running, you must start ADSync to continue.

There are many other ways to launch this, use the one you are most comfortable with.

AD Connect Wizard restart

To ensure the service is started automatically. Right click on the service name “Microsoft Azure AD Sync”

Click on Properties as shown below.

AD Connect Sync Service

As we can see, the service is set to start Automatically. Then we are good to go.

sync service not running

Now, let’s start the service by clicking on start. As we can see below, the service is starting.

start ADSync service

As we can see from the image below, the service has started and running as desired.

AD Connect Wizard restart

Now you can launch the AD Connect Tool once again or the Synchronization Service from the start up menu.

As we can see, the service is running, and now we can launch the Synchronization Service Manager.

Let’s initiate a delta sync and you can see from the image below the status is in progress.

I hope you found this blog post helpful. Please let me know in the comment session if you have any questions.

5/5 - (1 vote)

Thank you for reading this post. Kindly share it with others.

  • Share on X (Opens in new window) X
  • Share on Reddit (Opens in new window) Reddit
  • Share on LinkedIn (Opens in new window) LinkedIn
  • Share on Facebook (Opens in new window) Facebook
  • Share on Pinterest (Opens in new window) Pinterest
  • Share on Tumblr (Opens in new window) Tumblr
  • Share on Telegram (Opens in new window) Telegram
  • Share on WhatsApp (Opens in new window) WhatsApp
  • Share on Pocket (Opens in new window) Pocket
  • Share on Mastodon (Opens in new window) Mastodon
  • Share on Bluesky (Opens in new window) Bluesky
  • Share on Threads (Opens in new window) Threads
  • Share on Nextdoor (Opens in new window) Nextdoor
AWS/Azure/OpenShift Tags:AD Connect, AD Connect Error, Azure, Azure AD

Post navigation

Previous Post: Enter connection information for your on-premise directory or forests: Azure AD connect unable to connect directory, forest not available
Next Post: Pass-Through Authentication: Azure AD Connect Tool status displays inactive

Related Posts

  • front
    How to trigger SQS from a Lambda Function in the same account AWS/Azure/OpenShift
  • azurv2 1
    How to scale up and scale out on Azure AWS/Azure/OpenShift
  • Webp.net resizeimage 2
    Add or Remove Network Interface from a VM in Azure AWS/Azure/OpenShift
  • EC2 Public IP
    How to Allocate, Associate, Disassociate and Release Elastic IP Address from an EC2 Instance AWS/Azure/OpenShift
  • youtube cover blue
    How to use the Azure Cloud Shell or Azure CLI and Azure PowerShell AWS/Azure/OpenShift
  • AADSTS50020  User from Identity Provider does not exist in Tenant
    AADSTS50020: User from Identity Provider does not exist in Tenant AWS/Azure/OpenShift

More Related Articles

front How to trigger SQS from a Lambda Function in the same account AWS/Azure/OpenShift
azurv2 1 How to scale up and scale out on Azure AWS/Azure/OpenShift
Webp.net resizeimage 2 Add or Remove Network Interface from a VM in Azure AWS/Azure/OpenShift
EC2 Public IP How to Allocate, Associate, Disassociate and Release Elastic IP Address from an EC2 Instance AWS/Azure/OpenShift
youtube cover blue How to use the Azure Cloud Shell or Azure CLI and Azure PowerShell AWS/Azure/OpenShift
AADSTS50020  User from Identity Provider does not exist in Tenant AADSTS50020: User from Identity Provider does not exist in Tenant AWS/Azure/OpenShift

Leave a Reply Cancel reply

You must be logged in to post a comment.

Microsoft MVP

VEEAMLEGEND

vexpert-badge-stars-5

Virtual Background

GoogleNews

Categories

veeaam100

sysadmin top30a

  • Veeam Plugin update for Proxmox
    Update Veeam Backup for Proxmox Plugin to support PVE 9.0 Backup
  • defdfd
    The password has expired, update your password and try again AWS/Azure/OpenShift
  • ansible 1
    How to fix no Python interpreters found for the host Configuration Management Tool
  • BdeHdCfg
    Fix System Partition not available or large enough on Microsoft BitLocker Administration and Monitoring [Part 1] Windows Server
  • How to Disable Windows Startup Sound in Windows 11 banner
    How to Disable and Enable Startup Sound in Windows 11 Windows
  • Windows Server
    Migrate Roles and Features to Windows Server 2022 using WSMT Windows
  • 1 WeXxkEX0JG3oB781HD8Hrg
    Error 0x204: Unable to Connect to Remote PC [Part 1] Windows Server
  • images
    Query MBAM to display the BitLocker Recovery report Network | Monitoring

Subscribe to Blog via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 1,832 other subscribers
  • RSS - Posts
  • RSS - Comments
  • About
  • Authors
  • Write for us
  • Advertise with us
  • General Terms and Conditions
  • Privacy policy
  • Feedly
  • Telegram
  • Youtube
  • Facebook
  • Instagram
  • LinkedIn
  • Tumblr
  • Pinterest
  • Twitter
  • mastodon

Tags

AWS Azure Bitlocker Microsoft Windows PowerShell WDS Windows 10 Windows 11 Windows Deployment Services Windows Server 2016

Copyright © 2025 TechDirectArchive

 

Loading Comments...
 

You must be logged in to post a comment.