Merge pull request #8077 from ErikjeMS/win365

change for secure boot

Author: PRMerger12

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

@@ -81,7 +81,7 @@ The following device compliance settings report as **Not applicable** when being
 The following device compliance settings may report as **Not Compliant** when being evaluated for a Cloud PC:
 
 - **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 rolling out in Asia Pacific (APAC) regions. This feature will roll out to all customers over the next few months.
+- **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**:
 

windows-365/enterprise/whats-new.md

@@ -70,7 +70,7 @@ You can now choose the **Windows 11 Enterprise + OS Optimizations** image when c
 
 ### 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 i snow available in Europe, APAC, and North American regions.
+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.
 
 <!-- ########################## -->
 ## Week of July 4, 2022 (Service release 2206)