A man uses a tablet to remotely lock a laptop, with a secure cloud icon connecting the devices.
Microsoft is testing a feature for Windows admins who need to deal with a missing laptop without erasing it. Remote Lock lets IT lock a lost, stolen, or compromised Windows device from Microsoft Intune. Windows signs out every session, hides all sign-in options and shows a "Device Locked" screen. The device stays enrolled and managed, BitLocker stays on, and nothing is deleted.

Until now, Intune admins were stuck between waiting and wiping. Remote Lock is a reversible middle option. It is still a preview, though, and it has limits that admins should understand before they rely on it.

A man uses a tablet to remotely lock a laptop, with a secure cloud icon connecting the devices. Which Windows 11 Insider builds have Remote Lock?​

Reports name different builds, so here is what is confirmed:

  • Microsoft's documentation: Microsoft's release notes for Windows 11 Insider Experimental (Future Platforms) Preview Build 29708, dated November 13, 2026, describe Remote Lock. The build number is not consistent. 4sysops noticed that the announcement lists Future Platforms build 29708.1003, while the release notes are titled 29708.1001. Ghacks, Neowin and an earlier WindowsForum report use 29708.1001.
  • The newer 26H2 builds: BleepingComputer reports that Remote Lock is reaching Insiders in Beta (Build 26320.10003) and Experimental (Build 26340.10013). Notebookcheck says the Experimental build also introduces Remote Lock in Build 26340.10013. Warp2Search describes the pair as Beta build 26320.10003 and Experimental build 26340.10013, both based on the Windows 11 version 26H2 enablement package. It calls Remote Lock the standout feature in the Experimental build.

Several outlets tie the feature to Experimental build 26340.10013. The Beta build 26320.10003 claim comes mainly from BleepingComputer, so test it on your own Insider devices before assuming it's there.

The Microsoft Learn page for Remote Lock is labeled Preview. It lists Windows 11, Windows 10 and Windows Server 2016, 2019 and 2022 as applicable platforms. Neowin noted that the company has only announced the feature through its new Windows 11 preview, with no other details about older versions. Ghacks added that Microsoft has not said when the feature will reach the stable release of Windows 11.

Section summary: Remote Lock is preview-only and limited to Insider builds. Build numbers differ between sources, and Microsoft hasn't given a date for general availability.

What happens when a device is locked​

Microsoft's documentation describes the following behavior once the lock applies:

  • All active sessions are signed out. The user is logged off.
  • Every sign-in option is hidden. The lock screen shows no PIN, password or Windows Hello prompt.
  • No local unlock works. PIN, password, local administrator and web sign-in all fail. Only an unlock from Intune lifts it.
  • The lock survives restarts and offline periods. Pulling the network cable or rebooting doesn't clear it.
  • Nothing is erased. Data stays on the drive and the device stays enrolled, so when it's unlocked the user picks up where they left off.

Admins can customize the lock screen. Notebookcheck says it shows a Device Locked screen that admins can customize with a lock reason and help desk contact details. That helps if an honest finder or a confused employee turns the machine on.

Requirements​

According to Microsoft Learn, the preview needs:

RequirementDetail
ManagementMicrosoft Intune
Join/enrollment stateMicrosoft Entra joined, hybrid joined, or MDM-enrolled
Windows editionEnterprise, Education, or Pro
Configuration methodCustom OMA-URI configuration profile (preview)

Home users are not covered. As Ghacks put it, Remote Lock is aimed at managed business devices and requires Intune, so it does not apply to personal Windows 11 PCs that are not enrolled in device management.

How to set up Remote Lock in Intune​

