Merge pull request #7984 from MicrosoftDocs/main

merge main to Live Tuesday 10:30

Author: jborsecnik

memdocs/configmgr/core/clients/manage/cmg/plan-cloud-management-gateway.md

@@ -157,6 +157,8 @@ With a few exceptions, the configuration, operation, and functionality of the CM
 
 - A [**server authentication certificate**](server-auth-cert.md) for the CMG.
 
+- CMG names need to be between 3-24 alphanumeric characters. The name must begin with a letter, end with a letter or digit, and not contain consecutive hyphens. <!--13222041-->
+
 - **Other certificates** may be required, depending upon your client OS version and authentication model. For more information, see [Configure client authentication](configure-authentication.md).
 
 - Clients must use **IPv4**.

memdocs/configmgr/core/clients/manage/cmg/supported-configurations.md

@@ -2,7 +2,7 @@
 title: Supported configurations for CMG
 titleSuffix: Configuration Manager
 description: A list of the features and configurations that the Configuration Manager cloud management gateway supports.
-ms.date: 04/08/2022
+ms.date: 07/12/2022
 ms.prod: configuration-manager
 ms.technology: configmgr-client
 ms.topic: reference
@@ -30,6 +30,8 @@ Use this article as a reference for the features and configurations that are sup
 
 - Starting in version 2203, the option to deploy a CMG as a **cloud service (classic)** is removed.<!-- 13235079 --> All CMG deployments should use a [virtual machine scale set](plan-cloud-management-gateway.md#virtual-machine-scale-sets).<!--10966586--> For more information, see [Removed and deprecated features](../../../plan-design/changes/deprecated/removed-and-deprecated-cmfeatures.md).
 
+- CMG names need to be between 3-24 alphanumeric characters. The name must begin with a letter, end with a letter or digit, and not contain consecutive hyphens. <!--13222041-->
+
 ## Support for Configuration Manager features
 
 The following table lists CMG support for Configuration Manager features:

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

@@ -6,7 +6,7 @@ f1.keywords:
 ms.author: erikje
 author: ErikjeMS
 manager: dougeby
-ms.date: 06/13/2022
+ms.date: 07/12/2022
 audience: Admin
 ms.topic: troubleshooting
 ms.service: cloudpc
@@ -44,6 +44,15 @@ While a Windows PC (physical or Cloud PC) sits idle before the first user signs
 
  **Troubleshooting steps**: Make sure that a user signs in to new Cloud PCs as soon as possible.
 
+## Windows 10 to 11 in-place upgrade failure<!--40412134-->
+
+Upgrading an existing Cloud PC from Windows 10 to Windows 11 using the Settings app may fail.
+
+## Troubleshooting steps
+
+1. Edit the related provisioning policy to change the gallery image to Windows 11.
+2. Reprovision the Cloud PC.
+
 ## Windows 365 provisioning fails<!--38483005-->
 
 Windows 365 provisioning failures may occur because both: