A technician uses an RFID badge beside devices and a dashboard displaying security and authentication controls.
Microsoft's case for passwordless Windows has always sounded fine in a keynote. The harder test is a frontline worker tapping a badge on a shared tablet at 6 a.m., or a help desk trying to work out why half the finance team keeps dropping back to their PIN. On November 17, at Microsoft Ignite 2026, the Windows IT Pro Blog announced a group of Windows 11 changes aimed at those everyday cases. They cover sign-in reliability, visibility for IT, hybrid and frontline coverage, user-facing security controls, and the protections underneath.

Most of these features are still in preview. Some are in the Windows 11 Insider Experimental Preview channel now, some are headed for the November 2026 non-security preview update, and Microsoft calls at least one a future capability. Treat this as a roadmap to test, not features you can switch on across your fleet this week.

A technician uses an RFID badge beside devices and a dashboard displaying security and authentication controls. Windows Hello: fewer waits, one fixed order​

Microsoft says it reworked Windows Hello Face, Fingerprint and PIN to behave more consistently across sign-in and unlock:

  • No more waiting on biometrics. If Face or Fingerprint doesn't recognize you right away, the PIN box appears next to it. You no longer wait for the biometric attempt to time out before choosing another method.
  • PIN first after a restart. After a reboot, users sign in with their PIN. Face and Fingerprint work for later unlocks. Microsoft says many modern devices already work this way, and that Windows will build on this pattern as it keeps hardening Windows Hello.
  • Help in low light. Users reported that Face sign-in often failed in dim rooms. A new option briefly brightens the screen so the camera can see you. The setting is under Settings > Accounts > Sign-in options: turn on "Automatically adjust screen brightness during face recognition." It's in the Experimental channel now and is coming in the November 2026 non-security preview update.
  • Recognition and wake fixes. Microsoft says it improved Face recognition in everyday conditions and made Fingerprint unlock ready as soon as a device wakes from sleep.

Microsoft says these changes mean fewer users fall back to other methods and fewer tickets reach the help desk. It published no success rates, no ticket-reduction numbers and no list of supported devices, so those benefits are claims to check in your own pilot.

Summary: The changes make sign-in more predictable. The PIN-first-after-restart rule is the one most likely to surprise users who are used to face unlock on a cold boot, so it's worth telling them about it ahead of time.

New Windows Hello sign-in events in Event Viewer​

The most useful addition for administrators may be the new Windows Hello sign-in events. They don't change anything users see, but they give IT a record of what actually happens at sign-in. Microsoft lists three uses:

  • Audits and policy checks that show whether a device was unlocked with Face, Fingerprint or PIN
  • Investigating failed attempts or unusual sign-in behavior
  • Tracking adoption and finding users who may need help

Microsoft Learn's Windows Hello for Business configuration page, which marks the feature as Insider Preview, gives the event details:

LogEvent IDWhat it records
Windows Logs > Security4628Success. Logged for each sign-in, with the user's enrolled Hello methods, the method used, and Enhanced Sign-In Security status. Shows "-" if Windows Hello wasn't used
Windows Logs > Security4629Failure. A failed Windows Hello attempt and the method tried
Applications and Services Logs > Microsoft > Windows > HelloForBusiness > Operational5010Successful Windows Hello sign-in
Same Operational log7010Unsuccessful Windows Hello sign-in

According to Learn, events 4628 and 4629 use the existing Audit Logon policy, so you don't need a new audit setting to collect them. Learn recommends the Security events for monitoring and audits, and the Operational events for troubleshooting.

A practical starting point: search for 4628 events where the method field is "-". Those are users enrolled in Windows Hello who still signed in some other way, which is the gap you're trying to close.

Web sign-in now covers hybrid-joined PCs​

Many organizations have waited years for this one. Web sign-in was limited to Microsoft Entra joined devices. Microsoft now says it supports Microsoft Entra hybrid joined devices on Windows 11 Pro and Enterprise. From the Windows sign-in screen, users authenticate through a web-based Entra page using a passkey on their phone or a FIDO2 security key.

