Identity

Microsoft Entra Connect Sync: A Practical Guide

What Is Microsoft Entra Connect Sync?

Microsoft Entra Connect Sync, formerly Azure AD Connect Sync, is the Windows Server application that copies users, groups and other objects from on-premises Active Directory into Microsoft Entra ID, so people sign in to Microsoft 365 and other cloud apps with the same identity they use on the corporate network. The tool is free. Microsoft renamed Azure AD to Microsoft Entra ID in 2023.

As of November 2026, the current release is version 2.6.92.0 (September 23, 2026), a security hotfix Microsoft says to install as soon as possible. Two things matter most right now:

  • A hard deadline. Servers must run version 2.6.84.0 or later and use application-based authentication by April 7, 2027. Microsoft states that synchronization stops working after that date for servers that haven’t made the change. The steps are below.
  • A successor. Microsoft describes Microsoft Entra Cloud Sync as its strategic direction and says Connect Sync will be retired once Cloud Sync reaches full functional parity. There is no global retirement date, but Microsoft is notifying eligible tenants of Cloud Sync migration deadlines in waves.

This guide covers what Connect Sync does, how it differs from Cloud Sync, the deadlines and requirements that apply in 2026 and 2027, and the practices that keep a sync server healthy.

Deadlines and Supported Versions (2026–2027)

Connect Sync now runs on a fixed support clock. Each 2.x version retires 12 months after a newer version is released, all 1.x versions are unsupported and no longer synchronize, and the April 7, 2027 deadline applies to every server regardless of version. The table lists the dates published in Microsoft’s version history as of November 2026.

ItemDate or ruleWhat it means
Version 1.xUnsupportedSynchronization no longer works. Upgrade or migrate.
Version 2.5.79.0Support ended October 23, 2026Upgrade now.
Version 2.5.190.0Support ends February 2, 2027Plan the upgrade this quarter.
Version 2.6.1.0Support ends March 10, 2027Plan the upgrade this quarter.
2.6.84.0 or later, with application-based authenticationRequired by April 7, 2027Servers that haven’t made both changes stop synchronizing.
Version 2.6.3.0Support ends July 7, 2027Still below the April 2027 minimum.
Version 2.6.84.0Support ends September 16, 2027Meets the April deadline but retires months later.
Latest release2.6.92.0 (September 23, 2026)Security fixes; Microsoft recommends upgrading as soon as possible.

How to meet the April 7, 2027 deadline

  1. Check the version on every Connect Sync server, including staging servers.
  2. Upgrade to 2.6.92.0 rather than the 2.6.84.0 minimum. The installer is available only from the Microsoft Entra admin center. Version 2.6.84.0 can fail to install over an existing ADSync database (error 0xE0474352), which Microsoft fixed in 2.6.91.0.
  3. Confirm application-based authentication. Microsoft sets it up during new installations and manual interactive upgrades. If it wasn’t configured, open the Connect wizard and choose Additional tasks > Configure application-based authentication to Microsoft Entra ID (Microsoft’s instructions).
  4. Repeat on every staging server so a failover doesn’t bring back an unsupported configuration.

Automatic upgrade covers only part of the installed base. According to Microsoft’s automatic upgrade documentation, it is on by default only for Express installations that use the built-in LocalDB database, the default service account and fewer than 100,000 objects in the metaverse. A custom installation, a full SQL Server database, a LocalDB file of 8 GB or more, or TLS below 1.2 blocks it, and not every release is offered through automatic upgrade. If any of those apply, upgrade by hand.

Microsoft Entra Connect Sync vs. Cloud Sync

Connect Sync runs the whole synchronization engine on your own server; Cloud Sync runs it in Microsoft’s cloud and needs only lightweight provisioning agents on-premises. Microsoft calls Cloud Sync its strategic direction and says new synchronization features are built primarily there, but Connect Sync still handles some scenarios Cloud Sync doesn’t. The comparison below follows Microsoft’s Connect Sync to Cloud Sync decision guide (updated October 2026).

