Entra Connect Sync or Cloud Sync? Hybrid Identity Synchronization

Entra Connect Sync or Cloud Sync: the PHS, PTA and federation decision, AD cleanup with IdFix, staging mode and reading sync errors in the console.
Technical summary
Technology
Microsoft Entra Connect Sync, Entra Cloud Sync, Active Directory, PHS, PTA, AD FS, IdFix
Topic
Choosing, installing and operating a hybrid identity sync tool
Level
Intermediate–advanced
Prerequisites
  • Active Directory administration and PowerShell knowledge
  • Hybrid Identity Administrator or Global Administrator rights in Entra ID
  • A verified domain in Microsoft 365
In this article8 sections

In hybrid identity, cleaning up AD data and deciding on the authentication method matter as much as choosing the tool. There are two official ways to connect on-premises Active Directory to Microsoft Entra ID: Entra Connect Sync and Entra Cloud Sync. Both bring users, groups and password hashes to the cloud; their architectures, supported scenarios and operating overhead differ. Below we go through choosing the tool, the PHS/PTA/federation decision, AD preparation and how to read sync errors.

Two sync tools for hybrid identity

Entra Connect Sync, formerly Azure AD Connect, is a full sync engine installed on a Windows Server. Connector spaces, the metaverse and sync rules live in a local SQL database on the server. Configuration is done with the wizard on the server and the Synchronization Rules Editor.

Entra Cloud Sync moves the configuration to the cloud. On premises, only a lightweight provisioning agent (Microsoft Entra provisioning agent) runs; it connects to Entra ID over outbound 443, and the sync logic runs in Microsoft’s cloud service. High availability is achieved by installing more than one agent; the agents run active–active.

Microsoft is developing new features mainly on Cloud Sync and recommends it for most organizations. Some scenarios Connect Sync supports, however, are not available in Cloud Sync. Base your decision on these differences.

Feature comparison table

Scenario Connect Sync Cloud Sync
Installed component Sync engine + SQL Express LocalDB on the server (10 GB limit; full SQL Server above roughly 100,000 objects) Lightweight agent, configuration in the cloud
High availability Staging mode server (manual switchover) Multiple active agents
Disconnected multiple forests The sync server needs access to all forests A separate agent per forest; supported
Password Hash Sync Yes Yes
Pass-through Authentication Configured from the wizard Not configured from Cloud Sync; PTA agents are managed separately
Hybrid join device sync Yes Yes (enabled separately)
Scale No object limit per domain; groups with up to 250,000 members 150,000 objects per domain; groups with up to 50,000 members
Exchange hybrid writeback Yes Yes
Custom sync rules Synchronization Rules Editor Limited to attribute mapping expressions
Filtering Domain, OU, attribute OU or group scope

Microsoft regularly expands this feature set; check the current comparison page on Microsoft Learn before deciding. Ask these questions: Are there attribute transformations that need advanced sync rules? Do you need cross-forest object references or merging attributes from more than one domain? Does the domain have more than 150,000 objects or groups with more than 50,000 members? If you answer “yes” to any, you need Connect Sync. Device sync for hybrid Entra join exists in both tools; in Cloud Sync it is enabled separately. PTA and federation aren’t configured from Cloud Sync; they are managed with separate tools. If disconnected forests after a merger or reducing server maintenance overhead is the priority, Cloud Sync comes out ahead.

Device sync, device join and sign-in method are three separate topics. In Cloud Sync, device sync is off by default: after the service connection point (SCP) is configured in each forest, it is enabled separately in the Cloud Sync configuration and requires provisioning agent version 1.1.1107 or later. Sync only moves computer objects in AD to Entra ID. Hybrid join is completed when the device finds the tenant through the SCP and registers. How the user signs in (PHS, PTA or federation) is a decision independent of these.

Authentication method: PHS, PTA and federation

