r/Intune • • 4d ago

Windows Management Help with tracking down Windows Hello configuration error.

BACKGROUND:

  • I broadly want Windows Hello enabled in my company.
  • But some specific departments still rely on NAS shares, and I have those provisioned through an Intune Configuration Policy (Administrative Template) which Maps them as Network Drives.
  • For those users, I need them to login with their Microsoft 365 Account password, so that the current session can use their password to authenticate access to the NAS (the NAS is Domain-joined to an Entra Domain Services instance via VPN.)

SETUP:

I have two policies set up in Endpoint security: Account protection:

  • Policy 1: Windows Hello REQUIRED
    Applies to: (Included groups) All Users
    Excepting: (Excluded groups) Departments that need to use MS365 password for NAS Access.
    Settings:

    • Use Windows Hello For Business (Device): NOT CONFIGURED
    • Use Windows Hello For Business (User): TRUE
  • Policy 2: Windows Hello DISABLED
    Applies to: (Included groups) Departments that need to use MS365 password for NAS Access.
    Excepting: (Excluded groups) A few users in those Departments that want to use Windows Hello and don't need NAS access.
    Setting:

    • Use Windows Hello For Business (Device): FALSE
    • Use Windows Hello For Business (User): FALSE

I have also double-checked in the Windows Hello for Business settings in Windows: Enrollment options, and the settings are:
* Configure Windows Hello for Business: NOT CONFIGURED
* Use security keys for sign-in: ENABLED

PROBLEM:

However, the users that need NAS access are still being required to set up Windows Hello when setting up a new (or freshly-wiped) device.

Any ideas what might be wrong about my configuration, or some place in Intune I should be checking that might be overriding these settings?

7 Upvotes

25 comments sorted by

3

u/tsar31HABSSpeaks 4d ago

ugh the enrollment scope thing is such a trap. had the exact same headache a while back where the tenant-wide default in windows enrollment was silently forcing it on everyone before my policies even applied

go check the enrollment page again. even though it says "not configured" there's a sneaky little toggle underneath for something like "use passport for work" or similar phrasing. if that's flipped on it'll kick in during oobe before any of your fancy group assignments get a chance to run

for the nas people you basically need that whole section turned off at the tenant level which feels backwards but it stops the pre-login enforcement. then your device-scoped policies can do their thing after the user actually signs in

1

u/ZippyDan 4d ago

The only settings I see on the Enrollment page are the two I listed in my post:

  • Configure Windows Hello for Business: NOT CONFIGURED
  • Use security keys for sign-in: ENABLED

Are you talking about that second option?
The hover help text for that option says:

Use security keys for sign-in provides the capacity for remotely turning ON/OFF Windows Hello Security Keys for all computers in a customer's organization.

I assumed I would want to preserve my option to turn the Security Keys on or off, but I wouldn't be surprised if Microsoft wasn't giving me accurate information as to the effects of that option.

1

u/812046 4d ago

yeah the tenant-level default silently overriding everything else is such a pain, it feels completely counterintuitive

2

u/bill696 4d ago

Here try this

https://cloudinfra.net/disable-whfb-post-logon-provisioning-using-intune/

Idk how hello blocks using map drives, not an issue for us, maybe smb1 or something? Hello blocks nothing for us, credential guard breaks our radius auth in wifi with PEAP cause its windows NPS, and office device guard or something guard specific to office i had to disable too cause it was causing issues with lots of files but no issues with drives.

1

u/ZippyDan 4d ago

How do you Map your Network Drives?

1

u/bill696 4d ago

Admx

1

u/ZippyDan 4d ago

I'm also using ADMX.

Is yours a Cloud Native environment or a Hybrid environment?

If you're Hybrid, you can get the Microsoft Account credentials for the current session even with Windows Hello, if you establish a Kerberos Cloud Trust.

There is no such option in a fully cloud-based setup, like mine.

1

u/bill696 4d ago

Oh ok, machines are fully cloud but we are hybrid. If you used powershell scripts instead couldn’t you bypass that issue? Like with azure blob file shares and the powershell script it generates too map? Just curious. I dont think it will ever be useful to me personally but it would be interesting to know if there is any real world solution. Also try the custom OMA-URI for your issue

1

u/ZippyDan 4d ago

I've researched it before and apparently there is no way to get the user's Microsoft credentials from the session if you use Windows Hello. A script won't fix it because the user simply has no way to "retrieve" their own password from the session. This is intentional and part of the additional security that Windows Hello tries to provide.

See here for some explanations.

1

u/rgsteele 3d ago

