A laptop goes missing. A wipe is drastic if it turns up in a taxi an hour later. Doing nothing leaves a signed-in device in unknown hands. Remote lock for Windows is the middle option.
This is still a Preview feature. Microsoft labels remote lock as Preview, so behavior may change before general availability.
What it does
- IT locks a Windows device from Microsoft Intune.
- Windows signs out every active session, hides all sign-in options and shows a "Device locked" screen.
- Nothing is erased. The device stays enrolled and managed, BitLocker stays on and user data stays in place.
- The lock holds across restarts and while the device is offline. The lock can only be removed from Intune. Even a Global Admin or a local admin cannot unlock the device itself. After the unlock, the user picks up where they left off.
How to enable it
In the preview, remote lock runs through a custom OMA-URI profile in Intune. Devices must be Microsoft Entra joined, hybrid joined or MDM-enrolled, on Windows Pro, Enterprise or Education.
- Create the profile. In the Intune admin center, go to Devices > Windows > Configuration > Create > New policy. Choose Windows 10 and later, then Templates > Custom.
- Add the settings. Name the profile (for example, "Remote lock - ON") and add the settings below, with
LockState= 1. - Assign it to a lock group. Assign the profile to a device group reserved for locked devices. Adding a device to the group locks it at its next check-in.
- Unlock. To unlock, create a second profile with
LockState= 0, assign it to an unlock group, and move the device from the lock group to the unlock group.
| Setting | OMA-URI | Type | Value |
|---|---|---|---|
| Lock state (required) | ./Device/Vendor/MSFT/RemoteDeviceLock/LockState | Integer | 1 = lock, 0 = unlock |
| Lock reason (optional) | ./Device/Vendor/MSFT/RemoteDeviceLock/LockReason | String | Shown on the lock screen, up to 1,024 characters |
| Recovery hint (optional) | ./Device/Vendor/MSFT/RemoteDeviceLock/RecoveryHint | String | Help desk contact, up to 256 characters |
The read-only Status node reports the effective state: 0 Unlocked, 1 Locked, 2 Lock pending, 3 Error.
What it does not do
- It does not touch the account. Credentials stay valid and the user can still sign in on other devices. Disable the account or revoke sessions in Microsoft Entra ID.
- It does not isolate the device from the network or erase data. Use the existing Intune controls for that.
- There is no offline or local unlock, for anyone. No PIN, password, local admin, Global Admin or web sign-in works on a locked device. The lock is removed only from Intune, by moving the device to the unlock group.
- It does not block the boot and recovery paths. Windows Recovery Environment, Safe Mode and booting from USB or other media still work. Keep BitLocker on to protect data if the drive is removed or the device is reimaged.
Our take
Treat remote lock as one step in a lost-device runbook, not a replacement for it. The runbook we recommend:
- Lock. Lock the device in Intune.
- Revoke sessions. Revoke the user’s sessions in Microsoft Entra ID.
- Check encryption. Confirm BitLocker is on.
- Wipe only if needed. Wipe only if the device does not come back.
Create the lock and unlock groups before you need them. A stolen laptop is a bad time to design them.
Want help setting up Intune device controls and a lost-device runbook? Book a meeting with OnCloud.
Book a meeting