Lost or stolen Windows laptop? IT can lock it down without wiping it now

Microsoft is testing a remote lock capability for Windows that lets IT administrators freeze a lost or stolen machine over a remote connection instead of wiping it. The feature is built to run alongside Microsoft Intune for device management and BitLocker for disk encryption, so an organization can handle a fleet of laptops and phones spread across offices and remote locations.
The core behavior: once a device is reported missing or stolen, an admin can cut off login access from wherever they are, without erasing the laptop or phone. Microsoft says the lockdown holds through restarts and even when the device is offline from Wi-Fi, and only an admin can release it. That matters because it removes the usual ways a thief might get in — stored passwords, PINs or biometric sign-ins — since the device is already sealed before anyone reaches the login screen. In practice, think of it less as a wipe and more as a persistent padlock that an endpoint management system enforces.
The feature is narrower than a full compromise response, and Microsoft's own framing leaves clear gaps that other Windows controls still have to cover. Remote lock does not erase data or wipe the device if it never comes back, and it does not cut the missing machine off from corporate networks. Admins who want those actions still go through the Intune and Microsoft Entra dashboards. It also leaves the user's Microsoft account credentials untouched, so the person can still sign in on other devices to recover data, change passwords and temporarily revoke permissions.
The most significant limitation is at the boot layer. Remote lock does not prevent a device from starting in Safe Mode, booting from a USB drive, entering Windows Recovery Mode, or having its storage drive reimaged. Because those paths sit beneath the operating system's normal sign-in flow, Microsoft strongly recommends keeping BitLocker enabled until the device is either wiped or recovered. That advice follows from how the stack fits together: Intune pushes policy, Windows enforces the lock, and BitLocker is what keeps the data unreadable if someone tries to sidestep the OS entirely. A determined attacker with physical possession can still attempt those routes, so the lock raises the cost of casual access rather than making a stolen laptop unrecoverable.
Setup runs through policy rather than a single button. An admin signs into the Intune management center and navigates Devices, then Windows, then Configuration, then Create, New Policy, Windows 10 and later, Templates, then Custom. That creates a profile that can be applied to each network-connected device, along with a device group reserved for lockdown. Locking a machine is then a matter of adding it to that group. Unlocking works the same way in reverse: create a second profile and device group for the unlock state and move the device into it.
That group-based model is a familiar Intune pattern, and it carries the usual trade-offs. It scales well for large fleets, since membership can be managed in bulk, but it means the lock is only as fast as policy delivery — an admin needs the device to pick up the assignment, which is one reason the offline persistence matters. Organizations will also want to think about how these groups are named and audited, because moving a device between them is the whole control surface.
This is being tested, so teams evaluating it should treat availability, exact naming in the console, and behavior on unusual hardware as things to confirm in their own tenant rather than assume. The feature is designed for IT administrators rather than end users, so there is no self-service angle here; an employee who loses a laptop still reports it and waits for an admin to act.
Why it matters: IT teams that manage Windows fleets get a middle option between doing nothing and wiping a device that might still be recovered, which can preserve data and reduce the disruption of reissuing hardware. Developers and product teams working on endpoint management, device compliance or identity integrations should note that the lock sits on top of Intune policy and depends on BitLocker for protection below the OS, so it complements rather than replaces wipe, network isolation and credential reset flows. My inference is that the main operational cost will be maintaining clean device groups and clear runbooks so admins know when to lock, when to isolate and when to wipe.
Based on reporting from the original publisher. Visit the source for full context and later updates.
Publisher excerpt
The Intune-enabled feature will allow admins to remotely lock down any compromised Windows device.