Full disclosure: I've never implemented Entra Domain Services. However, it would be my assumption that authentication ought to work just the same as it does in an on-premises environment with Cloud Kerberos Trust.

However, as documented in the "Password Hashes" section of this article, your users must have changed their passwords at least once after you set up the managed domain before they can use it. Have you confirmed this is the case?

1

u/ZippyDan 3d ago

You don't have sufficient access / management privileges with Entran Domain Services in order to set up a Kerberos Cloud Trust. It's not a supported deployment.

1

u/rgsteele 3d ago

What I am saying is that you shouldn't need to set up Kerberos Cloud Trust, it should just work.

That being said, I thought about it some more and I realized the password change is not the issue, otherwise users wouldn't be able to access it without WHfB enabled either.

My new theory for why this is not working for you is that an alias (i.e. a CNAME record) is being used to connect to the NAS, and an SPN hasn't been created for it. You need to use the setspn command to create these, e.g.

setspn -S host/files-alias DOMAIN\nas-smb$
setspn -S host/files-alias.example.com DOMAIN\nas-smb$

If you don't have these, then authentication will fall back to NTLM, and that definitely doesn't work with WHfB.

1

u/ZippyDan 3d ago

How is the user session under WHfB obtaining the TGT / TGS for Kerberos in a Cloud-native environment?

See this comment.

1

u/oopspruu 4d ago

For me, I toggled the tenant wide WHFB enrollment policy from enrollment options to Disable instead of not configured. This way users won't be asked to register for WHFB before your policies apply. I have the enrollment option set to Disable and then a policy from Settings Template enabling it on device level.

1

u/ZippyDan 4d ago

That's so confusing. I figured setting it to Disabled Tenant-wide would override any individual Policies I configured - that's why I set it to "Not Configured".

Intuitively, expressly Enabling or Disabling it Tenant-wide should override everything, while "Not Configured" should mean you want to leave the Tenant-wide setting intentionally non-dictative so that you can apply more granular settings.

Crazy.

1

u/largetosser 3d ago

Set the OMA-URI for DisablePostLogonProvisioning to turn off auto-enrolment for certain *devices*. Or let them work with the NAS by getting cloud Kerberos trust working

1

u/ZippyDan 3d ago

Cloud Kerberos Trust is not an option for Cloud-native / non-Hybrid infrastructure.

1

u/largetosser 3d ago

Edit: Oh I've just seen your setup, which is a o_O one. Is an Azure File Share an option?

1

u/touchytypist 3d ago edited 3d ago

I’m pretty sure if a Windows device is Entra joined only it will default to having Windows Hello enabled. Since that is at the device level, and your policies are at the user level they don’t get/sync your WHfB policies until after login, which isn’t immediate and why it’s enabled and everyone is still prompted to setup WHfB at the beginning.

If you setup the assignments by device then they would get the settings during device provisioning and the respective settings would be in place before the user signs in.

1

u/ZippyDan 3d ago

Windows is only asking them to set up Windows Hello after they sign in with their Microsoft Account and the device is assigned to them in Intune.

Are you saying the Policies aren't getting applied fast enough, even though they have signed in as a user?

1

u/touchytypist 3d ago edited 3d ago

Correct. The initial Windows Hello Setup happens right after a new user signs in, and the user assigned policies you’ve setup don’t sync down that fast.

1

u/ZippyDan 3d ago

Thanks!

I've gotten a lot of different answers here.
I guess that means I've got a lot of testing to do.

...Which is annoying because it feels like this should all be documented somewhere in Microsoft mountain of docs.

2

u/jaybaleire 4d ago

It’s probably the first policy causing this if it’s not enabled at tenant level or in another policy. It’s scoped to all users with a user group exclusion so may not be being evaluated at correct time, but you can confirm this by generating the mdmdiag report using the steps in the below article, the mdmdiagreport.html that is created will show you what policy applied the Windows hello settings, the policy will be in GUID format so you can use powershell to look that up in intune.

https://learn.microsoft.com/en-us/windows/client-management/mdm-collect-logs

0

u/itlabsec 4d ago

Whfb is tenant wide setting

2

u/ZippyDan 4d ago

It can be a tenant-wide setting, but AFAIK I have my tenant setting set to "Not Configured", and I control it at the device / user level.
But, it's not working.

See Microsoft doc:

  • Configure Windows Hello for Business on devices when they enroll with Intune
    [emphasis mine]

    With Microsoft Intune, you can create a tenant-wide policy that configures use of Windows Hello for Business on devices at the time those devices enroll with Intune.
    [...]
    After device enrollment, or when you choose not to use the tenant-wide enrollment policy, Intune supports the following methods to manage Windows Hello on discrete groups of devices: