Windows Remote Lock: test the unlocking path too
Microsoft is previewing remote locking for Windows devices through Intune. Businesses need to test when the instruction works and how they recover the device before adopting it.
Lire en portugaisBy Pentesty
A preview for a limited test
The Register report dated November 17, 2026 covers the Windows Remote Lock preview. The official notes for experimental build 26340.10013, released November 16, describe locking through Intune without erasing data. These are features under development: availability in a preview does not establish uniform support across production devices.
The feature documentation says the command depends on the device’s next check-in. Once applied, the lock persists through restarts and loss of connectivity, while unlocking arrives through Intune. This creates two test questions: when the instruction becomes effective and how the team restores operation on a device that has legitimately been returned.
A sent instruction needs confirmation
Reserve a small group of eligible test devices. Document version, edition, management enrollment and encryption state before any change. Use test accounts and synthetic files. The initial goal is to validate the combination actually installed, with authorization and a recovery path, before proposing any expansion of the procedure.
Record approval of the request, the correct device, policy assignment and the time of each observed transition. Include a case where the machine is disconnected when the instruction is sent. Compare the state shown in management with local behavior after reconnection. A screenshot of a requested action alone does not establish the outcome on the endpoint.
Include recovery in the same exercise
Before applying the lock, decide who authorizes and who performs its removal. A support request should identify the device and establish the legitimacy of the recovery request through approved channels. Keep secrets out of the text displayed on screen. The support contact needs to remain usable when the laptop itself is unavailable.
Run the complete round trip: lock, confirmation, restart and authorized removal. Observe recovery after a period without networking and record the outcome, including errors and waiting time. The management continuity analysis helps examine platform dependence. Administrative console access should not be confused with a demonstrated ability to recover that particular device.
Add a scenario in which the usual operator is unavailable. Ask another authorized administrator to follow the approved procedure and recover only the exercise device. Record which permissions and information were needed without sharing accounts. If recovery depends on informal knowledge or an inaccessible credential, document that dependency and correct the procedure before considering it ready for an incident affecting real business operations.
Connect the other response decisions
The documented lock does not disable the user’s account, isolate networking or erase data. The documentation also distinguishes boot and recovery paths and recommends keeping BitLocker enabled. A loss or compromise report should therefore open separate decisions about identity, network communication and data protection, according to the facts established for the scenario.
For each decision, connect an accountable owner, an approved action and evidence of the outcome. If credentials may be exposed, the assessment of endpoints and sessions broadens the investigation. A bounded test ends with observed results and recorded limitations, supporting a decision on whether the preview meets the intended procedure. That conclusion applies to the tested configuration and needs review when it changes.
Frequently asked questions
Does Remote Lock already cover the whole fleet?
The sources reviewed present it as a preview. Verify eligibility and test the installed configuration before incorporating it into the company’s response procedure.
Does sending a command immediately lock an offline laptop?
The documentation ties application to the next check-in. Testing should distinguish the request, synchronization and observed device lock, including the disconnected period.
Does the lock replace an account review?
The feature does not change the account. Decisions about sessions and credentials need to consider the incident and other access authorized to that identity.
What evidence supports closing the test?
Keep approval, device identification and local results for locking and recovery. Include failures, observed timing and the limits of the configuration tested.
Sources and references
- The Register: November 17 report
- Microsoft: Remote Lock preview documentation
- Microsoft: experimental build 26340.10013 notes
Original Pentesty analysis, published November 17, 2026. The proposed scenarios are editorial guidance, with scope and validation to be defined for each environment.