Blog Post

Windows IT Pro Blog
9 MIN READ

Expand passwordless access with confidence

Katharine_Holdsworth's avatar
Nov 17, 2026

Passwordless sign-in is tested in ordinary moments: when an employee needs to start work immediately, when a frontline worker approaches a shared device, or when a security team needs to understand how devices across the organization are being unlocked.

Moving beyond passwords requires more than a strong authentication method. Organizations need a sign-in approach they can depend on across the ways people work, visibility that helps IT understand if everything is working as intended, and protection for the data and credentials beneath the experience. When those elements work together, passwordless sign-in becomes a trusted part of everyday work instead of another exception to manage.

At Microsoft Ignite 2026, we're sharing new Windows capabilities that make sign-in more reliable, extend passwordless access to more people and devices, give IT greater visibility, and strengthen the hardware-backed protection behind it all. Some are available in Windows Insider Preview builds; others lay the groundwork for future capabilities.

Make sign-in dependable for everyday work

Sign-in is the first thing people do on their device each day, but it also stays part of their workday after that: unlocking after a break, confirming a change, or signing in to a website with a passkey. Waiting, retrying, or switching methods turns that routine moment into friction. Windows Hello Face, Fingerprint and PIN improvements are designed to make sign-in more consistent and reliable, helping users reach their desktop with less sign-in friction and get back to work quickly.

A smoother path to the desktop

Windows Hello now provides a more consistent experience across sign-in and unlock, with clearer guidance and fewer interruptions. Users also no longer have to wait for a biometric attempt to finish before choosing another method: if Face or Fingerprint does not recognize them right away, the PIN entry option appears alongside it, so they can use whichever option works first. After a restart, users sign in with their PIN first, creating a more familiar and predictable sign-in experience that is consistent with many modern devices. Face and Fingerprint are then available for subsequent unlocks. This experience also establishes the sign-in pattern that Windows will build on as we continue strengthening Windows Hello security.

Reliability built in, across the ecosystem

Dependable sign-in has to work in the real conditions people work in, including late at night and in dim rooms. Users told us Face sign-in in low light was a common point of failure, so we added a screen brightness option for Face sign-in. When it's turned on in Settings, Windows briefly brightens the display in low light so the camera can see the user and complete sign-in.

We've also enhanced Face recognition for everyday conditions and improved Fingerprint unlock so it's ready when a device wakes from sleep. For IT, that means Windows Hello works more consistently across the range of devices in your fleet, so fewer users fall back to other sign-in methods and fewer sign-in issues reach your help desk.

Give IT visibility into how users sign in

Scaling passwordless requires more than deploying it. IT and security teams need to know how people are actually authenticating, whether expected methods are being used, and where problems occur. New Windows Hello Event Logs provide that operational evidence without changing the user experience. This gives IT and security teams more information to support:

  • Audits and policy checks with a record of if the device was unlocked using Face, Fingerprint or PIN

  • Investigations into unsuccessful attempts or unexpected sign-in behavior

  • Deployment analysis that can help teams understand adoption and identify where users may need support

The events provide visibility without changing the user experience, connecting the moment of sign-in to the operational evidence IT needs to manage passwordless access at scale.

Extend passwordless access to more workstyles

Passwordless only works at organizational scale when it works across the environments people actually use. Shared PCs, hybrid identity environments and existing on-premises resources can create gaps that leave organizations dependent on older authentication approaches. New Windows capabilities help close more of those gaps.

Bring passwordless to shared and hybrid environments with web sign-in

Previously available only for Microsoft Entra joined devices, web sign-in now supports Microsoft Entra hybrid joined devices. From the Windows sign-in screen, users can authenticate through a web-based Microsoft Entra experience with a passkey on their phone or a FIDO2 security key. Organizations with supported hybrid deployments can extend phishing-resistant, passwordless sign-in to more of the devices their people share. Web sign-in for Microsoft Entra hybrid joined devices is available on Windows 11 Pro and Windows 11 Enterprise.

NFC key sign-in is easier with tap location guidance now on shared and frontline Windows devices

For shared and frontline devices that support NFC tap on the front or edge of the display, Windows is also making the sign-in experience easier to discover. The new NFC tap location indicator on the Windows lock screen helps users quickly see where to tap an NFC-enabled card, key, or badge, reducing guesswork and help desk calls when moving between devices. OEMs can configure the indicator based on the device's NFC antenna placement, while IT admins retain control through policy, helping organizations bring phishing-resistant passwordless sign-in to more users with a clearer, more consistent experience.

Understand your device's security and privacy

Going passwordless asks people to trust their device with their identity. That trust grows when people can see how their device is protected and decide what apps can access. New security and privacy experiences in Windows Settings make that visible.

Security and privacy users can see and control

A new Security page in Windows Settings puts passkeys and core device protections in one place, so users can see how they're protected and act with confidence. Users can also allow or deny camera, microphone and location access for each desktop app, and apps using these capabilities for the first time must ask the user for permission first. Existing choices and enterprise policies carry over, so nothing resets. For IT, that means one familiar place to point users for their passkeys, protection and privacy, with your policies still in force.

More control over security key passkeys

Users can now see the passkeys stored on a FIDO2 security key and remove them one at a time, instead of resetting the entire security key to clear a single passkey. Admins preparing security keys for employees can also configure enterprise settings, such as which websites can read a security key's minimum PIN length.

Protect the trust beneath passwordless sign-in