For the preview there is no button in the Intune console. You lock a device by putting it in a group that has a lock policy assigned. Microsoft's steps are:

  1. In the Intune admin center, go to Devices > Windows > Configuration > Create > New policy.
  2. Choose Windows 10 and later, then Templates > Custom.
  3. Name the profile (Microsoft's example is "Remote lock - ON") and add the OMA-URI settings below, with LockState = 1.
  4. Assign the profile to a device group reserved for locked devices.
  5. To lock a device, add it to that group. The lock applies at the device's next check-in.
  6. To unlock, create a second profile with LockState = 0 and assign it to a separate unlock group. Then move the device from the lock group to the unlock group.

The settings Microsoft documents are:

SettingOMA-URIData typeValue
Lock state (required)./Device/Vendor/MSFT/RemoteDeviceLock/LockStateInteger1 = lock, 0 = unlock
Lock reason (optional)./Device/Vendor/MSFT/RemoteDeviceLock/LockReasonStringShown on the lock screen, up to 1,024 characters
Recovery hint (optional)./Device/Vendor/MSFT/RemoteDeviceLock/RecoveryHintStringHelp desk contact, up to 256 characters

How to confirm the lock applied​

Assigning the profile doesn't mean the device is locked yet. Microsoft documents a read-only Status node that reports the actual state:

  • 0 Unlocked
  • 1 Locked
  • 2 Lock pending
  • 3 Error

"Lock pending" usually means the device hasn't checked in since you added it to the group. A missing laptop that's switched off or in a drawer won't get the policy until it connects to the internet. Neowin made the same point: a computer must initially receive the locking policy through Intune, which happens at its next check-in. Once the lock applies, it holds while offline. An unlock also waits for the next check-in.

Common mistakes​

  • Leaving the device in both groups. If a device is in the lock group and the unlock group at once, the two profiles conflict. Microsoft's instructions say to move the device, so remove it from the lock group when you add it to the unlock group.
  • Expecting an instant lock. The lock depends on check-in, so check the Status node instead of assuming it worked.
  • Treating the recovery hint as an afterthought. Without a help desk contact on the lock screen, a stranded employee may not know who to call.

Section summary: You lock and unlock by moving devices between groups with two custom profiles. Check the Status node to see whether the lock is pending, applied or failed.

What Remote Lock doesn't cover​

Microsoft lists several things outside the feature's scope, and each one matters for incident response:

  • The user's account still works. Credentials stay valid on other devices. To disable the account or revoke sessions, use Microsoft Entra ID.
  • The device stays on the network. Remote Lock doesn't isolate the machine. Use Intune's existing isolation controls for that.
  • Nothing gets wiped. If you need the data gone, use Intune's wipe controls.
  • Boot and recovery paths stay open. The Windows Recovery Environment, Safe Mode and booting from USB or other media are not blocked.

The last point is the important one. Remote Lock controls who can sign in to Windows. It doesn't stop someone from reaching the disk another way. If a thief removes the drive or boots from a USB stick, BitLocker is what protects the data, which is why Microsoft says to keep it on. On a device without BitLocker, Remote Lock gives much weaker protection than it seems to.

If you suspect the user's credentials were stolen along with the laptop, locking the device alone isn't enough. Use the full playbook: Entra account actions, network isolation if needed, and a wipe if recovery looks unlikely.

Don't confuse it with other "remote lock" features​

Microsoft has used the same name for several things:

  • Intune's existing device action. The Backroom Tech points out that Microsoft now documents two different features called "Remote lock," and they behave differently. The older action is under Devices > All devices: select the device, then choose Secure > Remote lock from the action row. The new preview is a separate policy-based mechanism built on the RemoteDeviceLock settings.
  • Consumer Find My Device. Microsoft's support pages describe a separate feature for personal Microsoft accounts. You locate and lock the device from your Microsoft account's devices page. Find My Device must have been turned on beforehand and location must be enabled. It has nothing to do with Intune.

When a ticket says "remote lock the laptop," confirm which one is meant.

Analysis: a useful gap-filler with rough edges​

Admins have wanted this for a long time. When a laptop is left in a taxi, a full wipe is often too much: it destroys data, the device may turn up the next day, and re-provisioning takes time. Neowin described the goal as securing compromised devices without going for the nuclear option and wiping their hard drives clean. A lock that survives reboots and offline periods and can be reversed fits that situation.

There are reasons to hold back for now:

  • The admin workflow is clunky. 4sysops said the feature remains preview-only and depends on OMA-URI configuration. Managing devices through group membership is workable, but it's slow when you're in a hurry. A dedicated console action would be faster and less error-prone, and it would be no surprise if Microsoft added one before general availability, though it hasn't said so.
  • It's only as strong as BitLocker. The open recovery and boot paths aren't a flaw, since Microsoft documents them plainly. They do mean an unencrypted device gets little real protection from Remote Lock.
  • Experimental features can disappear. Microsoft says features in these channels may change, be removed, or never ship beyond Insiders.

Bottom line​

Remote Lock lets Intune admins lock a lost or stolen Windows device without wiping it. Users see a locked screen, data and enrollment stay intact, and only an admin can unlock it. For now it requires Insider builds, Entra-joined, hybrid-joined or MDM-enrolled devices on Pro, Enterprise or Education, and a custom OMA-URI profile. It doesn't disable accounts, isolate devices, erase data or block alternative boot paths, so keep BitLocker on and use it alongside your other response steps. Test it on a spare Insider device you can reach, then check the Status node before relying on it for a real lost laptop.

 

References

  1. Microsoft testing Remote Lock for lost or stolen Windows devices BleepingComputer 2026-11-17T06:19:51-05:00
  2. Windows 11 Insider Experimental (Future Platforms) Preview Build 29708.1003 - Windows Insider Program | Microsoft Learn learn.microsoft.com
  3. Windows 11 26H2: New Insider Builds 26320 and 26340 Bring Remote Lock, Pluton Crypto Preview, and Taskbar List View warp2search.net