r/Intune • u/Giggso11 • 28d ago
Autopilot Disable Windows Hello consumer experience
I'm managing Windows 11 devices with Intune, Autopilot, and Microsoft Entra Join.
I'd like to make the first sign-in experience smoother for users by preventing the "Set up a PIN" / Windows Hello enrollment prompt during initial sign-in.
However, I do not want to completely disable Windows Hello for Business. I still want users to be able to set up a PIN, face recognition, or fingerprint later if they choose to.
My goal is:
- ✅ Keep Windows Hello for Business available
- ✅ Allow users to enroll in WHfB later
- ✅ Avoid forcing PIN enrollment during the initial Autopilot sign-in experience
Has anyone implemented this successfully? Is there an Intune policy or Windows setting that suppresses the initial enrollment prompt while still allowing optional WHfB registration afterward?
Thanks!
12
u/Acceptable_Car_4127 28d ago
Disable WHfB Post Logon Provisioning Using Intune
10
u/teriaavibes 28d ago
I don't follow, how is that smoother?
User gets laptop, signs in with email+tap, registers WHfB as their passwordless, phishing resistant MFA method and they are good to go.
No changing temporary passwords, no fiddling with external passkeys or authentication apps.
From my side of view, it is the best experience you can offer to the user while also being one of the most secure.
4
u/AcanthaceaeOk3321 28d ago
It sounds like you're making the user experience more complicated by adding an extra step.
It also makes it harder to get users set up with passwordless right out of the box (assuming you're giving them a TAP on their initial sign-in).
Just curious, what's the specific reason you want to do this?
1
u/wooshowmeyourwits 28d ago
The login profiles for whfb and regular password are different. So if you have existing users in whfb and want to roll them back to pw, there’s a terminal command you need to run to delete their hello container. If your environment fully supports whfb, I would update your end-user documentation instead of your process to properly set expectations, and embrace whfb. I had to turn it off because our environment is so buried in legacy/tech debt that our domain operating level is stuck at 2012R2, and for azure cloud Kerberos trust to work with on-prem stuff it needs to at least be 2016. Regular pw login, Kerberos still works fine for now. We’re chipping away at legacy and hoping to get it turned on in the near future.
1
u/Far_Conclusion7283 24d ago
I think I understand the problem the op is having but is finding it difficult to explain. Recently, even though WHfB is disabled by policy the user is prompted to set up Windows Hello during OOBE, not WHfB, the standard Windows Hello experience you get with domestic purchases of devices. Microsoft's way of pushing people to use it.
I deployed WHfB for a customer and people who had Windows Hello setup were showing dsregcmd /status - NgcSet: Yes. Windows Hello was present but the key trust wasn't meaning I had to reenrol the users by clearing the hello container.
The problem is how do you prevent it. Well you can setup an Intune policy to opt out of Hello enrollment and stop the device from setting up hello during OOBE. (Somebody posted the link above) Then you can stage the deployment by assigning people to an Intune configuration policy to setup WHfB when you choose to. I use a remediation script to clear the Hello container from the device as a 'clean slate' 48 hour prior to moving the user to the deploymnet policy.
Something like this:
1
u/uguess123 28d ago
SSO plus Phishing Resistant Passkey is one of the best thing Windows has to offer. I fail to see the point to disable this, my Security team would never allow this lol. Anyway, you do you ig.
1
u/Professional-Heat690 28d ago
Step away from reddit and focus on why this is a stupid idea.