Before you start
- An on-premises Active Directory in good shape (see Windows Server 2025, first settings)
- A Microsoft 365 or Entra ID tenant and a public domain name whose DNS you manage
- Global Administrator rights on the tenant and Enterprise Admin rights on AD
In plain words
Many organisations have two directories: the on-premises Active Directory, on their servers, which handles Windows sign-ins, shares and printers; and Entra ID (formerly Azure AD), in Microsoft's cloud, which handles access to Microsoft 365 (Outlook, Teams, OneDrive). Hybrid identity links the two so that each person has a single account and a single password everywhere. It's like a company with two buildings: rather than issuing two badges per employee, you link both access control systems to a single staff register.
Information checked on 25 October 2026 against Microsoft's documentation.
1. The vocabulary
| Term | Meaning |
|---|---|
| Tenant | Your "space" at Microsoft: an Entra ID instance holding your users, groups, licences and settings. Created at the first Microsoft 365 or Azure subscription |
| Entra ID | The directory and identity service in Microsoft's cloud (formerly Azure Active Directory) |
| Active Directory (AD DS) | The on-premises directory, hosted on your Windows Server domain controllers |
| Synchronisation | Automatically copying accounts and groups from AD to Entra ID |
| Source of authority | The directory where an object is created and modified; in classic hybrid, it's on-premises AD |
| UPN | The sign-in name in email format: spo@example.com |
| Hybrid join | A PC joined to on-premises AD and also registered in Entra ID |
| Azure Arc | The service that lets you manage on-premises servers from the Azure portal |
2. The three identity models
| Model | Principle | For whom |
|---|---|---|
| Cloud only | Accounts exist only in Entra ID; PCs are joined to Entra ID and managed by Intune | Small organisations without a local server, new businesses |
| Hybrid | Accounts are created in on-premises AD and synchronised to Entra ID | Most organisations that already have AD and on-premises applications |
| On-premises only | No Microsoft cloud | Isolated environments, or no Microsoft 365 |
Hybrid is often a stage: you keep AD for whatever still depends on it (shares, applications, printers), and move progressively to the cloud.
3. Synchronising identities: Connect Sync or Cloud Sync
Microsoft offers two tools that copy accounts from AD to Entra ID:
| Entra Connect Sync | Entra Cloud Sync | |
|---|---|---|
| Architecture | An on-premises server that does all the work, with its database | Lightweight on-premises agents; configuration and processing are in the cloud |
| High availability | No: if the server goes down, synchronisation stops (a standby server in staging mode is possible) | Yes: several active agents take over from each other |
| Updates | Up to you | Automatic |
| Disconnected AD forests (merger, acquisition) | No | Yes |
| Very large directories | No limit | Up to 150,000 objects per domain |
| Very large groups | Up to 250,000 members | Up to 50,000 members |
| Advanced synchronisation rules | Yes | No (simpler expression builder) |
| Configuring AD FS federation and pass-through authentication (PTA) | Yes | No: separate tools, but PTA and SSO keep working after migration |
| Syncing computers for hybrid join | Yes | Yes (to be turned on separately) |
| Device writeback to AD (legacy certificate-based Windows Hello for Business) | Yes | No: replaced by cloud Kerberos trust |
| Provisioning groups from the cloud to AD | No | Yes |
Microsoft is organising the move to Cloud Sync
In April 2026, Microsoft announced the gradual transition from Entra Connect Sync to Entra Cloud Sync. Organisations have been notified individually since July 2026 (Microsoft 365 message centre, Entra Connect Health, emails), starting with those whose configuration is fully covered by Cloud Sync; large directories and advanced configurations move later. New synchronisation features are developed for Cloud Sync first. For a new deployment, go with Cloud Sync if it covers your needs; otherwise, install Connect Sync and prepare the migration.
To migrate an existing server, Microsoft provides a guided migration tool, run from the active Connect Sync server: it assesses the environment, creates the Cloud Sync configuration, tests it on one object (on-demand provisioning), then switches Connect Sync to staging mode. Keep Connect Sync installed during the planned two-week validation period. Follow the date given in your tenant's own notification; if you are genuinely blocked, an extension can be requested from support.
What to prepare before synchronising
| Step | Why |
|---|---|
| Verify your public domain in the tenant (TXT record in DNS) | UPNs must use a verified domain, for example example.com |
| Add this UPN suffix in AD (Active Directory Domains and Trusts console) and apply it to the accounts | An AD in .local or .lan isn't routable: without this, accounts arrive as @tenant.onmicrosoft.com |
| Clean up the directory with Microsoft's IdFix tool | Duplicates, forbidden characters and malformed addresses block synchronisation |
| Limit the scope to certain organisational units (OUs) | Sync only real users and groups, not service accounts or administration accounts |
| Don't sync AD administrator accounts | A cloud administrator account must be a cloud-only account, and vice versa |
Check and change UPNs in PowerShell (Active Directory module):
$OU = "OU=Users,DC=company,DC=local"
# Show the current UPNs
Get-ADUser -Filter * -SearchBase $OU |
Select-Object SamAccountName, UserPrincipalName
# Move them to the verified domain
Get-ADUser -Filter * -SearchBase $OU | ForEach-Object {
Set-ADUser $_ -UserPrincipalName ($_.SamAccountName + "@example.com")
}
Test on a pilot OU first. If the email address differs from the SamAccountName, build the UPN from the mail attribute: ideally, the UPN should be identical to the email address.
4. Choosing the authentication method
| Password hash synchronisation (PHS) | Pass-through authentication (PTA) | Federation (AD FS) | |
|---|---|---|---|
| Where the password is checked | In the cloud, from a derivative of the synchronised hash | By an on-premises agent, which queries AD | On your AD FS servers |
| Extra on-premises infrastructure | None | 3 agents recommended for redundancy | AD FS farm and proxy servers in a DMZ, certificates |
| Works if the on-premises site goes down | Yes | No | No |
| Leaked credentials detection (Entra ID P2) | Yes | Only if PHS is also turned on | Only if PHS is also turned on |
| Enforces AD logon hours and lockout in real time | Partly (disabled account: up to 30 minutes' delay) | Yes | Yes |
| Complexity | Low | Medium | High |
Microsoft's recommendation: PHS
Microsoft recommends password hash synchronisation, with Seamless single sign-on (Seamless SSO) or Entra ID-joined workstations. Even if you use PTA or federation, turn on PHS as a fallback: in ransomware attacks that took on-premises AD offline, organisations that had it turned on got their Microsoft 365 email back within hours; the others took weeks.
The password is not copied as is: only a derivative of its hash, itself hashed again, is sent. New organisations generally no longer need AD FS; Microsoft provides a guide for migrating from federation to cloud authentication.
5. Workstations
| PC state | What it means | Management |
|---|---|---|
| AD-joined only | Sign-in through AD, Group Policy (GPO) | GPO, on-premises tools |
| Hybrid-joined (AD + Entra ID) | The PC is known to both directories: single sign-on to Microsoft 365, device-based conditional access | GPO and Intune (co-management) |
| Entra ID-joined only | No more dependence on the local domain; access to on-premises shares remains possible through Kerberos | Intune |
Hybrid join is the natural transition for an existing fleet. For new workstations, Microsoft steers towards direct Entra ID join with Windows Autopilot and Intune; see MDM: managing computers, phones and tablets.
6. Email: Exchange hybrid
If email is still on an on-premises Exchange Server, an Exchange hybrid deployment allows coexistence with Exchange Online during the migration: shared address book, shared calendars, gradual mailbox moves. Microsoft provides the Hybrid Configuration Wizard.
Exchange 2016 and 2019 have been unsupported since 14 October 2025: organisations keeping on-premises email must move to Exchange Server Subscription Edition (SE); most choose to finish migrating to Exchange Online.
The "last Exchange server". For a long time, even after all mailboxes had been migrated, you had to keep an Exchange server (or its management tools) to modify the mail attributes of synchronised accounts. That's no longer mandatory: you can now move management of Exchange attributes to the cloud, mailbox by mailbox (Set-Mailbox -Identity <user> -IsExchangeCloudManaged $true in Exchange Online PowerShell), then uninstall the last server following Microsoft's procedure. Identity (name, password, groups) is still managed in on-premises AD.
Three precautions from Microsoft
- After moving a mailbox to Exchange Online, wait one synchronisation cycle plus 24 hours before switching its attributes to the cloud; otherwise old values can overwrite the correct ones in AD.
- The tenant-wide setting (
Set-OrganizationConfig -ExchangeAttributesCloudManagedByDefault) should only be turned on once all mailboxes have been migrated and no more mailboxes are created in on-premises Exchange: turning it on earlier isn't supported and blocks migration of the remaining mailboxes. - Distribution lists and contacts aren't covered by this setting: to manage them after Exchange is removed, you need to transfer their management (source of authority) to Entra ID.
7. Azure Arc: managing on-premises servers from Azure
Azure Arc installs an agent (Connected Machine agent) on your Windows or Linux servers, whether physical, virtual or at another provider. They then appear in the Azure portal as if they were hosted there.
| Feature | Benefit |
|---|---|
| Inventory and tags | A single view of all servers |
| Azure Update Manager | Schedule and track updates for all servers |
| Hotpatch for Windows Server 2025 | Fewer restarts for monthly patches (subscription required) |
| Extended Security Updates (ESU) | Paid patches for some end-of-life versions |
| Microsoft Defender for Cloud, machine configuration | Centralised security and compliance |
| Windows Admin Center in the Azure portal | Administer an on-premises server from the browser |
Some features are included, others are billed by usage: check the details before turning them on. Azure Arc doesn't move any data: the servers stay on your premises.
8. The licences to know
| Feature | Licence required |
|---|---|
| Synchronisation, single sign-on, basic two-factor authentication | Included in Entra ID (and Microsoft 365) |
| Conditional Access, password writeback (SSPR with writeback to AD), dynamic groups | Entra ID P1 (included in Microsoft 365 Business Premium, E3, E5) |
| Identity Protection (sign-in risk, leaked credentials), PIM (just-in-time roles) | Entra ID P2 (included in E5) |
| Workstation management with Intune | Included in Microsoft 365 Business Premium, E3, E5 |
9. A step-by-step deployment plan
- Inventory: accounts, groups, OUs, service accounts, applications that use AD, Exchange status.
- Preparation: verified domain in the tenant, UPN suffix, clean-up with IdFix, choice of OUs to sync.
- Cloud administration accounts: two cloud-only emergency access (break glass) accounts, and named administration accounts, protected by phishing-resistant two-factor authentication (see Two-factor authentication, passkeys and FIDO2 keys).
- Pilot synchronisation: a test OU, PHS turned on, check in the Entra admin centre.
- Two-factor authentication for everyone, then Conditional Access (see Conditional Access and access governance).
- Roll-out of synchronisation, then of Microsoft 365 licences.
- Workstations: hybrid join, then co-management with Intune.
- Email: Exchange hybrid and mailbox migration, if needed.
- Monitoring: Entra Connect Health, sign-in logs, alerts.
The domain controller remains the main target
Hybrid identity links your AD to the cloud: an attacker who takes control of AD (or of the synchronisation server) can also reach Microsoft 365. Treat the Entra Connect Sync server like a domain controller (highest administration tier), don't sync privileged accounts, and protect cloud accounts with strong two-factor authentication.
Key points
- Hybrid identity links on-premises AD and Entra ID for a single account; AD remains the source of authority.
- Cloud Sync is the future (transition organised by Microsoft since 2026); Connect Sync is still needed for advanced scenarios.
- PHS is recommended, and turned on as a fallback even with PTA or AD FS.
- Prepare UPNs on a verified domain, clean up with IdFix, and don't sync privileged accounts.
- Azure Arc manages on-premises servers from Azure; Conditional Access requires Entra ID P1.
Sources
- Microsoft: choose the right authentication method for your hybrid identity solution
- Microsoft: synchronisation tools and hybrid scenarios
- Microsoft: decision guide from Entra Connect to Cloud Sync
- Microsoft: what's new in Entra (transition to Cloud Sync, April 2026)
- Microsoft: Microsoft Entra hybrid join
- Microsoft: Azure Arc-enabled servers
- Microsoft: manage Exchange attributes from the cloud in a hybrid environment
- Microsoft: decommission the last Exchange server
- Microsoft: migrate to Cloud Sync with the guided migration tool