Complete Transfer to Cloud Sync (issue)

Chris Atzinger 0 Reputation points
2026-11-18T03:34:45.7166667+00:00

I thought I'd get started on transitioning from Entra Connect to Cloud Sync. Our domain is (IMHO) simple and straight-forward. I have 2 DCs (DC1, DC2) and I've setup a member server (AD1) that's been running Entra Connect on Windows Server 2022 since early 2021 (I did have to upgrade the TLS a while ago). I upgraded AD Connect manually a few weeks ago and saw that there is now a required migration to Cloud Sync.

I have made it through all of the steps (and passed). I also verified a DN in the Entra portal as requested by "Step 1" Provisioning on Demand, but I cannot get past "Step 2" Complete Transfer to Cloud Sync".

I will click on "Complete Transfer to Cloud Sync" and wait... then I'll see the following:

Cloud Sync activation failed before commit and the original state was restored. The migration transition failed before commit. The original state was restored. Error: Required Cloud Sync jobs did not become active within five minutes: 'AD2AADProvisiong" for domain "company.com" (AD2AADProvisiongxxxxxxxxxxxxxxxxxx) (state: NotRun), "AD2AADPasswordHash" for domain "company.com" (AD2AADPasswordHashxxxxxxxx) (state: NotRun).

Correct the reported transient condition, then select Activate again.

Any advice, or what to look at to resolve?

All tests passed, etc. I did see an error the very first time I ran it something about an account (gMSA), but when I closed and restarted everything came up fine and continued. I can log in and see "disabled" for the domain in the dashboard and for the agent I see "active".

Microsoft Security | Microsoft Entra | Other
0 comments No comments

2 answers

Sort by: Most helpful
  1. Chris Atzinger 0 Reputation points
    2026-11-18T18:22:40.65+00:00

    I do also believe the issue is with the gMSA account. I have done the following today:

    Install-WindowsFeature RSAT-AD-PowerShell

    Import-Module ActiveDirectory

    Test-ADServiceAccount -Identity "pGMSA_xxxxxxxx"

    Test-ADServiceAccount : Cannot find an object with identity: 'pGMSA_xxxxxxxx' under: 'DC=crsreprocessingllc,DC=local'.

    At line:1 char:1

    • Test-ADServiceAccount -Identity "pGMSA_xxxxxxxx"
    • CategoryInfo : ObjectNotFound: (:) [Test-ADServiceAccount], ADIdentityNotFoundException
      • FullyQualifiedErrorId : ActiveDirectoryCmdlet:Microsoft.ActiveDirectory.Management.ADIdentityNotFoundException,M
      icrosoft.ActiveDirectory.Management.Commands.TestADServiceAccount

    When I open services.msc on AD1 (this is where I was running PowerShell & where AD Connect has been running) I can see three related services running.

    Microsoft Azure AD Connect Agent Updater (Log On As: NT Authority\System)

    • Microsoft Azure AD Connect Provisioning Agent (Log On As: company.local\pGMSA_xxxxxxxx)
    • Microsoft Azure AD Sync (Log On As: NT Service\ADSync)

    The services are running. I can stop and restart them without error.

    Please advise.

    Was this answer helpful?

    0 comments No comments

  2. Ali N. Chouman 0 Reputation points
    2026-11-18T09:12:04.75+00:00

    Based on the error, I would focus first on the Cloud Sync provisioning agent and its gMSA configuration rather than the AD Connect configuration itself.

    Although the agent shows as Active in Entra, this only confirms that the agent is registered and communicating. The two required jobs (AD2AADProvisioning and AD2AADPasswordHash) are still not starting.

    Since you mentioned seeing an initial gMSA-related error during installation, I would investigate that first:

    On AD1, verify that the Microsoft Entra Provisioning Agent and Agent Updater services are running.

    Verify the gMSA account and test it using PowerShell: Test-ADServiceAccount -Identity "provAgentgMSA" (Replace with the actual gMSA name.)

    If the test returns False, investigate KDS configuration, gMSA permissions and replication between DC1 and DC2.

    Check Windows Event Viewer, particularly System logs and Service Control Manager events. Event ID 7041 is worth checking because it can indicate missing service logon rights.

    Review the provisioning agent trace logs under: C:\ProgramData\Microsoft\Azure AD Connect Provisioning Agent\Trace

    If all these checks pass, I would export the migration wizard diagnostics and investigate the activation failure with Microsoft Support.

    I would also avoid manually deleting or modifying the Cloud Sync configurations created by the migration wizard, as this could interfere with its recovery mechanism.

    My first suspicion would be something related to the gMSA/service initialization, given the initial installation error you mentioned.

    Was this answer helpful?

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.