Remote Lock for Windows: Intune’s New Lost-Device Option, Explained
Someone emails you that their laptop is missing. Is it stolen, or did it slide under the passenger seat on the drive home? Until five minutes ago, the honest answer for a Windows device was: wipe it and find out, because there was no good middle option. Microsoft just shipped one. Remote Lock for Windows, currently in preview, locks a device from Intune without touching a single file on it — and it’s worth understanding exactly where its edges are before you lean on it.
Key takeaways
Remote Lock signs a Windows device out of every session, hides all sign-in options, and shows a locked screen with a custom message and help-desk contact — nothing is erased, BitLocker stays on, and the device stays enrolled. It’s configured today through a custom OMA-URI profile (it’s preview, not yet a one-click admin-center button), requires Entra joined, hybrid joined, or MDM-enrolled Windows Enterprise/Education/Pro, and applies at the device’s next check-in rather than instantly. The sharpest edge: there is no offline or local unlock at all — not a PIN, not local admin, nothing. The device only unlocks by checking back in to Intune, and boot-level paths like WinRE, Safe Mode, and external media aren’t blocked by this control, which makes BitLocker the thing actually protecting data if the drive gets pulled.
What actually happens on the device
Enable it, and Windows signs out every active session immediately, hides all the normal sign-in options, and shows a lock screen you control the wording on. Two optional fields do the work: LockReason (up to 1,024 characters) explains why to the user, and RecoveryHint (up to 256 characters) tells them who to call. The lock survives a restart and holds even while the device is offline — it doesn’t need a live connection to stay locked, only to get unlocked. Nothing about the device’s management state, its enrollment, or its data changes. This is explicitly a holding pattern, not a remediation.
How to set it up right now
Because it’s still preview, there’s no dedicated button on a device’s overview page yet — you build it as a custom configuration profile:
- In the Intune admin center: Devices > Windows > Configuration > Create > New policy, platform Windows 10 and later, profile type Templates > Custom.
- Add the OMA-URI settings below, with
LockStateset to 1 to lock. - Assign the profile to a device group you reserve for locked devices. Add the device you want locked to that group — the lock applies at its next check-in, not instantly.
- To unlock, build a second profile with
LockStateset to 0, assigned to a separate unlock group, and move the device there.
| 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 | Message on the lock screen |
| Recovery hint (optional) | ./Device/Vendor/MSFT/RemoteDeviceLock/RecoveryHint |
String | Help-desk contact info |
A read-only Status node reports the actual effective state — 0 Unlocked, 1 Locked, 2 Lock pending, 3 Error — worth checking before you assume a lock landed, since this whole mechanism runs on the device’s check-in cadence rather than firing the moment you assign the profile.
Requirements
The device needs to be Microsoft Entra joined, hybrid joined, or MDM-enrolled, running Windows Enterprise, Education, or Pro — Windows Home isn’t in scope. Nothing in the documentation ties this to a specific licensing add-on beyond standard Intune management, which makes it a low-barrier control to pilot compared to features gated behind E5 or Entra ID P2.
Remote Lock vs. Remote Wipe: pick based on certainty, not severity
These solve different moments, not different degrees of the same problem. Remote Lock is for the “I don’t know yet” window — a device reported missing, a login from somewhere unexpected, anything where wiping would be an overreaction if it turns out to be nothing. It’s fully reversible and costs you nothing if the laptop turns up in a coat pocket. Remote Wipe is for the moment you’ve decided the device isn’t coming back under your control — confirmed theft, retirement, a device you’re never getting physically back. Reach for lock first in almost every “missing device” call; only escalate to wipe once the ambiguity is gone.
The gotchas worth knowing before you flip this on
- There’s no fallback unlock. No PIN, no local admin account, no web-based override — the device unlocks only by checking in to Intune and picking up the unlock profile. If a device genuinely can’t reach your Intune environment (no network path, a broken NIC, a tenant-side outage), it stays locked until it can. Don’t lock a device you need back in production in the next ten minutes without a plan for that.
- It doesn’t touch the user’s account. Credentials stay completely valid, and the user can sign in on a different device with the same account while this one sits locked. If the actual concern is a compromised credential rather than a missing laptop, Remote Lock alone doesn’t contain that — you still need Microsoft Entra ID to revoke sessions or force a password reset.
- Boot-level paths aren’t blocked. Windows Recovery Environment, Safe Mode, and booting from USB or other external media all still work — this control operates at the normal Windows sign-in layer, not the boot layer. The thing standing between someone with physical access and your data is BitLocker, not this feature. If BitLocker isn’t already on, Remote Lock is largely theater.
- It’s group-membership-driven right now, not a button. Build the operational workflow around moving a device between an Entra ID group and waiting for a check-in, not around a one-click action on the device page — that may well change once this leaves preview, but it’s not how it works today.
Bottom line
Remote Lock fills a real gap — a reversible, non-destructive way to take a device out of commission the moment you’re unsure about it, instead of jumping straight to a wipe you can’t take back. Just go in knowing what it isn’t: it’s not an account-level control, it’s not a boot-level control, and right now it’s not instant. Pair it with BitLocker already being on and a clear answer for what happens if the device can’t check back in, and it’s a genuinely useful first response for exactly the kind of call that used to force an all-or-nothing decision.