Passwordless sign-in protects how people access Windows. But attackers don't stop at the sign-in screen. They also go after the device when it's lost or stolen, the protocols it uses to authenticate on the network, and the hardware that stores its keys. Windows includes protections designed to help address each of these attack vectors.

Reduce reliance on legacy authentication with IAKerb

NTLM is one of the largest attack surfaces in Windows environments. It's open to relay, pass-the-hash, and offline cracking attacks, and it doesn't support mutual authentication. Even so, many organizations haven't been able to retire it. IAKerb closes one of the big blockers for NTLM retirement by enabling Kerberos-based authentication beyond direct domain connectivity. Supported Windows devices can authenticate on-premises resources using Kerberos even when they do not have direct line of sight to a domain controller. This reduces scenarios that would otherwise fall back to NTLM and helps organizations move toward a more secure, Kerberos-first authentication model. IAKerb is currently supported on Windows 11 clients, with Windows Server support planned for a future release.

Admin rights only when you need them

Standing admin rights is one of the easiest ways for attackers to take over a Windows device. With Administrator protection, admin users run with standard rights by default. Each time admin rights are needed, Windows grants them elevated access just in time, inside a system-managed account, and removes them when the task is done. This shuts down common attack paths like privilege reuse and User Account Control bypasses, and users can still install apps, change settings and run admin tools as usual.

Lock a device without losing anything

With remote lock, IT can lock a managed Windows device from Microsoft Intune or other device management service. The lock signs out active sessions and blocks users from signing in. The locked screen shows the organization's message and help desk contact.

Nothing is erased: the device stays enrolled and managed, BitLocker protection stays in place, and user data stays where it is. That makes it the right tool when you need to protect a lost or stolen device until it's recovered or contain a compromised device while your security team investigates. When required, the IT admin can unlock the device remotely from Microsoft Intune and the user picks up where they left off, with no reimaging and no lost work.

BitLocker TPM + PIN for every managed user

Many organizations require a startup PIN so a lost or stolen device's drive stays locked until the right person turns it on. But with BitLocker managed through Microsoft Intune, only users with administrator rights could set that PIN. Since most users aren't admins, IT couldn't easily require TPM + PIN across the fleet.

We've changed that. When your Intune policy permits silent standard user enablement and requires TPM + PIN, Windows encrypts the device right away and then prompts the user at the desktop, whether admin or standard, to set their startup PIN. Compliance is reported back to Intune automatically, and the recovery password is backed up first, so IT can always recover the device. The BitLocker startup PIN unlocks the hard drive when the device powers on, before Windows starts. It's separate from the Windows Hello PIN, which users enter to sign in once Windows is running.

Bringing enterprise credential protection into Microsoft Pluton

Passwordless sign-in helps establish who the user is. Organizations also need to trust the device that they're signing in from. Protecting the private keys behind a device's identity and management credentials helps defend against their theft and reuse to impersonate a trusted device.

We're bringing Microsoft Entra device identity and Microsoft Intune enrollment credentials into Pluton, with attestation enabling services to verify that protection. While this will be available to customers in a future release, we're introducing the Microsoft Pluton Key Storage Provider (KSP) now as the foundational piece that enables these scenarios for developer evaluation. Developers can use familiar Windows cryptographic APIs such as NCrypt to create, manage and use keys protected inside Pluton.

From helping protect a lost device's data to advancing protection for enterprise device credentials, these updates and planned capabilities strengthen the foundation beneath a passwordless experience that organizations can trust.

Move from preview to practice

Use the resources below to evaluate each capability in supported Windows Insider Preview builds and validate it against your device, policy, and deployment requirements:

Capability

How to try it

Windows Hello sign-in improvements

Available today in the Windows 11 Insider Experimental Preview channel.

Automatically adjust brightness for Windows Hello facial sign-in

Available today in Windows 11 Insider Experimental Preview build 26340.9750 and coming soon in the November 2026 non-security preview update.

Navigate to Settings > Accounts > Sign-in options. Select "Automatically adjust screen brightness during face recognition."

Monitoring Windows Hello sign-in activity

Available today in the Windows 11 Insider Experimental Preview channel.

Event Viewer > HelloForBusiness/Operational

Event Viewer > Windows Logs/Security

Web sign-in for Microsoft Entra hybrid joined devices

Available today in Windows 11 Insider Experimental Preview build 26340.9750 and coming to retail soon.

NFC Tap Location Indicator

Coming to NFC-enabled devices in the November 2026 non-security preview update.

Passkey security key management

Coming this month to Windows Insiders in the Experimental channel.

Security page in Windows Settings

Coming this month to Windows Insiders in the Experimental channel.

IAKerb (Initial and Pass-Through Authentication using Kerberos)

Available today in in the Windows 11 Insider Experimental Preview channel.

Administrator protection

Administrator protection is off by default. IT admins can turn it on with Intune or Group Policy starting with the August 2026 non-security preview update.

Individual users can go to Windows Security > Account protection and turn it on starting with the October 2026 non-security preview update.

Remote lock

Coming this month to Windows Insiders in the Experimental channel.

Requires a Windows 11 Enterprise, Windows 11 Education or Windows 11 Pro device that is Microsoft Entra joined, hybrid joined or MDM-enrolled.

BitLocker TPM + PIN for standard users

Coming this month to Windows Insiders in the Experimental channel.

Requires Intune-managed device and a startup PIN with TPM in your BitLocker policy.

Pluton Key Storage Provider

Coming this month to Windows Insiders in the Experimental channel.

Learn more

Updated Nov 17, 2026
Version 2.0
No CommentsBe the first to comment