Home→Blog→Azure AD Hybrid Identity Architecture: Synchronisa...
Azure Security

Azure AD Hybrid Identity Architecture: Synchronisation, Pass-Through Authentication, and Federation

Deep dive into hybrid identity patterns: Azure AD Connect vs Cloud Sync, password hash sync vs pass-through authentication vs federation, SSO capabilities, migration from on-premises AD to cloud, disaster recovery, and monitoring sync health.

Alpesh Nakar
Sep 4, 2025
4 min read
🇦🇺 Australian Context
📜 ACSC, Privacy Act

⚡TL;DR

  • •Hybrid identity keeps on-premises AD and cloud Entra ID in sync to provide single identity across both environments.
  • •Password Hash Sync (PHS) is simplest and resilient; Pass-Through Authentication (PTA) avoids cloud-stored hashes but requires on-prem infrastructure and has no failover.
  • •Cloud Sync is lightweight and agent-based; Azure AD Connect is mature and feature-rich—choose based on complexity and resilience needs.
  • •Enable Seamless SSO for domain-joined devices to remove daily password prompts; monitor sync health with Azure AD Connect Health.
  • •Plan migration path: hybrid short-term, phased move to cloud-only over 2-3 years with disaster recovery testing.

Why hybrid identity is the bridge between on-premises and cloud

Most Australian organisations don't migrate to cloud overnight—they evolve gradually, maintaining on-premises Active Directory infrastructure whilst progressively adopting Microsoft 365 and cloud services. This hybrid reality creates identity complexity: users maintained in on-premises AD must authenticate to cloud services, maintaining a single identity across on-premises and cloud resources. Hybrid identity architecture solves this: it synchronises on-premises AD users and groups to Entra ID, enabling seamless access to both on-premises and cloud resources with single sign-on (SSO). Getting hybrid identity right is foundational—misconfigurations cause widespread authentication failures, SSO breakage, and access control chaos. This article provides guidance on hybrid identity patterns, synchronisation strategies, and disaster recovery.

1) Hybrid identity architecture fundamentals

Source of truth concept

  • On-premises as source of truth: User accounts are created and maintained in on-premises AD. Information (names, email, phone, group membership) is replicated to Entra ID via synchronisation. Users cannot be created directly in Entra ID—they must originate from on-premises AD. Changes in on-premises AD are synchronised to Entra automatically.
  • Cloud-only model (no on-premises AD): Users created directly in Entra ID. No on-premises infrastructure required. Simpler for cloud-native organisations but limits hybrid access to legacy on-premises apps.
  • Most Australian organisations: Hybrid model—maintain on-premises AD investment whilst progressively migrating to cloud. Protects existing infrastructure investment, enables gradual cloud adoption, supports legacy on-premises applications indefinitely.

2) Azure AD Connect: Full synchronisation

How Azure AD Connect works

  • Deployment: Install Azure AD Connect server (Windows Server 2012 R2+) joined to on-premises AD domain. Server connects to on-premises AD on one side, Entra ID on cloud side.
  • Synchronisation engine: Bidirectional synchronisation of user objects, groups, contacts, and attributes. Runs on schedule (default: every 30 minutes). Detects changes in on-premises AD (new users, modified attributes, group membership changes) and pushes to Entra ID.
  • Password handling: Passwords are NOT synchronised. Instead, password hashes are one-way synchronised (cannot reverse hash to recover password). When user authenticates to cloud service, Entra validates password hash matches stored hash—enabling seamless cloud logon without password transmission.

Azure AD Connect authentication methods

  • Password Hash Synchronisation (PHS): On-premises password hash is synchronised to Entra. Cloud authentication validates against synchronised hash. Simplest deployment, no on-premises infrastructure required for cloud authentication. If on-premises connectivity lost, users can still authenticate to cloud services (failover capability). Slightly less secure than other methods (password hash can be captured in certain attack scenarios).
  • Pass-Through Authentication (PTA): Entra redirects authentication requests to on-premises agents. Agents validate password against on-premises AD. More secure (password never transmitted to cloud; on-premises AD validates). Requires internet connectivity to on-premises agents for cloud authentication (no failover if on-premises network down). Additional infrastructure (install agents on 2-3 on-premises servers).
  • Federation (ADFS): Active Directory Federation Services acts as identity broker. Entra redirects authentication to AD FS. AD FS authenticates against on-premises AD. Enables advanced authentication policies (certificate-based auth, sophisticated MFA). Most complex deployment—requires AD FS infrastructure, certificates, federation metadata management. Rarely chosen for new deployments due to complexity.

3) Azure AD Cloud Sync: Lightweight synchronisation

Cloud Sync vs Azure AD Connect

  • Cloud Sync advantages: Agent-based (install lightweight agent on domain-joined server, not dedicated sync server). Supports multi-forest synchronisation (multiple on-premises AD forests sync to single Entra tenant—useful for mergers/acquisitions). Easier to scale (deploy agents to multiple locations for resilience). Managed entirely in cloud (no on-premises sync database to maintain).
  • Azure AD Connect advantages: Longer history (mature product, industry standard). More granular synchronisation control (filtering, transformation rules). Advanced features (group writeback, device sync).
  • Migration path: Many organisations migrate from Azure AD Connect to Cloud Sync as infrastructure modernises. Both can coexist during transition (dual sync).

4) Single Sign-On (SSO) across on-premises and cloud

Seamless SSO concept

  • User experience: User logs into Windows 10/11 laptop (joined to on-premises AD). Windows caches Kerberos token. When user opens browser and accesses Microsoft 365, Entra recognises cached Kerberos token and automatically authenticates—no password prompt required.
  • Behind the scenes: Entra Connect issues Seamless SSO ticket (time-limited token). Browser uses ticket to authenticate to cloud services. No credential transmission required.
  • Scope: Seamless SSO works for Microsoft 365 cloud applications (Teams, SharePoint, Outlook web, etc.). On-premises applications using Windows authentication (Kerberos) also authenticate seamlessly.

Sources referenced in this article: Azure AD Connect, Cloud Sync, Password Hash Synchronisation, Pass-Through Authentication, AD FS, Privacy Act.

Assess Your Maturity

Understand where your organisation stands on the Essential Eight maturity model and identify priority controls.

Train Your Team

Hands-on Essential Eight fundamentals course for security teams, architects, and IT leaders.

Frequently Asked Questions

Questions security teams commonly ask about Essential Eight implementation.

Ready to Move from Level 1 to Level 2+?

Start your 12-month Essential Eight maturity journey with expert guidance and practical roadmaps.

Read Next

Continue exploring security insights and best practices

Azure Security
Sep 1, 2025
9 min read

Comprehensive guide to passwordless authentication implementation: Windows Hello for Business, FIDO2 security keys, Microsoft Authenticator, deployment planning, user enrolment, temporary access passes, phishing-resistant MFA for Essential Eight Level 3.

Process
May 2, 2026
11 min read

The named risks Australian programmes most often miss during a hybrid Active Directory to Microsoft Entra ID cutover — with likelihood, impact, and the mitigation each risk needs before go-live.

Technology
Apr 26, 2026
12 min read

An end-to-end walk-through for Australian organisations retiring on-premises Active Directory in favour of Microsoft Entra ID — what to keep, the order to retire AD Connect and ADFS, and the resilience controls that survive cutover.