The sync tool and how users sign in are separate decisions.

  • Password Hash Synchronization (PHS): Authentication happens entirely in the cloud. Even if the on-premises server and systems infrastructure goes down, users can still access Microsoft 365. Entra ID Protection features such as leaked credential detection rely on PHS. For most organizations this is the default option with the fewest dependencies.
  • Pass-through Authentication (PTA): The password is validated directly against a DC by on-premises PTA agents. It is preferred by organizations that require that no derivative of the password goes to the cloud. The price is that the agents and DC access become the only way to sign in. Microsoft recommends more than one agent for high availability; even with PTA, consider keeping PHS enabled as a backup.
  • Federation (AD FS): Authentication is handed off to an on-premises AD FS farm. It needs additional servers, certificates and a WAP layer. Microsoft recommends moving from federation to managed authentication (PHS or PTA); in a new deployment it is considered only if there is a real requirement such as smart cards or third-party MFA. An expired token-signing certificate stops federated sign-ins.

Conditional access and MFA policies after sign-in are a separate design topic, covered in our Conditional Access planning guide.

AD preparation before sync: UPN suffix, IdFix, OU filtering

Many sync errors come from AD data that could be cleaned up before installation.

  1. Routable UPN suffix: If the forest is named example.local, users are synchronized as [email protected] and end up with an onmicrosoft.com address in the cloud. In Active Directory Domains and Trusts, the verified domain (example.com) is added as a UPN suffix, and users’ UPNs are updated to match their primary email address.
  2. IdFix scan: Microsoft’s open-source IdFix tool lists duplicate proxyAddresses and UPN values, invalid characters and format errors. The suggested fixes can be applied in bulk, but export and review every change first.
  3. OU filtering: Service accounts, disabled users, test objects and built-in groups are kept out of sync scope. If scope will be defined by OU structure, user and computer objects are first moved into well-organized OUs.
  4. AD health: Replication errors, stale DC records and DNS problems directly break sync. Complete the Active Directory health check steps before installation.

A controlled PowerShell example for updating UPNs:

Import-Module ActiveDirectory
$ou = "OU=Users,OU=HQ,DC=example,DC=local"
Get-ADUser -SearchBase $ou -Filter * -Properties mail |
  Where-Object { $_.mail -like "*@example.com" } |
  ForEach-Object {
    Set-ADUser $_ -UserPrincipalName $_.mail -WhatIf
  }

After checking the -WhatIf output, remove the parameter and apply the change. Sign-in in the DOMAIN\user format (sAMAccountName) doesn’t change; users who sign in with their UPN and applications that use the UPN as an identity are affected. Announce the change in advance. A silent UPN change generates support requests.

Installation steps and the staging mode server

Entra Connect Sync

  1. A domain-joined, up-to-date Windows Server is prepared. Installing on a DC is supported, but a separate member server is cleaner in terms of operations and security. Protect this server as a Tier 0 asset; if it is compromised, AD and cloud identity go together.
  2. The current Entra Connect version is downloaded from the Microsoft Entra admin center. Since support for older versions ends at intervals, regularly compare the installed version with Microsoft’s version history page.
  3. Choose customized installation; define the authentication method, forests, OU filter, source anchor attribute (default ms-DS-ConsistencyGuid) and optional features (Exchange hybrid, password writeback).
  4. The “Start the synchronization process when configuration completes” option can be left unchecked on the first installation, so the first sync is started after the scope has been checked.

Staging mode: A second server is installed with the same configuration, and staging mode is enabled in the wizard. This server performs imports and syncs but no exports. When the primary server fails or during an upgrade, the pending exports on the staging server are reviewed and the server is made active by turning off staging mode. There are never two active servers at the same time.

# Scheduler status and last cycle
Get-ADSyncScheduler

# Stop the scheduler before maintenance
Set-ADSyncScheduler -SyncCycleEnabled $false

# Delta or full cycle after a change
Start-ADSyncSyncCycle -PolicyType Delta
Start-ADSyncSyncCycle -PolicyType Initial

Set-ADSyncScheduler -SyncCycleEnabled $true

Entra Cloud Sync

  1. For high availability, the provisioning agent is installed on at least two member servers (preferably three, as Microsoft recommends), and each is registered with Entra ID; the agent setup wizard creates a gMSA by default.
  2. A Cloud Sync configuration is created in the Entra admin center; scope is defined by OU or group, and attribute mappings are adjusted with expressions if needed.
  3. A single user is tested with “Provision on demand,” and the result is shown step by step. The configuration is then enabled.

