Logo
CloudWithSingh
Back to all field notes
Workflow
Microsoft Intune
Intermediate

Remote Lock for Windows in Intune: Lock a Lost Laptop Without Wiping It

The new Windows remote lock (preview) in Intune: what it does and doesn't do, the two-profile setup with the exact OMA-URIs, the lost-laptop runbook with Graph PowerShell, and the gaps you still have to cover with Entra ID and BitLocker.

Parveen Singh
November 16, 2026
8 min read
Prerequisites:Windows Pro, Enterprise or Education devices that are Entra joined, hybrid joined or MDM enrolled in IntuneRights to create configuration profiles and manage group membership in Intune and Entra ID
TLDR

Windows finally has a remote lock that isn't a wipe. Push one setting from Intune and the laptop signs everyone out, hides every sign-in option and shows a "Device locked" screen until an admin unlocks it. Nothing is erased and the device stays managed. It's in preview, it runs through a custom OMA-URI profile and two groups, and it does not touch the user's account, so pair it with an Entra session revoke.

🧭 Lock, Wipe or Disable: Pick the Right Tool

A lost laptop is three separate problems: the device, the data on it and the account that was signed in. Remote lock solves the first one only.

SituationUse thisWhat it does
Laptop lost or stolen, might come backRemote lock (Windows, preview)Locks the device, keeps data, enrollment and BitLocker in place
Laptop gone for good, or holds data you can't riskWipeResets the device and removes data
Employee leaving, device returning to the poolRetire or Autopilot resetRemoves company data and management, or resets for the next user
Password or tokens might be compromisedDisable the user or revoke sessions in Entra IDStops the account everywhere, on every device
Suspected compromise, need the device off the networkDefender for Endpoint isolation (outside this feature)Cuts network access while you investigate

Intune's built-in Remote lock button still only covers phones, Macs and a few other platforms. For Windows, this preview is the path, and it's driven by a configuration profile instead of a button.

🔒 What Remote Lock Does and Doesn't Do

It doesIt doesn't
Signs out every active sessionTouch the user's account (credentials stay valid elsewhere)
Hides all sign-in options (PIN, password, web sign-in, local admin)Isolate the device from the network
Shows a locked screen with your reason and help desk contactErase any data
Keeps BitLocker on and the device enrolledBlock Windows Recovery, Safe Mode or booting from USB
Survives restarts and holds while offlineOffer any local or offline unlock

The last row matters most for support. There is no PIN, recovery code or local admin trick. The only way back in is the unlock profile from Intune.

🛠️ One-Time Setup: Two Profiles, Two Groups

Build this before you need it. During an incident you want to add a device to a group, not read documentation.

#CreateName itSettings
1Entra security group (assigned membership)Remote lock - ONEmpty until a device is lost
2Entra security group (assigned membership)Remote lock - OFFEmpty until a device is recovered
3Custom profile, Windows 10 and laterRemote lock - ONLockState 1, plus LockReason and RecoveryHint
4Custom profile, Windows 10 and laterRemote lock - OFFLockState 0
5AssignmentsProfile 3 to group 1, profile 4 to group 2Device groups, not user groups

The path in the Intune admin center: Devices > Windows > Configuration > Create > New policy > Windows 10 and later > Templates > Custom.

The OMA-URIs

SettingOMA-URIData typeValue
Lock state (required)./Device/Vendor/MSFT/RemoteDeviceLock/LockStateInteger1 lock, 0 unlock
Lock reason (optional)./Device/Vendor/MSFT/RemoteDeviceLock/LockReasonStringShown on the lock screen, up to 1,024 characters
Recovery hint (optional)./Device/Vendor/MSFT/RemoteDeviceLock/RecoveryHintStringHelp desk contact, up to 256 characters

Copy them one at a time:

./Device/Vendor/MSFT/RemoteDeviceLock/LockState
./Device/Vendor/MSFT/RemoteDeviceLock/LockReason
./Device/Vendor/MSFT/RemoteDeviceLock/RecoveryHint