CapabilityConnect SyncCloud Sync
Where the sync engine runsYour Windows serverMicrosoft’s cloud, with agents on-premises
Objects per AD domainNo published limit150,000
Members per synced group250,00050,000
Advanced custom sync rulesYesNo
Cross-forest references and merging attributes from several domainsYesNo
Device sync for Microsoft Entra hybrid joinYesYes (enabled separately)
Device writebackYesNo (discontinued in favor of Cloud Kerberos Trust)
Pass-through authentication and AD FS setupYesNo
Disconnected forests (no trust between them)NoYes
Several active instances for availabilityNo (one active server plus staging servers)Yes (multiple agents)
Group provisioning to AD; on-demand provisioningNoYes

Stay on Connect Sync for now if you depend on custom sync rules, cross-forest references, device writeback, pass-through authentication, very large groups or more than 150,000 objects in a domain. Move to Cloud Sync if none of those apply, or if you need to sync disconnected forests, for example after an acquisition.

Since version 2.6.91.0, Connect Sync includes a guided migration workflow to Cloud Sync. The option appears only for tenants in the current migration wave, and Microsoft limits the guided tool to one forest with no more than 2,000 objects in scope and no more than 30 included organizational units per domain. Custom sync rules, group filtering, a custom user principal name and directory extensions block it; larger or customized environments migrate manually. Migration deadlines arrive in a notice to each tenant. If a blocker prevents you from meeting yours, Microsoft asks you to open a support request for a temporary exception, which isn’t guaranteed. See the migration documentation.

Microsoft Entra Connect Sync Architecture and Concepts

Connect Sync moves data in three stages: it imports objects from each connected directory into a local staging area, combines them into one identity record per person or group, then exports the result to Microsoft Entra ID. By default the scheduler runs a sync cycle every 30 minutes; if you change the schedule, a cycle must still run at least once every seven days. Microsoft’s architecture overview defines the parts below.

Connector

A connector is the module that handles all communication with one connected data source, such as an Active Directory forest or the Microsoft Entra tenant. A typical deployment has one connector per forest plus one for Microsoft Entra ID. Each connector decides which objects and attributes it reads and writes.

Connector Space

The connector space is a staging area holding a representation of the objects the connector reads from its data source, along with pending changes. Each connector has its own. Keeping a copy here lets the engine compare what changed since the last run and send only the differences. Don’t confuse it with staging mode, which is a separate idea described under best practices.

Metaverse

The metaverse holds the combined identity information from all connected sources. When the same person appears in two forests, the metaverse joins those records into one object, and sync rules decide which source wins for each attribute.

Sync Rules and Attribute Flow

Sync rules control which objects enter the metaverse, how records from different sources are joined, and how attributes flow and are transformed on the way in and out. Connect Sync ships with default rules that cover most deployments. Custom rules give you full control but are exactly what makes a later move to Cloud Sync harder, so document every custom rule you add.

Filtering and Provisioning

Filtering limits sync to chosen domains, organizational units, groups or attribute values. Provisioning is the export side: creating, updating and deleting users and groups in Microsoft Entra ID so they match the source directory, including removing cloud accounts when the on-premises account is deleted or moved out of scope.

Sign-In Methods: Password Hash Sync, Pass-Through Authentication and Federation

Connect Sync can configure three ways for synced users to sign in to Microsoft Entra ID. Microsoft’s guidance on choosing an authentication method is to enable password hash synchronization whichever method you pick, so it is already in place if you need to fall back to it.

MethodWhere the password is checkedOn-premises dependency
Password hash synchronization (PHS)Microsoft Entra ID, against a hash of the password hash (synced about every two minutes)None at sign-in time
Pass-through authentication (PTA)Your domain controllers, through lightweight agentsAgents and domain controllers must be reachable
Federation (for example AD FS)Your federation serversFederation farm must be available

Server Requirements

Microsoft’s prerequisites page lists these requirements for current versions:

  • A domain-joined Windows Server; Microsoft recommends Windows Server 2025 or 2022. Server Core isn’t supported.
  • A writable domain controller; read-only domain controllers aren’t supported.
  • TLS 1.2 enabled. Installation fails without it.
  • .NET Framework 4.7.2 or later and PowerShell 5.0.
  • A database. The bundled SQL Server Express LocalDB has a 10 GB limit, which Microsoft puts at roughly 100,000 objects. Larger environments need a full SQL Server instance.