Reading and fixing sync errors

Errors appear on the server in the Operations tab of Synchronization Service Manager, and in the Entra admin center under Entra Connect Health (Connect Health reports require an Entra ID P1 license). The first place to look in the console is the last export step in the Operations tab. The most common ones:

Error Meaning How to fix
AttributeValueMustBeUnique The same proxyAddresses or UPN exists on another object Find the conflicting object and make the value unique
InvalidSoftMatch The matching cloud object is linked to another AD object Review the link and the sourceAnchor value
DataValidationFailed Invalid character or format Fix it with IdFix
LargeObject Attribute size limit exceeded (e.g. many certificates) Clean up unnecessary values

Query AD directly to find the conflicting value:

Get-ADObject -Filter "proxyAddresses -eq 'smtp:[email protected]'" -Properties proxyAddresses |
  Select-Object DistinguishedName, ObjectClass

After fixing the error, run a delta cycle and confirm the error is gone. To understand why a single object isn’t syncing, check Metaverse Search and the connector space object properties in Synchronization Service Manager; an object caught by the scope filter shows as “filtered” in the connector space. If the object isn’t there at all, the problem is the filter. If it’s there but not moving on, the problem is a rule.

Migrating from Connect Sync to Cloud Sync

You don’t move from an existing Connect Sync installation to Cloud Sync in one go. The pilot approach Microsoft documents is as follows:

  1. Confirm that Cloud Sync meets your needs: if there is no blocker such as advanced sync rules, cross-forest references or scale limits, the migration can be planned. If you use device sync, Microsoft’s migration tool lists it as a blocker; add device sync to the migration plan separately.
  2. Choose an OU for the pilot. When taking this OU out of Connect Sync scope, apply the rule changes in Microsoft’s pilot document so that objects aren’t deleted in the cloud; the scheduler is stopped during this.
  3. Create the Cloud Sync configuration to cover only the pilot OU, verify it with provision on demand and enable it.
  4. Watch the pilot objects over several sync cycles; test sign-in, password changes and group memberships.
  5. Expand the scope in stages; remove Connect Sync after all objects have been moved.

At each stage, make sure the same object isn’t managed by both tools at once. Once the identity infrastructure is ready, you can move on to our articles on Exchange Online migration methods for mail and device setup with Windows Autopilot for devices. Microsoft’s Entra hybrid identity documentation should be the official reference. For hybrid identity design and an assessment of your existing AD, see our infrastructure consulting and Microsoft 365 services pages.

Frequently asked questions

Can Entra Connect Sync and Cloud Sync work together in the same tenant?

Yes. Microsoft supports using both tools in the same tenant; for example, you can sync a disconnected forest with Cloud Sync and the main forest with Connect Sync. The rule is that the same object must not be in scope of both tools at the same time; scope should be clearly separated with OU or group filters.

Does Password Hash Synchronization send the passwords themselves to the cloud?

No. PHS doesn’t send the AD password hash itself to Entra ID, but a value derived from that hash with additional salting and many iterations. The on-premises password hash can’t be recovered from this value. PHS is also required for Entra ID Protection features such as leaked credential detection to work.

Does a staging mode server require a license or extra cost?

No separate Microsoft license is needed for Entra Connect Sync; the staging server is just an extra Windows Server instance. It is installed with the same configuration and performs imports and syncs but doesn’t write to Entra ID or AD. When the primary server fails, it is brought into service by turning off staging mode.

How do I trigger a sync cycle manually?

On the Entra Connect Sync server, the PowerShell command Start-ADSyncSyncCycle -PolicyType Delta syncs only the changes. After a rule or filter change, run a full sync with Start-ADSyncSyncCycle -PolicyType Initial. In Cloud Sync, a single user is tested with provision on demand on the configuration screen.

Support

Contact us for support or a discovery session on this topic.

Contact form
[email protected]

Eretek System Support

Server installation, configuration, incident response and scheduled maintenance. Active Directory, virtualization and backup are managed with the same discipline.

Knowledge Center

Other articles