Entra Cloud Sync configuration drop down not listing AD domain

Question

I have AD Connect V2 running on a DC and wanted to migrate to Entra Cloud Sync. I configured staging mode on the Sync DC machine as suggested and then downloaded and installed the Cloud Sync agent which was listed as active on the Entra CS agents portal. When proceeding to configure the sync under the "Add new configuration", no domain gets listed - it's simply empty.

Now after having uninstalled the agent and removed from staging mode AD Connect, it says it syncs but it doesn't, and the last sync time is now updating. I tried adding a test user and forcing a sync and it doesn't appear in Azure so that confirms something is definitely broken here. Users updating their password will not have this reflected in the cloud. I can't remove and Cloud Sync configuration as none are present.

I have configured several Cloud Sync setups and never had this issue. This particular AD domain has Exchange in Full Hybvrid mode so maybe this has something to do with the issue, though I don't see why as I have other setups with Cloud Sync working after running the HCW. Anyhow, any idea why the domain is not listed in the setup? Something appears to have broken tenant side. I opened a support ticket in the mean time.

**Update: I re-enabled staging mode ad then disabled it again and now users are synching so something got stuck there. I still don't see any domain listed, but that's a minor issue atm.

Answer 1

Hi @Luca
Thank you for posting your query on Q&A.

I understand that you are facing an issue with Entra Cloud Sync configuration and in drop down not listing AD domain in the azure portal.
To get the domain name in configuration blade need to validate the Service Account in the Entra cloud sync provisioning agent configuration tool with the on-premise administrator credentials. which shows in the below screen shots.

Step-1

Step-2

Step-3

The other side you are facing sync issues with the AD Connect after successful uninstallation of agent and you have removed the stating mode.
Would you please run the Delta sync cmdlet by using the PowerShell and check.

Start-ADSyncSyncCycle -PolicyType Delta

After performing the Delta Sync if you still persist the issue run the Full sync with the below cmdlet.

Start-ADSyncSyncCycle -PolicyType Initial

After successful full sync check the Entra Portal, is the new user is reflecting or not, if you do not see the new user in users.
Please do share the AD Connect status of each connecters space, also share the operations tab updated details after the successful Delta and Full Sync and please let us know if you see any error in the status of operations tab like no-start-ma.
I hope this answer helps! please Feel free to ask any questions you may have.

Thanks,
Akhilesh.

Please "Accept the answer" if the information helped you. This will help us and others in the community as well.

Answer 2

Hi Akhilesh, as mentioned in my initial reply, I uninstalled the agent and took the AD Connect service out of staging mode (twice) to restore AD Connect sync and all went back to normal. Apparently something got "stuck" and reiterating the operation of putting the sevice in staging and taking the service out of staging mode fixed the stalled synching.

Answer 3

I had this same issue in my lab. It turns out when I installed the Cloud Sync connector, I had selected the wrong bullet. I needed to install it as "HR driven provisioning / Entra Cloud Sync" but I had instead selected the 2nd bullet which was something like "Entra ID to AD for application provisioning." I reinstalled with the 1st bullet selected and the drop down menu was un-greyed out.