The request goes back a long way. In a 2022 Microsoft Q&A thread, a Microsoft responder said hybrid support was "under consideration" with no ETA. ID Tech reported that the hybrid feature shipped in Windows 11 Insider Experimental Preview Build 26340.9750, released on October 16, and that supported users can authenticate with a security key, a phone passkey or a Temporary Access Pass.

Hybrid shops care about what happens after sign-in. Both ID Tech and the HTMD Blog report that after a successful web sign-in, Windows obtains a Kerberos ticket so the user can continue accessing on-premises file shares and internal websites.

Before you roll it out, check these points:

  • The public docs are out of date. The main Microsoft Learn web sign-in page still states that web sign-in is not supported for Microsoft Entra hybrid joined or domain joined devices. Expect it to be updated as the feature moves toward release.
  • Plain domain-joined PCs are still excluded. The change applies to hybrid joined devices, not machines joined only to on-premises Active Directory.
  • It needs internet access. Learn says cached credentials aren't supported with Web sign-in. As ID Tech notes, users can't sign in this way while the device is offline.
  • It's still a preview. Microsoft says it's "coming to retail soon" without a date. ID Tech also points out that Microsoft warns experimental functionality can change, be removed or never reach a general Windows release.

NFC badges: an on-screen hint for where to tap​

On shared and frontline devices with NFC readers on the front or edge of the display, the lock screen can now show a tap location indicator pointing to where a card, key or badge should go. OEMs set the indicator to match each device's antenna position, and IT can control it through policy. It's coming to NFC-enabled devices in the November 2026 non-security preview update.

The indicator doesn't add NFC hardware or change how authentication works. It removes the guesswork for someone moving between unfamiliar devices.

A Security page in Settings and per-key passkey management​

On the user side, Microsoft is adding:

  • A new Security page in Windows Settings that puts passkeys and core device protections in one place.
  • Per-app privacy controls for desktop apps. Users can allow or deny camera, microphone and location access for each app, and apps must ask for permission the first time they use those features. Microsoft says existing user choices and enterprise policies carry over unchanged.
  • Passkey management on security keys. Users can see the passkeys stored on a FIDO2 security key and delete them one at a time, instead of resetting the whole key to remove one. Admins who prepare keys for employees can set enterprise options, such as which websites can read a key's minimum PIN length.

All three are listed as coming to Experimental-channel Insiders this month.

IAKerb, Administrator protection, remote lock and BitLocker​

IAKerb: reducing NTLM fallback​

Microsoft describes NTLM as one of the largest attack surfaces in Windows. It's open to relay, pass-the-hash and offline cracking attacks, and it doesn't support mutual authentication. IAKerb (Initial and Pass-Through Authentication using Kerberos) lets supported Windows 11 clients use Kerberos for on-premises resources even without a direct connection to a domain controller. Microsoft says that removes one of the main obstacles to retiring NTLM. IAKerb is in the Experimental channel now, and Windows Server support is planned for a later release.

It reduces cases where Windows falls back to NTLM. It doesn't eliminate NTLM, so you still need to audit where NTLM is used before you block it.

Administrator protection: elevation only when needed​

With Administrator protection on, admin accounts run with standard rights. When a task needs admin rights, Windows grants them just in time inside a system-managed account and removes them when the task finishes. Microsoft says this shuts down attacks such as privilege reuse and User Account Control (UAC) bypasses.

The feature is off by default:

  • IT can enable it through Intune or Group Policy starting with the August 2026 non-security preview update.
  • Individual users can turn it on under Windows Security > Account protection starting with the October 2026 non-security preview update.

Microsoft says users can still install apps and run admin tools as usual. Test it against older line-of-business software before you rely on that.

Remote lock: lock the device, keep the data​

