Merge branch 'release-intune-2207' of https://github.com/microsoftdocs/memdocs-pr into erikre-wn2207-14955687

Author: Erikre

memdocs/intune/enrollment/android-samsung-knox-mobile-enroll.md

@@ -134,7 +134,7 @@ Still need help? Check out the complete [KME User Guide](https://docs.samsungkno
 
 - **Device Owner support:** Intune supports enrolling Dedicated and Fully Managed devices by using the KME portal. Other Android enterprise device owner modes will be supported as they become available in Intune.
 
-- **Work profile support:** KME is a corporate device enrollment method and devices enrolled in Android personally-owned work profile ensure work and personal data are separate on personal devices. Device enrollment to personally-owned work profile using KME is a supported scenario in Intune.
+- **Work profile support:** KME is a corporate device enrollment method and devices enrolled in Android personally-owned work profile ensure work and personal data are separate on personal devices. Device enrollment to personally-owned work profile using KME is not a supported scenario in Intune.
 
 - **Factory reset to enroll to Android enterprise:** If repurposing devices that have already been set up, devices need to be factory reset when enrolling to Android Enterprise.
 

windows-365/enterprise/known-issues-enterprise.md

@@ -83,7 +83,11 @@ The following device compliance settings may report as **Not Compliant** when be
 - **Require BitLocker**
 - **Require Secure Boot to be enabled on the device.** Cloud PC support for [Secure boot](/windows-hardware/design/device-experiences/oem-secure-boot) functionality is now available to all customers.
 
-**Troubleshooting steps**:
+**Troubleshooting steps to enable secure boot on the Cloud PC**:
+
+1. [Reprovision](reprovision-cloud-pc.md) the specific Cloud PC.
+
+**Troubleshooting steps to remove not compliant settings**:
 
 1. [Create a filter for all Cloud PCs](create-filter.md#create-a-filter-for-all-cloud-pcs).
 2. For any existing device compliance policies that both evaluate to a Cloud PC and contain either of the **Not Compliant** settings, use this new filter to exclude Cloud PCs from the policy assignment.

windows-365/enterprise/whats-new.md

@@ -68,7 +68,7 @@ You can now choose the **Windows 11 Enterprise + OS Optimizations** image when c
 <!-- vvvvvvvvvvvvvvvvvvvvvv -->
 ### Device provisioning
 
-### Provision Cloud PCs with Secure Boot<!--38012584-->
+#### Provision Cloud PCs with Secure Boot<!--38012584-->
 
 Support for creating Cloud PCs that use [Secure boot](/windows-hardware/design/device-experiences/oem-secure-boot) functionality is now available in Europe, APAC, and North American regions. Existing Cloud PCs won't have secure boot automatically enabled.