Read Time: 2 minutes

Key facts

Topic Microsoft Tests Remote Lock
Severity Low
Versions 26320.10003, 26340.10013, 29708.1001

What happened

Microsoft introduced a non-destructive locking mechanism in the Intune admin center that relies on custom configuration profiles and group assignments to secure lost or stolen hardware. Instead of wiping a missing laptop, administrators toggle a configuration setting to freeze access until the device is recovered.

In the Intune admin center, the locking and unlocking workflow follows a specific group-based sequence:

  1. Create a custom configuration profile (for example,Remote lock – ON) with theLockStatevalue set to1, and assign it to a dedicated locked-devices group.
  2. Add the missing endpoint to that locked-devices group so the restriction applies at the device’s next check-in.
  3. Create a second custom configuration profile withLockStateset to0and assign it to a separate unlock group.
  4. Move the recovered endpoint from the lock group into the unlock group to restore normal user access.

In plain English

Think of this feature like a deadbolt that only your IT department has the key to turn. When a laptop goes missing, moving its record into a designated lock group tells the operating system to bar local access at its next check-in, while moving it to an unlock group later opens the door again without erasing the hard drive.

Who’s affected

Microsoft is testing the new Windows Remote Lock capability with enterprise IT administrators and end users running eligible Windows 11 Insider Preview builds. The feature applies to managed devices enrolled through Microsoft Intune, targeting systems upgraded to preview builds 26320.10003, 26340.10013, and 29708.1001 in the Beta channel.

To qualify for management, endpoints must meet specific edition and directory enrollment criteria:

  • Operating system editions: Windows Enterprise, Windows Education, or Windows Pro.
  • Enrollment states:Microsoft Entra-joined, hybrid-joined, or mobile device management (MDM)-enrolled devices.

Once an administrator triggers the lock, the device stays enrolled and managed while BitLocker encryption remains active and user data stays intact. The lock persists across system restarts and while the machine is offline, without isolating the endpoint from the enterprise network. Only an administrator can lift the restriction remotely so the user can resume work where they left off.

Related on InfoSec Platform

  • Practical Guide: Orion browser for Linux axed months after beta launch

Sources: BleepingComputer, Digitaltrends, ZDNET, The Register