Microsoft is testing a way for standard users to add their own BitLocker preboot PIN, without an admin stepping in. That could save a helpdesk call, but don’t send the policy to the whole fleet. On standard-user devices without the feature, Microsoft warns that encryption fails or existing TPM-only devices report non-compliant.
What’s actually new (and what isn’t)
The change is in Windows 11 Insider Preview Build 28020.3532, released on 13 November 2026 in the Beta (26H1) channel. The preboot PIN itself is not new: TPM+PIN has existed for years behind the “Require additional authentication at startup” policy. On those builds, with the feature enabled, standard users can add the PIN without elevation. All users targeted by the policies get a notification if their device does not already have a PIN, including administrators. Selecting it opens the enrollment window. This is the BitLocker preboot PIN entered before Windows loads, not a Windows Hello PIN.
Admin-side prerequisites, user-side enrollment
The enrollment gesture belongs to the user, but everything that makes it happen is admin configuration. Microsoft’s release notes list four existing BitLocker policies to set in Intune or another device management solution: AllowStandardUserEncryption to ON, AllowWarningForOtherDiskEncryption to OFF, RequireDeviceEncryption to ON, and SystemDrivesRequireStartupAuthentication to ON. Two reference details that matter when you plan with these. First, AllowStandardUserEncryption is CSP-only (no Group Policy equivalent), and it depends on AllowWarningForOtherDiskEncryption being set to 0, the silent-encryption mode. The CSP reference says that value 0 only takes effect on Microsoft Entra joined devices. Do not assume that wording establishes support for this new enrollment flow on hybrid-joined devices; validate the join type separately. Second, SystemDrivesRequireStartupAuthentication is the ADMX-backed “Require additional authentication at startup” setting, so its behavior is the same surface you’ve had for years, just now enforceable on standard-user devices that support the new enrollment. Also keep the general BitLocker rule in mind: settings are enforced when encryption starts; changing policy does not restart encryption on an already-protected drive.
The failure mode the targeting warning is about
Scope the required-TPM+PIN policy wider than the Insider test group and you get exactly the outcome Microsoft spells out: standard users whose devices don’t have the feature can’t add the required protector, so device encryption fails on those machines. Devices already encrypted with TPM only can’t satisfy the new requirement and report as non-compliant with policy. Those are the documented outcomes: failed encryption and policy non-compliance. The rollout is also gradual and explicitly experimental (“Features and experiences included in these builds might never get released”), so a device on the right build number still isn’t proof the enrollment feature is active on it.
Will the PC come back after an overnight patch reboot?
Test the restart your fleet actually uses, including an Autopatch deadline or a maintenance-window reboot. If TPM+PIN protection remains active for that restart and no working Network Unlock path is available, the PC stops at the PIN screen before Windows can finish coming back online. Confirm whether your update or deployment process temporarily suspends BitLocker protection for that reboot, and verify that protection resumes afterward. This is not a recommendation to suspend every patch cycle manually: Microsoft’s FAQ says no user action is required to apply Microsoft quality or feature updates. The pilot needs to prove the unattended restart path, not assume it.
Network Unlock is a specific domain-environment setup, not something a VPN connection supplies. It requires a wired corporate network, compatible UEFI DHCP support and a Windows Deployment Services server, along with its policy and certificates. If it is unavailable, the usual TPM+PIN prompt returns. Do not assume it is an option for an Entra-only pilot or a remote laptop at home.
A validation checklist before it touches anything else
I haven’t run this in a fleet, and this list is a plan, not a report. If you want to pilot it, this is the bounded sequence I’d use with a small, dedicated standard-user Insider group:
- Confirm policy scope: the startup-authentication and device-encryption settings land on the test group only, nothing dynamic that could widen later.
- Confirm the notification audience: all targeted users without a PIN receive the prompt, including any administrators in scope. On a test device with the feature active, verify that a standard (non-admin) account can complete enrollment from it.
- Reboot and verify the PIN is actually demanded at preboot and the device unlocks with it.
- Check protector and encryption state from an elevated prompt (
manage-bde -status): TPM+PIN present, protection on and encryption progress where expected. Record the same checks after the managed patch reboot to confirm protection resumed if it was suspended. - Check Intune compliance for the test device, then confirm a non-target device is untouched.
Before real users join the pilot, also confirm where the recovery key is backed up and that the helpdesk can retrieve the right key. Check the actual Entra or AD recovery configuration rather than assuming this enrollment change establishes a new backup path.
Bottom line
Requiring admin rights to add a PIN is a support chore this experiment could remove. It does not remove the preboot prompt or make unattended restarts someone else’s problem. Keep the policy on feature-enabled Insider test devices, verify encryption and compliance, and test a real managed reboot before considering a wider rollout.
Sources
- Windows 11 Insider Beta (26H1) Preview Build 28020.3532 release notes (Microsoft Learn, 13 November 2026)
- Announcing new builds for 13 November 2026 (Windows Insider Blog)
- BitLocker CSP reference (Microsoft Learn; used to verify AllowStandardUserEncryption scope and dependencies)
- BitLocker Network Unlock (Microsoft Learn)
- BitLocker FAQ (Microsoft Learn)
- BitLocker operations guide (Microsoft Learn)