From Intune or another device-management service, IT can lock a managed Windows device. Active sessions are signed out, sign-in is blocked, and the lock screen shows your organization's message and help-desk contact. Nothing is erased. The device stays enrolled and managed, BitLocker stays on, and user data stays in place. An admin can later unlock it from Intune.

That covers the case between doing nothing and wiping a laptop that might just be in someone's car. Requirements are Windows 11 Pro, Enterprise or Education, on a device that is Entra joined, hybrid joined or MDM-enrolled. It's coming to Experimental-channel Insiders this month.

BitLocker TPM + PIN for standard users​

Until now, with BitLocker managed through Intune, only users with admin rights could set a startup PIN, so requiring TPM + PIN across a fleet was impractical. In the new flow, if your Intune policy allows silent enablement for standard users and requires TPM + PIN, Windows encrypts the drive immediately and then prompts the user at the desktop to set a startup PIN, whether they're an admin or not. The recovery password is backed up first, and compliance is reported to Intune.

Microsoft points out that the BitLocker startup PIN, which unlocks the drive before Windows starts, is separate from the Windows Hello PIN. Put that in your user communications.

From general Intune practice: silent BitLocker setups have traditionally been unable to require a startup PIN, because setting one needs the user. The new flow handles this by encrypting first and prompting afterward. Test your exact policy combination and recovery process in a pilot before deploying widely. The feature requires an Intune-managed device and a BitLocker policy that specifies TPM with a startup PIN.

Pluton Key Storage Provider​

Microsoft plans to store Microsoft Entra device identity and Intune enrollment credentials in the Pluton security processor, with attestation so services can confirm the keys are protected there. Customers get that in a future release. What's arriving this month for Experimental-channel Insiders is the Microsoft Pluton Key Storage Provider (KSP), for developers to evaluate. It lets developers create, manage and use Pluton-protected keys through familiar Windows cryptographic APIs such as NCrypt. Microsoft didn't list supported hardware or a customer ship date.

Availability at a glance​

FeatureStatus, per Microsoft
Windows Hello sign-in improvementsExperimental channel now
Low-light face brightnessExperimental channel now; November 2026 non-security preview update
Windows Hello sign-in eventsExperimental channel now
Web sign-in for hybrid joined devicesExperimental channel now; retail "soon"
NFC tap location indicatorNovember 2026 non-security preview update
Security-key passkey managementExperimental channel, this month
Security page in SettingsExperimental channel, this month
IAKerbExperimental channel now (Windows 11 clients only)
Administrator protectionOff by default; IT controls from the August 2026 preview update, user toggle from the October 2026 preview update
Remote lockExperimental channel, this month
BitLocker TPM + PIN for standard usersExperimental channel, this month
Pluton KSPExperimental channel, this month (developer evaluation)

Where to start​

This isn't one switch that makes an organization passwordless. Microsoft is closing specific gaps: hybrid devices, shared hardware, NTLM fallback, standing admin rights and missing BitLocker PINs. A reasonable order of work:

  1. Turn on the sign-in events first. They use your existing logon auditing and show where you stand today.
  2. Pilot hybrid web sign-in on shared devices with reliable network access, and confirm that on-premises file shares still open after sign-in.
  3. Test Administrator protection against your app catalog before enabling it broadly.
  4. Update recovery runbooks for remote lock and the new BitLocker PIN flow.
  5. Keep preview features off production machines until they're generally available.

Microsoft hasn't provided measurements to back its reliability claims, and several pieces are still marked "coming soon." The direction is clear, though, and organizations whose passwordless plans stalled on hybrid joins or shared devices now have something concrete to test.

 

References

  1. Expand passwordless access with confidence Windows IT Pro Blog Tue, 17 Nov 2026 21:53:57 GMT
  2. Use Web Sign-In To Enable Passwordless Sign-In In Windows learn.microsoft.com
  3. Microsoft Tests Passwordless Windows Sign-In on Hybrid Entra Devices - ID Tech idtechwire.com