Skip to main content

Microsoft Previews Remote Lock for Lost Windows Devices in Intune

Microsoft has started a preview that lets IT lock a lost or stolen Windows device from Intune without wiping it. How the group-based preview works, which editions it covers, and why the lock group needs protecting.

A woman in a gray coat works on a laptop while sitting in a subway car.
KBY News Desk6 min read

In this article

Share

Microsoft has started a preview of remote lock for Windows, which lets IT lock a lost, stolen or compromised Windows device from Microsoft Intune without wiping it. The feature is documented on Microsoft Learn in a page dated Thursday 12 November and updated the next day. In the preview it is not a button in the Intune console: admins set it up with a custom configuration profile and lock or unlock a device by moving it between groups. Microsoft says the lock “holds across restarts and while offline, and only an admin can lift it remotely”, and that “Nothing is erased: the device stays enrolled and managed, BitLocker stays on and user data stays in place.”

We are covering this a few days after Microsoft published the page because it fills a gap many Windows admins have worked around for years, and because the way the preview works has consequences for who can lock your devices that are easy to miss.

#What remote lock does

The idea is a middle option between doing nothing and wiping. When a laptop is left on a train, taken in a burglary or suspected of being compromised, the usual choices are to wait and hope it comes back, or to wipe it remotely and accept that any data not already synced is gone. Remote lock lets IT stop the device being used without destroying anything on it. If it turns up, an admin unlocks it and the user carries on.

According to Microsoft’s documentation, the lock:

  • stays in place when the device restarts, and works even if the device is offline once it has received the setting;
  • can only be lifted remotely by an admin; there is no local unlock;
  • leaves the device enrolled and managed, with BitLocker still on and user data in place.

Microsoft is also clear about what it does not do. User accounts are not touched, there is no local way to unlock, and Recovery and Safe Mode are not blocked. Help Net Security, which reported the preview on 16 November, adds the consequence for identity: credentials “remain valid and can still be used to sign in on other devices”.

#Which devices it covers

Microsoft’s page says devices “must be Microsoft Entra joined, hybrid joined or MDM-enrolled, running Windows Enterprise, Education or Pro”. It names editions, not version numbers. Help Net Security reported a different list, saying the preview covers Windows 11, Windows 10 and Windows Server 2022, 2019 and 2016. Microsoft’s own page does not mention Windows Server, so we would treat the Learn page as the authority and not assume servers are covered until Microsoft says so.

#How it works in the preview

“In the preview, remote lock is configured through a custom configuration profile in Intune,” Microsoft says. The profile uses a custom OMA-URI setting with a value called LockState: 1 locks the device and 0 unlocks it. Two optional values, LockReason and RecoveryHint, let you set what the user sees.

In practice, the documented pattern is to create two Entra groups, one for devices to lock and one for devices to unlock, and assign a profile to each. To lock a device, you add it to the lock group. To unlock it, you move it to the unlock group. The device picks up the change the next time it checks in with Intune.

That is a workable design for a preview, and it means you can try the feature today without waiting for a console button. It also means the speed of the lock depends on how quickly the device checks in, and that the lock only reaches a device that is online at some point after you make the change.

#Our view: useful, but watch who controls the groups

For organisations with laptops in the field, this is a genuinely useful addition. A wipe is the right answer when a device is gone for good, but it is a blunt tool when a laptop has simply been left in a meeting room or a taxi and will probably come back. A reversible lock that survives restarts and keeps BitLocker in place is the option many admins have wanted for Windows.

The group-based design in the preview has a side effect that we think deserves attention before anyone rolls it out. If adding a device to a group locks it, then anyone who can change that group’s membership can lock devices, including, by mistake or on purpose, the CEO’s laptop or the whole sales team’s. In our view the lock group should be treated like a privileged control: an assigned group rather than a dynamic one, owned by a small number of admins, and ideally a role-assignable group so that only privileged roles can change it. A dynamic group whose rule is edited carelessly could lock hundreds of devices at the next check-in.

The second point is about what remote lock is not. It stops the device being used. It does not sign the user out of anything else, and Microsoft says Recovery and Safe Mode are not blocked. On a lost or stolen device, the data is protected by BitLocker, not by the lock, and the user’s accounts are protected only by what you do in Entra ID. Remote lock should sit alongside those steps, not replace them.

#Who should care

Any organisation that manages Windows devices with Intune and has staff working away from the office: field engineers, sales teams, executives who travel, schools with student laptops. Organisations that manage Windows with Configuration Manager alone, or not at all, are not covered by this preview. Remember that it is a preview: Microsoft can change how it works before it is generally available, and it should not yet be the only step in a lost-device process.

#What to do

  1. Read the Learn page and try it on test devices. Set up the lock and unlock profiles against a small pilot group of devices you control, and check how long a lock takes to apply after you change a group.
  2. Protect the lock group. Use an assigned, not dynamic, group, restrict who can change its membership, and consider a role-assignable group. Record who added each device and why.
  3. Check BitLocker coverage. Because Recovery and Safe Mode are not blocked, make sure every Windows device has BitLocker on and its recovery keys escrowed in Entra ID or Intune. Remote lock does not protect data on its own.
  4. Update the lost-device runbook. For a lost or stolen device: lock it, then in Entra ID revoke the user’s sessions and, if there is any chance the password was exposed, reset it. Wipe only if the device is not recovered within the time your policy sets.
  5. Write the message users will see. Use LockReason and RecoveryHint to tell anyone who finds the device how to return it, without giving away anything sensitive.

#What we do not know yet

Microsoft has not said when remote lock will become generally available, whether it will become a standard device action in the Intune console, or whether it will extend to Windows Server. We will report on those when Microsoft announces them.

Evidence trail

Sources and verification

Primary documentation and external technical references used in this article.

  1. 01Microsoft Learn: Remote lock for Windows devices (preview)learn.microsoft.com
  2. 02Help Net Security: Microsoft previews remote lock for lost or stolen Windows deviceshelpnetsecurity.com

About this page

Credited to

Dates

Published

Corrections

No corrections are listed for this page. Some review sweeps corrected pages without naming each one; those are in the corrections log.

Reader Interaction

Comments

Add a thoughtful note on Microsoft Previews Remote Lock for Lost Windows Devices in Intune. Comments are checked for spam and held for moderation before appearing.

Loading comments...

More news

All news

Was this useful?

Reports go to the site owner and are used to correct pages. Corrections are listed at /corrections.

Get new fixes by email.

New runbooks, configuration traps and fixes from KBY Technologies, about twice a week.