Lock screen text that actually helps the person holding the laptop:

LockReason:   This device was reported lost and has been locked by Contoso IT.
RecoveryHint: If this is your laptop, call the help desk at 1-800-555-0100 or email helpdesk@contoso.com.

🚨 Runbook: A Laptop Is Lost

StepActionWhere
1Add the device to Remote lock - ONEntra ID or Graph PowerShell
2Trigger a sync so it doesn't wait for the next check-inIntune > Devices > the device > Sync
3Revoke the user's sessions, or disable the account if credentials may be exposedEntra ID
4Confirm the profile shows Succeeded for the deviceIntune > the profile > Device status
5Log the incident with the BitLocker recovery key locationYour ticketing system

The same thing in Microsoft Graph PowerShell:

Connect-MgGraph -Scopes "GroupMember.ReadWrite.All","Device.Read.All","User.RevokeSessions.All"
 
# Find the Entra device object and the lock group
$device = Get-MgDevice -Filter "displayName eq 'LAPTOP-0142'"
$lock   = Get-MgGroup  -Filter "displayName eq 'Remote lock - ON'"
 
# Lock: add the device to the lock group
New-MgGroupMember -GroupId $lock.Id -DirectoryObjectId $device.Id
 
# Kill the user's refresh tokens and browser sessions on every device
Revoke-MgUserSignInSession -UserId "alex@contoso.com"

Reading the status

The CSP reports the effective state on the device through a read-only Status node:

StatusMeaning
0Unlocked
1Locked
2Lock pending
3Error

🔓 Runbook: The Laptop Comes Back

StepAction
1Remove the device from Remote lock - ON
2Add it to Remote lock - OFF
3Sync the device and wait for the unlock profile to show Succeeded
4Have the user sign in; their files and apps are where they left them
5Remove the device from Remote lock - OFF once it's confirmed unlocked
$unlock = Get-MgGroup -Filter "displayName eq 'Remote lock - OFF'"
 
Remove-MgGroupMemberDirectoryObjectByRef -GroupId $lock.Id -DirectoryObjectId $device.Id
New-MgGroupMember -GroupId $unlock.Id -DirectoryObjectId $device.Id

🧱 The Gaps You Still Cover Yourself

Remote lock blocks the Windows sign-in screen. It does not block the boot path, so anyone with the laptop can still reach Windows Recovery, Safe Mode or boot from a USB stick. What protects your data at that point is BitLocker.

GapCover it with
Drive pulled out or device reimagedBitLocker on every device, enforced by an Intune disk encryption policy
User signed in somewhere else with the same passwordEntra ID: revoke sessions, reset the password, or disable the account
Device needs to be cut off from the networkDefender for Endpoint device isolation
Device is never coming backIntune Wipe

Put remote lock in your lost-device process now, test it on one spare laptop, and write down the unlock steps for the help desk. It's a preview, so check the official page before you roll it out wide.

📚 Official References

ResourceWhat's There
Remote lock for Windows (preview)The feature, the OMA-URIs, the lock screen and the scope limits
Intune device action: remote lockThe built-in remote lock button and the platforms it covers
Deploy OMA-URIs to target a CSP through IntuneHow custom profiles deliver CSP settings
Revoke-MgUserSignInSessionRevoking a user's sessions after a lost device

What's Next

Bookmark this page

Save it for your next project sprint

Start a project

Apply what you just learned hands-on

Follow on Instagram

Daily cloud tips & behind-the-scenes

Try hands-on labs

Practice in a real cloud environment

Parveen Singh

Parveen Singh

Microsoft Certified Trainer & Cloud Solutions Consultant

Related Field Notes

Found this useful?

Stay in the loop

Weekly cloud insights, no spam

Subscribe

Explore CloudLearn

Hands-on labs & projects

Start Learning

Book Training

Custom cloud training for your team

Get in Touch

On this page

Subscribe