Microsoft Azure AD Sync service not showing in Services.msc but shows in Get-Service

Question

We've noticed that "Microsoft Azure AD Sync" & "Microsoft Azure AD Connect Agent Updater" services are not showing up in Services.msc but shows up in Get-Service PowerShell command & also in Task Manager >> Services, as "Microsoft Azure AD Sync (ADSync)" & "Microsoft Azure Connect Agent Updater" (AzureADConnectAgentUpdater).

Investigating further, I've noticed that this service is showing up in not just Get-Service command but also in Registry (Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ADSync) – just not in Services.msc

We've tried to repair & reinstall Azure AD Connect sync (Microsoft Entra Connect sync - v2.4.129.0), along with checking SFC & DISM command & further clearing any pending updates & restarting server a few times but still the same.

Is there anything further we'd do to see why the service exists on the server/system, yet not showing up in Services.msc?

Answer 1

Hi Darsh,

Thanks for your post. Please make sure ADSync service account can log on locally, as a service.

1. Select Start, enter gpedit.msc in the search box, and then press Enter to open the Local Group Policy Editor snap-in.
2. In the console tree, under Computer Configuration, expand Windows Settings > Security Settings > Local Policies, and then select User Rights Assignment.
3. Verify that the ADSync service account is added for the following policy settings:

Log on as a service

Reference. https://learn.microsoft.com/en-us/troubleshoot/entra/entra-id/user-prov-sync/services-sync-not-start

Best Regards,

Ian Xue

---

If the Answer is helpful, please click "Accept Answer" and upvote it.

Answer 2

Thanks for your time in getting back.

Whilst I've now added this account in "Log on as a service", I'm not entirely convinced if this is needed, as even without it, the "Microsoft Azure AD Sync" service was already running & syncing users from on-prem DC to O365. If permission was an issue, I'd have thought even syncing would've have been happening. Also, Get-Service command did show the service running along with the Task Manager - just not in the Services.msc

Hence, it seems less of a permission issue & more of a visual/display issue in Services.msc not showing this service at all.