How to Migrate Microsoft Entra Cloud Sync to a New Server
Question details
Transfer or recreate the Microsoft Entra Cloud Sync agent and its configuration on a new replacement server.

- Product
- Microsoft Entra Cloud Sync
- Device & OS
- not provided
- Scenario
- Active Directory is being moved to a new domain controller because the old server hosting the Cloud Sync agent is malfunctioning.
- Observed behavior
- The directory synchronization agent needs to be migrated to a new server to maintain hybrid identity synchronization with Microsoft Entra ID.
Verify that your new server meets all Microsoft Entra hardware and OS prerequisites, and ensure you have Hybrid Identity Administrator or Global Administrator privileges before initiating the migration.
Reinstall and Configure the Cloud Sync Agent on the New Server
The standard approach is to perform a fresh installation of the Cloud Sync agent on the new server and recreate your configuration.
By setting up a fresh configuration, you can bypass issues caused by the malfunctioning old server and ensure your new domain controller environment starts with a clean synchronization state.
If the old server is still accessible, navigate to Control Panel > Programs and Features, and uninstall the Microsoft Entra Provisioning Agent to prevent synchronization conflicts.
Log in to the Microsoft Entra admin center, go to Identity > Hybrid management > Microsoft Entra Connect > Cloud sync, and click on 'Agent' to download the latest provision agent.
Run the installer on the new domain controller. During the setup wizard, authenticate using your Global Administrator or Hybrid Identity Administrator credentials.
Return to the Cloud sync portal in Entra ID, select 'New configuration', choose your Active Directory domain, and map your scoping filters and attribute mapping as needed.

Use the Built-In Migration Tool to Transfer Settings
Transfer existing configuration files directly from the old server to the new one using the migration utility located in the installation folder.
Manage Server Migration Documentation Seamlessly with WPS Office
While resolving Microsoft Entra server migrations requires specialized IT skills, keeping track of deployment checklists, server scripts, and migration reports doesn't have to be complicated. WPS Office provides a free, lightweight, and powerful alternative to Microsoft Office, letting you maintain robust IT documentation with full format compatibility.
- 1. Download and Install: Visit the official WPS Office website and download the free installer for your administrative workstation.
- 2. Document Your Server Settings: Use WPS Writer to draft your migration procedures or WPS Spreadsheet to log Active Directory user mapping properties and server IPs.
- 3. Save in MS Office Formats: Save your critical IT documentation in .docx or .xlsx formats so it remains accessible to your entire team.

Frequently Asked Questions
What are the server prerequisites for installing the Microsoft Entra Cloud Sync agent?
The server must be running Windows Server 2016 or later. It requires at least 4 GB of RAM, a minimum of 100 GB of disk space, .NET Framework 4.7.1 or higher, and outbound internet access over port 443 to communicate with Microsoft Entra ID.
Will users experience authentication downtime during the Cloud Sync agent migration?
Generally, no. Cloud Sync handles the synchronization of identities, not real-time authentication pass-through. Any changes made in local AD during the migration window will simply be queued and synced to Entra ID once the new agent is online.
Can I run multiple Cloud Sync agents at the same time for redundancy?
Yes. Microsoft highly recommends deploying multiple Cloud Sync agents across different servers to ensure high availability. If one server goes offline, the other active agents will automatically handle the synchronization workload.
Do I need to reboot the server after installing the new Entra Cloud Sync agent?
A reboot is typically not required after installing the agent unless there are pending Windows updates or a specific dependency like the .NET Framework was installed concurrently.




