Entra Connect vs Cloud Sync: how to choose for a hybrid environment

Compare Microsoft Entra Connect Sync and Cloud Sync capabilities, then plan a migration pilot with validation and rollback.

01

Two engines, one architecture decision

Connect Sync runs rules on an on-premises server. Cloud Sync orchestrates provisioning from Entra through domain-joined agents; multiple active agents can provide redundancy. In either case, a sync outage is not necessarily a sign-in outage: inventory PHS, PTA, federation and Seamless SSO separately. At fictional Boreal Workshop, an acquired forest is disconnected while headquarters uses cross-forest join rules. Evaluate these needs separately.

02

1. Read Microsoft’s matrix against your dependencies

Both engines synchronize users, groups and contacts and support password hash synchronization (PHS). Cloud Sync is suited to disconnected forests and provisioning Entra groups to AD. Connect Sync remains relevant for advanced rules, cross-forest references or groups exceeding Cloud Sync limits. Microsoft’s matrix lists 150,000 objects per domain and 50,000 group members for Cloud Sync; check scope and flow direction before applying those ceilings. Support for Exchange hybrid attributes does not remove the need to test your actual Exchange flows and features.

03

2. Devices and authentication: avoid false equivalences

Cloud Sync can synchronize computer objects for Entra hybrid join when the separate feature is configured; the current matrix still lists device synchronization as a blocker for the guided migration tool. This is neither device writeback nor an Intune migration. Cloud Sync does not configure PTA or AD FS as Connect Sync does; avoid changing the sign-in method at the same time as the sync engine. Check hybrid join documentation, platform support and migration-path eligibility before approval.

04

3. Check versions, roles and licensing

Record the Connect Sync and agent builds, then check release history and requirements for your chosen path. Microsoft recommends domain-joined Windows Server 2022 or 2025 for the agent; Server Core is unsupported. Check TLS 1.2, outbound and proxy access, domain controller connectivity and gMSA. Documented setup uses a non-guest Hybrid Identity Administrator and elevated AD rights to create the gMSA; keep this separate from inventory and do not retain these privileges on an operating account. Check licensing by feature: Microsoft documents Entra ID P1 for group provisioning to AD; separately review SSPR and password writeback entitlements.

05

4. Establish a read-only baseline

On the Connect server, use an account authorized to read ADSync configuration and check staging mode, connectors and rules. Export configuration using Microsoft’s method before changes; an export is not a directory backup. In Entra, record object IDs and anchors for an authorized pilot sample, memberships, managers and required Exchange attributes. The local commands below start no sync cycle and cannot establish sign-in dependencies or effective permissions by themselves. Protect the output.

PowerShell — read only
# Connect Sync, Windows PowerShell — read only
Import-Module ADSync
Get-ADSyncScheduler | Select-Object SyncCycleEnabled,StagingModeEnabled
Get-ADSyncConnector | Select-Object Name,ConnectorTypeName
Get-ADSyncRule | Select-Object Name,Direction,Precedence,Disabled
06

5. Choose a migration path before changing filters

Use the guided tool only if the option appears on the active server and its readiness review confirms eligibility. Otherwise use a documented manual path for your topology or retain Connect. In Microsoft’s manual pilot, objects stay in Connect scope with the documented cloudNoFlow and JoinNoFlow rules; those rules block the relevant normal exports while some references may continue to flow. Do not remove the OU from scope as a cutover shortcut or let two engines normally export the same objects. Premature exclusion can remove memberships or other references.

07

6. Pilot, accept or roll back

In an approved window, start with a small representative OU and follow the chosen path. Validate unchanged Entra ID, sign-in, a password change on a test account, groups, managers and any applicable Exchange or device workflows. Review provisioning logs, agent health and unexpected deletions. Stop the wave if identities duplicate, references disappear or sign-in regresses. To roll back, stop new Cloud Sync exports for the batch using the documented path before returning authority to Connect; inspect pending exports before resuming. An already exported deletion requires separate recovery. Keep the baseline configuration and retire Connect only after acceptance and reference validation. This focused review complements a hybrid identity assessment.

08

Microsoft Learn references