Microsoft is testing a Windows 11 security feature that gives IT teams an option between leaving a missing laptop accessible and erasing it. Remote Lock blocks normal Windows sign-in through Microsoft Intune while keeping the device enrolled and its files in place. For a laptop that might simply have been left in a meeting room, that is a useful distinction.

The important qualifier is availability: this is a preview, not a capability administrators should assume exists across their production fleet. Windows Latest reported the feature on November 16, and Microsoft lists it in Windows 11 Insider Preview Build 29708.1001, released November 13 in the Experimental (Future Platforms) channel.

What Windows 11 Remote Lock actually does

When the lock takes effect, Windows signs out every active session, removes the usual sign-in choices and displays a dedicated locked-device screen. A password, Windows Hello PIN, local administrator account or web sign-in cannot lift the lock. An administrator must send the unlock through Intune.

The device remains managed, existing BitLocker protection stays enabled and user data is not erased. The lock also survives restarts and continues to apply while the computer is offline after receiving it.

Think of Remote Lock as a managed sign-in barrier, not a remote data vault. It changes who can get back into the normal Windows environment without turning the incident into an immediate wipe-and-rebuild operation. Because active sessions are signed out, administrators should still treat activation as disruptive rather than as an ordinary screen lock.

Preview support needs careful interpretation

Microsoft's preview documentation specifies Windows Pro, Enterprise or Education and devices that are Microsoft Entra joined, hybrid joined or MDM-enrolled. The documentation also carries broad operating-system applicability labels, including older Windows versions and Windows Server releases.

Those labels should not be mistaken for confirmation that every listed operating system already supports this preview. The concrete announcement is tied to Build 29708.1001. Microsoft's release notes also warn that Experimental channel features can change, disappear or never reach a public Windows release.

For IT teams, the sensible next step is a controlled evaluation on an eligible test device, not a promise to the business that every missing laptop can now be locked this way. Confirm support on the actual build and enrollment configuration before adding it to an incident-response commitment.

How Intune delivers the lock

The preview uses a custom configuration profile rather than a simple assumption that Intune's existing Remote lock action now covers Windows. Microsoft describes creating the profile under Devices > Windows > Configuration > Create > New policy, selecting Windows 10 and later, and then Templates > Custom.

The required setting is ./Device/Vendor/MSFT/RemoteDeviceLock/LockState, configured as an integer. A value of 1 requests a lock; 0 requests an unlock. Two optional string settings under the same path, LockReason and RecoveryHint, let administrators supply an explanation and help-desk contact information. Their respective limits are 1,024 and 256 characters.

Microsoft's workflow assigns the lock profile to a dedicated device group. Adding a laptop to that group applies the lock at its next check-in. Recovery uses a separate profile with LockState set to 0; the administrator moves the computer from the lock group to the unlock group.

A read-only Status node distinguishes Unlocked, Locked, Lock pending and Error. Operationally, that distinction matters: assigning a policy is not the same as confirming that a missing computer has enforced it.

Connectivity is the main operational catch

An offline laptop cannot receive a new Intune instruction until it reconnects and checks in. Remote Lock is therefore not an instantaneous protection mechanism for a device that has already disappeared from the network.

The same dependency matters during recovery. There is no local or offline unlock, even for someone who knows an administrator password. A returned laptop needs to receive the unlock through Intune before normal sign-in becomes available again.

Before a pilot, test both directions. Verify that a device receives the lock, reports its effective state, remains locked after a restart, and can subsequently receive the unlock. Include a realistic return-to-office scenario rather than testing only on a continuously connected lab machine.

Why BitLocker and account security still matter

Remote Lock does not block Windows Recovery Environment, Safe Mode or booting from external media. It also does not prevent someone from removing the drive or reimaging the computer. Microsoft's guidance explicitly says to keep BitLocker enabled to protect the data in those circumstances.

Nor does the feature isolate the laptop from the network or disable its user's identity. Credentials remain valid on other devices. If an incident includes suspected account compromise, the response must separately address Microsoft Entra ID account controls and session revocation as appropriate.

These are different security jobs: Remote Lock restricts normal device sign-in, encryption protects stored information, and identity controls address account access. None should be treated as a substitute for the others.

What users and help desks should prepare for

For employees, the practical message is straightforward: a managed locked-device screen is a reason to contact IT, not repeatedly reset a password. Help desks should have a documented way to verify the caller, identify the device and authorize its release.

For administrators, a useful pilot also includes clear recovery text, tightly scoped device groups and a check that lock and unlock assignments do not overlap unintentionally. Keep the feature within existing lost-device procedures rather than replacing those procedures with a single policy.

Remote Lock could make recoverable laptop incidents less destructive. Its value depends on verified deployment, working management connectivity and an unlock process that is as carefully tested as the lock itself.

Sources

Technical details were checked against Microsoft's Remote Lock preview documentation and the Build 29708.1001 release notes.

Original reporting: Abhijith M B at Windows Latest.