2.3.4. Windows Hello for Business
💡 First Principle: Windows Hello for Business replaces something you know and send (a password) with something you have and unlock (a private key on this device). The PIN or biometric gesture never travels anywhere; it only unlocks a key held by the device's TPM, and the key proves who you are. That's why a stolen PIN is useless away from the device, and why Hello satisfies multifactor authentication in Conditional Access.
The provisioning flow makes the model concrete: the user optionally enrolls a biometric, completes MFA, creates a PIN, Windows generates a key pair (in the TPM where possible), and the public key is registered with the identity provider. Authentication to Entra ID always uses that key. The credential is a user key bound to the device, so in hybrid environments both the user and the device objects must be synced.
Cloud-only deployments need almost no work: when you Entra join a device, Windows automatically attempts Hello enrollment with default settings. Intune is where you take control, in two places:
- The tenant-wide Windows Hello for Business policy at Devices > Enrollment > Windows tab > Windows Hello for Business applies at enrollment time to the whole organization, including during Autopilot. Only an Intune Service Administrator can edit it. Its main choices are Enabled, Disabled (users can't provision Hello) or Not configured (Intune leaves Hello alone); Use a TPM (Required by default, or Preferred with software fallback); and the PIN rules — length defaults to 6 characters, with a minimum of 4 and a maximum of 127, and lowercase, uppercase and special characters are Not allowed by default.
- Per-group, post-enrollment configuration uses the endpoint security Account protection profile (which in July 2024 replaced the deprecated Identity protection template and combines Hello with Credential Guard), security baselines, or the settings catalog. If the tenant-wide policy disabled Hello, you can re-enable it for a group with the settings catalog setting Use Windows Hello For Business.
Biometrics always keep a work PIN as fallback. If both a device-PIN configuration policy and a Hello policy apply, the Hello policy wins, because the device and work PINs merged long ago.
Hybrid environments add a trust type, which describes how the device authenticates to on-premises Active Directory (so it doesn't apply to cloud-only deployments):
| Trust type | PKI needed (hybrid) | When to choose it |
|---|---|---|
| Cloud Kerberos trust | No | Recommended default; uses Microsoft Entra Kerberos and has no key-sync delay |
| Key trust | Yes, domain controller certificates | Hybrid deployments already using it; can move to cloud Kerberos trust without reprovisioning |
| Certificate trust | Yes, and federation with AD FS | Only when certificate authentication scenarios require it; no direct migration path to cloud Kerberos trust |
Cloud Kerberos trust works on Entra joined and hybrid joined devices. You deploy Microsoft Entra Kerberos first (it creates an AzureADKerberos object in AD that looks like a read-only domain controller), then set Use Windows Hello For Business = true and Use Cloud Trust For On Prem Auth = Enabled in the settings catalog. If the tenant-wide policy already enables Hello, only the cloud trust setting is needed. Watch for conflicts: if Group Policy and Intune both configure Hello, Group Policy wins and Intune's settings are ignored. Members of privileged built-in AD groups can't use cloud Kerberos trust, and on a hybrid joined device the first PIN sign-in needs line of sight to a domain controller.
Licensing is a favorite distractor: Windows Hello for Business doesn't need Entra ID P1 or P2 (automatic MDM enrollment and Conditional Access do).
⚠️ Exam Trap: A Hello PIN is not a shorter password checked by a server, even though typing it looks identical. The PIN never leaves the device; it unlocks a TPM-protected private key, and the key — not the PIN — proves identity to Microsoft Entra ID. So "a four-digit PIN is weaker than a 14-character password" is the wrong analysis: someone who steals the PIN still needs the physical device.
Reflection Question: A hybrid organization wants Hello sign-in to on-premises file servers without building a PKI, but its Hello settings delivered from Intune never take effect on some desktops. Which trust type fits, and what is the most likely reason Intune's settings are being ignored?