Microsoft Entra Connect Sync Limitations

Connect Sync’s main limitations are operational: one active server at a time, an on-premises server to patch and upgrade on Microsoft’s schedule, and custom configuration that ties you to it. The specific constraints:

  • No active-active setup. Only one server exports at a time. Microsoft supports staging servers, rebuild-on-failure and virtual machine recovery for continuity, plus SQL Always On availability groups or clustering for the database, but not SQL mirroring.
  • Mandatory upgrade cadence. With 12-month version retirement and the April 2027 deadline, a server you don’t maintain eventually stops syncing.
  • Directory object limits. Microsoft Entra ID allows 50,000 objects per tenant by default, or 300,000 once you verify a domain. Groups synced through Connect Sync are limited to 250,000 members (service limits).
  • Customization costs later. Custom sync rules, attribute filters and cross-forest joins are often configured in the Synchronization Rules Editor or PowerShell, are hard to audit, and block the guided migration to Cloud Sync.
  • Monitoring needs a license. Connect Sync is free, but Microsoft Entra Connect Health, which provides sync error alerts and performance monitoring, requires Microsoft Entra ID P1. See our guide to Microsoft Entra pricing.
  • Workforce identity only. Connect Sync syncs your employees’ directory to Microsoft’s cloud. It doesn’t manage sign-in or accounts for the customers of an application you build; that is the job of a customer identity (CIAM) platform.

Microsoft Entra Connect Sync Best Practices

The goal is a sync server that stays supported, can be recovered quickly, runs with least privilege and is documented well enough to migrate later.

Upgrade on a Schedule, Not on a Deadline

Check the version history each quarter and keep every server within the support window. Before April 7, 2027, confirm each server runs 2.6.84.0 or later and has application-based authentication configured, including staging servers.

Keep a Staging-Mode Server

A staging-mode server imports and synchronizes like the active server but exports nothing, and it doesn’t run password sync or writeback. It gives you a warm standby you can switch to if the active server fails, and a safe place to test configuration changes and upgrades.

Use Least-Privilege Service Accounts

Let the installer create the default service accounts unless you have a reason not to, and grant the AD connector account only the permissions the features you enable require. Treat the Connect Sync server as a tier-0 asset, with the same protection as a domain controller, because it can change identities in both directories.

Document and Review Sync Rules

Export your configuration after every change and keep a list of custom rules, filters and the reason for each. Review it at least yearly. That list is also your migration inventory: anything on it that Cloud Sync doesn’t support decides whether you can move.

Filter Deliberately

Sync only the organizational units and groups that need cloud access. Smaller scope means fewer objects against tenant limits, fewer sync errors and less exposed data. Test filter changes on a staging server first, because removing objects from scope deletes the matching cloud accounts.

Monitor Sync Health

Watch for export errors, duplicate attribute conflicts and cycles that stop running. If you have Microsoft Entra ID P1, enable Connect Health alerts; otherwise check the Synchronization Service Manager and event logs on a schedule.

Selling SaaS to Companies That Run Entra ID

Connect Sync solves an internal problem: getting your own employees’ Active Directory accounts into Microsoft Entra ID. If you build a B2B SaaS product, your enterprise customers have usually solved that problem already, and their next question is how their Entra ID users sign in to your product and get removed from it when they leave.

That is customer identity, and it is what Frontegg handles. According to Frontegg’s SSO documentation, each of your customers’ admins configures their own SAML or OIDC connection through Frontegg’s self-service admin portal, and Microsoft Entra ID is among the identity providers listed in the SAML setup guide. Users are routed to their company’s identity provider by email domain once the customer verifies the domain with a DNS TXT record. Admins can also set up SCIM provisioning from Entra ID, so users are created and deprovisioned in your product automatically. See our guides to Azure AD (Entra ID) SSO and user management for more.

START FOR FREE

Looking to take your User Management to the next level?
Sign up. It's free