Hybrid Identity and External Users: Microsoft Entra Connect, Password Hash Sync, Federation, B2B and External ID
Why Hybrid Identity?
Most companies already have Active Directory on-premises. Employees should use one identity for both on-premises and cloud apps. Hybrid identity synchronizes on-premises users to Microsoft Entra ID.
text
On-premises AD ──► Microsoft Entra Connect (or Cloud Sync) ──► Microsoft Entra ID ──► Microsoft 365, Azure, SaaS apps
users, groups, password hash (optional)
Sync Tools
| Tool | Notes |
|---|---|
| Microsoft Entra Connect Sync | Full-featured agent on a server. Supports complex forests, filtering, device writeback |
| Microsoft Entra Cloud Sync | Lightweight agents managed from the cloud, good for multi-forest and simple setups |
Sign-In Methods
| Method | How it works | Pros | Cons |
|---|---|---|---|
| Password hash sync (PHS) | A hash of the hash of the password syncs to Entra ID. Entra validates sign-ins | Simple, works even if on-premises is down, enables leaked-credential detection | Passwords validated in cloud |
| Pass-through authentication (PTA) | Sign-in is checked on-premises by agents | No hashes in cloud, enforces on-premises policies instantly | Needs agents online and reachable |
| Federation (AD FS) | Sign-in is redirected to your AD FS servers | Smart cards, special claims | Complex, more servers, single point of failure |
Microsoft's usual advice Use password hash sync (optionally with seamless SSO) unless you have a firm reason for PTA or federation. Keep PHS as a backup even with other methods.
Seamless SSO and Device Join
- Seamless SSO: users on domain-joined devices are signed in without typing the password again
- Hybrid Entra join: a device is joined to AD and registered in Entra ID. Entra join: cloud-only device management with Intune
Planning Checklist
- Clean up AD first: fix UPN suffixes, remove duplicates, check attributes
- Add and verify your custom domain
- Choose a sign-in method
- Use filtering to sync only needed OUs and groups
- Install Entra Connect on a dedicated server and add a staging server for failover
- Turn on health monitoring (Entra Connect Health)
- Do not sync highly privileged on-premises admin accounts to the cloud admin roles
External Users
| Scenario | Solution |
|---|---|
| Partners and contractors use your apps | Entra B2B collaboration: invite guests, they sign in with their own identity (work account, Microsoft account, Google, one-time passcode) |
| Customers sign up and sign in to your consumer apps | Microsoft Entra External ID (successor to Azure AD B2C for new customers): branded sign-up, social logins, custom flows |
| Cross-tenant trust | Cross-tenant access settings and B2B direct connect |
bash
az rest --method post --url https://graph.microsoft.com/v1.0/invitations \
--body '{"invitedUserEmailAddress":"partner@fabrikam.com","inviteRedirectUrl":"https://myapps.microsoft.com","sendInvitationMessage":true}'
- Control guests with Conditional Access, access reviews and entitlement management (access packages)
- Restrict who can invite and which domains are allowed
Practice
- Choose a sign-in method for: a small company, a bank with strict on-premises policy, a firm that uses smart cards
- List five steps before installing Entra Connect
- Invite a guest user and give them access to one group
- Explain how B2B differs from External ID for customers
Conclusion
Hybrid identity syncs on-premises AD to Entra ID with Entra Connect or Cloud Sync. Password hash sync is the simple default, PTA and federation have special uses, and B2B and External ID handle partners and customers.
Quick Summary: why; sync tools; sign-in methods; SSO; checklist; external users.

