An Intune configuration profile showing Succeeded is comforting. It is also answering a much smaller question than most people think.
It proves that policy reached the device. It does not prove that the signed-in user completed Windows Hello for Business provisioning, that a key exists on that device, or that Microsoft Entra ID has the matching public key.
That gap matters during a passwordless rollout. A dashboard can look healthy while users keep signing in with passwords, a prerequisite silently blocks enrollment, or Group Policy overrides the setting that Intune says it delivered.
Windows Hello for Business is ready only when the evidence forms a complete chain:
- The correct policy is assigned and applied.
- The user and device pass the provisioning prerequisites.
- A Windows Hello key exists for that user on that device.
- The corresponding authentication method is registered in Microsoft Entra ID.
Anything less is progress, not proof.
Policy delivery is the first checkpoint
Windows Hello for Business can be configured in Intune through the tenant-wide enrollment setting or through targeted policy such as the Settings catalog and Account protection.
The difference is operationally important. The tenant-wide setting under Devices > Windows > Windows Enrollment > Windows Hello for Business applies when a device enrolls. Changing it later does not update devices that are already enrolled. A targeted device configuration policy applies after enrollment and can update during normal policy refresh.
That makes the tenant-wide setting a poor place to look when troubleshooting a device that enrolled months ago. The value visible in the portal today is not necessarily the value that device received at enrollment.
Policy source matters too. Windows Hello settings delivered through Intune use the PassportForWork CSP. If the same settings also arrive through Group Policy, the GPO settings take precedence. MDMWinsOverGP does not rescue the Intune configuration because that control applies to the Policy CSP, not PassportForWork.
The practical rule is simple: avoid managing Windows Hello for Business through both GPO and CSP. A successful Intune status beside an overriding GPO is still a conflict.
Provisioning belongs to the user
Windows Hello for Business is not finished when the device receives policy. Provisioning occurs for a user after sign-in, and every prerequisite must pass before the enrollment experience starts.
The checks include whether:
- The device is Microsoft Entra joined or Microsoft Entra hybrid joined.
- The user signed in with an organizational account.
- Windows Hello for Business policy is enabled.
- The device meets the hardware requirements.
- The session is local rather than Remote Desktop.
- The required authentication and deployment-specific prerequisites are available.
The user then completes multifactor authentication and creates a PIN. Biometrics can be added when supported, but the PIN remains the fallback gesture. Provisioning creates an asymmetric key pair for that user and device; the private key stays protected on the device and the public key is registered with the identity provider.
That is why checking only the device is incomplete. Two people can use the same computer and have different Windows Hello states. One can be fully provisioned while the other has never seen the prompt.
The local proof: dsregcmd /status
On the endpoint, run the following command from the signed-in user’s normal session:
dsregcmd /status
Do not elevate the prompt for this check. The User State section is tied to the current user’s context, and Microsoft notes that user-state values can be invalid or show errors when the command runs elevated.
The two fields that answer the immediate question are:
NgcSet : YES
NgcKeyId : {key-guid}
NgcSet : YES means a Windows Hello key is set for the logged-in user. NgcKeyId identifies that key. Together, they prove that this user has a Hello credential on this device.
Other fields help explain why provisioning did not happen. AzureAdPrt : YES confirms that the current user has a Microsoft Entra primary refresh token. When Windows exposes the NGC Prerequisites Check, values such as IsDeviceJoined, IsUserAzureAD, PolicyEnabled, DeviceEligible, and SessionIsNotRemote show which gate passed or failed. A PreReqResult of Will Provision means the platform expects to launch enrollment at the next sign-in.
dsregcmd is excellent local evidence, but it has a narrow scope: the current user on the current device. It is not a fleet report.
When no key exists, read the prerequisite decision
If NgcSet is NO or the user was never prompted, the useful question is not “did the Intune policy sync?” It is “which provisioning prerequisite failed?”
Open Event Viewer and go to:
Applications and Services Logs
> Microsoft
> Windows
> User Device Registration
> Admin
The Windows Hello provisioning events record the prerequisite evaluation. They can show that policy was enabled while another requirement—device join, user authentication, hardware eligibility, a local session, or a deployment-specific trust check—prevented enrollment from launching.
The PassportForWork policy keys can separately confirm that policy arrived. They cannot prove that the user created a credential. That distinction keeps the investigation in order:
- Intune status and PassportForWork state answer was policy delivered?
- User Device Registration events answer why did provisioning start or stop?
NgcSetandNgcKeyIdanswer does this user have a local key?
Each signal closes a different part of the chain.
The tenant proof: reporting and Microsoft Graph
Once one device is working, the question changes from “did this user provision?” to “who across the tenant has actually registered Windows Hello?”
The Microsoft Entra authentication methods activity report is the quickest portal view. Its user registration details can show Windows Hello for Business among a user’s registered methods, with no script required. It is useful for rollout tracking, but it is not real-time: Microsoft documents reporting latency of up to 36 hours.
For key-level inventory, Microsoft Graph exposes each user’s registered Windows Hello for Business methods:
GET /users/{id-or-userPrincipalName}/authentication/windowsHelloForBusinessMethods
The response includes the device display name, key strength, creation time, optional last-used time, and the authentication-method ID. For application access, the least-privileged permission documented for this operation is:
UserAuthMethod-WindowsHello.Read.All
The endpoint is user-scoped, so a tenant-wide inventory means listing users and querying the methods for each one. The method is also documented under the Microsoft Graph beta endpoint at the time of writing. That makes it useful for verification and controlled reporting, but it deserves the usual beta warning before becoming a production dependency.
Graph closes the cloud side of the evidence chain. Match the returned device display name and key details to the user and endpoint you verified locally. A local NgcKeyId without a corresponding cloud registration—or a stale cloud method for a device that no longer exists—is something to investigate, not count as a successful rollout.
What each signal actually proves
| Signal | What it proves | What it does not prove |
|---|---|---|
| Intune policy status | The configuration was delivered and processed | The user completed provisioning |
| PassportForWork policy state | Windows received the relevant policy values | A Hello key exists |
| User Device Registration events | Which provisioning prerequisites passed or failed | Tenant-wide adoption |
NgcSet and NgcKeyId |
The current user has a key on this device | Every user or device is ready |
| Entra authentication methods report | A user is reported as registered for Hello | Immediate, device-level detail |
| Microsoft Graph method list | The user’s registered keys and associated device details | That the current local key is healthy without endpoint evidence |
No single green indicator proves the whole system. The verification becomes reliable when the signals agree.
A rollout check that scales
For a pilot, I would use the same sequence every time:
- Confirm the intended Intune policy and make sure GPO is not overriding it.
- Sign in locally as the pilot user and complete provisioning.
- Run
dsregcmd /statusin that user’s non-elevated session. - If no key exists, read the User Device Registration admin log before changing policy.
- Confirm the user’s Windows Hello registration in the Entra report or Microsoft Graph.
- Record the user, device, local key state, cloud registration, and verification time.
That turns “the profile succeeded” into evidence an MSP can put on a ticket and defend later.
The one-page reference
The visual checklist for configuring, provisioning, and verifying Windows Hello for Business is in the knowledge base:
→ Windows Hello for Business Verification — part of my MSP Microsoft 365 knowledge base on GitHub.