Merge branch 'main' of https://github.com/MicrosoftDocs/memdocs-pr into Android8Support

Author: lenewsad

memdocs/intune/enrollment/device-enrollment-manager-enroll.md

@@ -33,7 +33,7 @@ ms.collection:
 
 # Enroll devices in Intune by using a device enrollment manager account
 
-You can enroll up to 1,000 mobile devices with a single Azure Active Directory account by using a device enrollment manager (DEM) account. DEM is an Intune permission that can be applied to an Azure AD user account and lets the user enroll up to 1,000 devices. A DEM account is useful for scenarios where devices are enrolled and prepared before handing them out to the users of the devices. By design, there's a limit of 150 Device Enrollment Manager (DEM) accounts in Microsoft Intune.
+You can enroll up to 1,000 devices with a single Azure Active Directory account by using a device enrollment manager (DEM) account. DEM is an Intune permission that can be applied to an Azure AD user account and lets the user enroll up to 1,000 devices. A DEM account is useful for scenarios where devices are enrolled and prepared before handing them out to the users of the devices. By design, there's a limit of 150 Device Enrollment Manager (DEM) accounts in Microsoft Intune.
 
 ## Limitations of devices that are enrolled with a DEM account
 

memdocs/intune/enrollment/enrollment-restrictions-set.md

@@ -200,7 +200,6 @@ The following filter properties are always available to use with enrollment poli
 
 * OS version 
 * Operating System SKU 
-* Ownership
 * Enrollment profile name
 
 **iOS/iPadOS and macOS**  

memdocs/intune/enrollment/windows-enrollment-status.md

@@ -99,7 +99,7 @@ To turn on the Enrollment Status Page, follow the steps below.
 8. Choose **Settings** > *choose the settings you want to apply to this profile* > **Save**.
 
 > [!NOTE]
-> Due to OS restrictions, only a subset of filters are available to use when assigning **Enrollment Status Page** policies. The filter picker will only show filters that have rules defined for `osVersion`, `operatingSystemSKU`, `deviceOwnership`, and `enrollmentProfileName` properties. Filters that contain other properties are not shown.
+> Due to OS restrictions, only a subset of filters are available to use when assigning **Enrollment Status Page** policies. The filter picker will only show filters that have rules defined for `osVersion`, `operatingSystemSKU`, and `enrollmentProfileName` properties. Filters that contain other properties are not shown.
 
 ## Set the enrollment status page priority
 

memdocs/intune/fundamentals/in-development.md

@@ -90,7 +90,7 @@ As part of a public preview, you'll soon be able to use the Microsoft Defender f
 ## Device configuration
 
 ### Use Collect diagnostics to collect additional details from Windows 365 devices through Intune remote actions<!--  12636207 -->
-Intune’s remote action to [*Collect diagnostics*](../remote-actions/collect-diagnostics.md) will soon collect additional details from Windows 365 (Coud-PC) devices.  (**Devices** > **Windows** > *select a Windows 365 device* > **Collect diagnostics**)
+Intune's remote action to [*Collect diagnostics*](../remote-actions/collect-diagnostics.md) will soon collect additional details from Windows 365 (Cloud PC) devices.  (**Devices** > **Windows** > *select a Windows 365 device* > **Collect diagnostics**)
 
 The new details for Windows 365 devices include the following registry data:
 - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\AddIns\WebRTC Redirector 

memdocs/intune/protect/encrypt-devices.md

@@ -177,6 +177,9 @@ IT admins need to have a specific permission within Azure Active Directory to be
 
 All BitLocker recovery key accesses are audited. For more information on Audit Log entries, see [Azure portal audit logs](/azure/active-directory/devices/device-management-azure-portal#audit-logs).
 
+> [!NOTE]
+> If you delete the Azure AD object for an Azure AD joined device protected by BitLocker, the next time that device syncs with Azure AD it will remove the key protectors for the operating system volume. Removing the key protector leaves BitLocker in a suspended state on that volume. This is necessary because BitLocker recovery information for Azure AD joined devices is attached to the Azure AD computer object and deleting it may leave you unable to recover from a BitLocker recovery event.
+
 ### View recovery keys for tenant-attached devices
 
 When you’ve configured the tenant attach scenario, Microsoft Endpoint Manager can display recovery key data for tenant attached devices.

windows-365/enterprise/end-user-access-cloud-pc.md

@@ -20,7 +20,7 @@ ms.assetid:
 #ROBOTS:
 #audience:
 
-ms.reviewer: alcort
+ms.reviewer: ivivano
 ms.suite: ems
 search.appverid: MET150
 #ms.tgt_pltfrm:
@@ -75,7 +75,7 @@ For a list of clients by operating system, see [Remote Desktop clients](/windows
 
 To set up their Remote Desktop client, users follow these steps:
 
-1. Download the Remote Desktop app from the Download App page on [www.microsoft.com/windows-365?rtc=1](https://www.microsoft.com/windows-365?rtc=1).
+1. Download the Remote Desktop app from the [Remote Desktop clients page](/windows-server/remote/remote-desktop-services/clients/remote-desktop-clients).
 2. Select **Subscribe**.
 3. Enter their Azure Active Directory credentials.
 4. The Cloud PC appears in the list, and they can double-click it to launch.