Merge pull request #6847 from MicrosoftDocs/main

Publish 02/17/2022 3:30 PM PT

Author: Angela Fleischmann

memdocs/intune/remote-actions/device-remote-lock.md

@@ -7,7 +7,7 @@ keywords:
 author: Smritib17
 ms.author: smbhardwaj
 manager: dougeby
-ms.date: 02/27/2020
+ms.date: 02/17/2022
 ms.topic: how-to
 ms.service: microsoft-intune
 ms.subservice: remote-actions
@@ -34,6 +34,8 @@ ms.collection: M365-identity-device-management
 
 The **Remote lock** device action locks the device. To unlock the device, the device owner enters their passcode. You can remotely lock devices that have a PIN or password set. Devices that don't have a PIN or password can't be remotely locked.
 
+When **Remote lock** is applied to a device that doesn’t have a PIN or password, the device’s screen will turn off but the device will not be locked and the user will be able to wake the device and start using it again without entering a PIN or password. Ensure devices have a PIN or password policy enforced before using the **Remote lock** action to lock the device.
+
 ## Supported platforms
 
 **Remote lock** is supported for the following platforms:

windows-365/enterprise/in-development.md

@@ -64,7 +64,7 @@ Currently, Windows 365 and Azure Virtual Desktop share a common framework for id
 <!-- ***********************************************-->
 ## Device management
 
-### Nested virtualizations<!--37800910-->
+### Nested virtualization<!--37800910-->
 
 In a future release, Windows 365 8vCPU/32GB licenses will support nested virtualizations for most currently supported regions. Southeast Asia and West US 2 will follow at a later date.