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.


