Merge pull request #6635 from ErikjeMS/win365rel2201

Win365rel2201

Author: Angela Fleischmann

windows-365/enterprise/create-provisioning-policy.md

@@ -7,7 +7,7 @@ keywords:
 author: ErikjeMS  
 ms.author: erikje
 manager: dougeby
-ms.date: 08/02/2021
+ms.date: 02/07/2022
 ms.topic: how-to
 ms.service: cloudpc
 ms.subservice:
@@ -52,6 +52,7 @@ A few things to keep in mind:
     - **Gallery image**: Choose **Select** > select an image from the gallery > **Select**. Gallery images are default images provided for your use.
     - **Custom image**:  Choose **Select** > select an image from the list > **Select**. This will show the list of images that you uploaded using the [Add device images](add-device-images.md) workflow.
 1. Select **Next**.
+1.	On the **Configuration** page, choose a language pack in the dropdown. The selected language pack will be installed on Cloud PCs provisioned with this policy. Select **Next**.
 1. On the **Assignments** page, choose **Select groups** > choose the groups you want this policy assigned to > **Select** > **Next**.
 1. On the **Review + create** page, select **Create**. It can take up to 60 minutes for the policy creation process to complete, depending on when the Azure AD connect sync last happened.
 

windows-365/enterprise/edit-provisioning-policy.md

@@ -7,7 +7,7 @@ keywords:
 author: ErikjeMS  
 ms.author: erikje
 manager: dougeby
-ms.date: 08/02/2021
+ms.date: 02/07/2022
 ms.topic: how-to
 ms.service: cloudpc
 ms.subservice:
@@ -34,7 +34,7 @@ You can update provisioning policies to change assignments or key attributes, li
 
 1. Sign in to the [Microsoft Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431), select **Devices** > **Windows 365** (under **Provisioning**) > **Provisioning policies** > select a policy.
 ![Screenshot of edit policy](./media/edit-provisioning-policy/edit-policy.png)
-2. On the policy page, you can edit the **General** information, **Image**, and **Assignments** by selecting **Edit** next to each header.
+2. On the policy page, you can edit the **General** information, **Image**, **Configuration**, and **Assignments** by selecting **Edit** next to each header.
 
 If you change the on-premises network connection or image in a provisioning policy, no change will occur for previously provisioned Cloud PCs. Newly provisioned Cloud PCs will honor the changes in your provisioning policy. To change the previously provisioned Cloud PCs to align with the changes, you must reprovision those Cloud PCs.
 

windows-365/enterprise/provide-localized-windows-experience.md

@@ -2,12 +2,12 @@
 # required metadata
 title: Provide users a localized Windows experience on their Cloud PC
 titleSuffix:
-description: Learn how to provide a localized Windows experience for your end-users.
+description: Learn how to provide a localized Windows experience for your end users.
 keywords:
 author: ErikjeMS  
 ms.author: erikje
 manager: dougeby
-ms.date: 09/03/2021
+ms.date: 02/07/2022
 ms.topic: how-to
 ms.service: cloudpc
 ms.subservice:
@@ -32,14 +32,31 @@ ms.collection: M365-identity-device-management
 
 For users to be productive on their Windows 365 Cloud PC, it's important for Windows to use a display language that they're comfortable with. Users can always change the display language themselves through the Settings app in Windows. But the Windows experience is more welcoming if the user sees the right language immediately, starting when they first sign in.
 
-To provide a localized Windows experience when users first sign in, there are two steps:
+There are two different ways to provide a localized Windows experience when users first sign in:
+
+- Configure a provisioning policy
+- Create a custom device image
+
+## Configure a provisioning policy
+
+To make sure that the correct language packs are available on the Cloud PC at first sign-in, you can configure a provisioning policy:
+
+- [Create a provisioning policy](create-provisioning-policy.md) and choose a **Language & Region pack** under **Configuration**. There are 38 Windows language packs available for Windows 365. Windows 365 will automatically use the default local keyboard layout for the language pack. 
+
+All Cloud PCs provisioned with this policy will have the chosen language pack at the first sign-in experience.
+
+You can also [edit provisioning policies](edit-provisioning-policy.md) to change the Language & Region configuration. After saving the policy and [reprovisioning](reprovision-cloud-pc.md) the associated Cloud PCs, the chosen language pack will be on the Cloud PCs.
+
+## Create a custom device image
+
+To create a custom device image that gives users a localized Windows experience, follow these steps:
 
 1. [Create a custom device image with the languages installed](#create-a-custom-image-with-the-languages-installed).
 2. [Configure the default language using Group Policy](#configure-the-default-language-using-group-policy).
 
 Cloud PCs provisioned from this image will be fully configured to work in any of the installed languages, without any user action. When the user signs in to the Cloud PC, Group Policy will evaluate the device and set the appropriate pre-installed language as the user's preferred language for Windows.
 
-## Create a custom image with the languages installed
+### Create a custom image with the languages installed
 
 Creating a custom image with the languages installed is the best way to make sure that the desired languages are available on the Cloud PC when the user signs in.
 
@@ -48,7 +65,7 @@ Before starting the custom image process, check if your language is supported by
 - The language you want to provide for your users is supported by the PowerShell script, follow the steps to [Add languages to Windows using a script and capture the image](#add-languages-to-windows-using-a-script-and-capture-the-image). Windows 10 custom images only.
 - The language you want to provide for your users isn't supported by the PowerShell script, follow the steps to [Add languages to Windows manually and capture the image](#add-languages-to-windows-manually-and-capture-the-image).
 
-### Add languages to Windows using a script and capture the image
+#### Add languages to Windows using a script and capture the image
 
 To add a language using the [Windows 365 Language Installer](https://www.powershellgallery.com/packages/Windows365LanguagesInstaller/1.0.0.0) script:
 
@@ -61,18 +78,18 @@ To add a language using the [Windows 365 Language Installer](https://www.powersh
 
 After you're done adding the desired languages and are ready to capture the image, follow the steps to [finish customizing your image](/azure/virtual-desktop/language-packs#finish-customizing-your-image).
 
-### Add languages to Windows manually and capture the image
+#### Add languages to Windows manually and capture the image
 
 To manually install the desired languages to your Windows 10/11 Enterprise custom image, follow the steps in [Add language packs to a Windows 10/11 multi-session image](/azure/virtual-desktop/language-packs) up to and including [finish customizing your image](/azure/virtual-desktop/language-packs#finish-customizing-your-image).
 
 > [!NOTE]
 > Though these instructions are written specifically for Windows 10/11 Enterprise multi-session, these same steps apply to Windows 10/11 Enterprise.
 
-### Upload the custom image
+#### Upload the custom image
 
 To upload the custom image to the Windows 365 service, after you've captured the image as an Azure managed image, follow the steps in [Add or delete device images](add-device-images.md).
 
-## Configure the default language using Group Policy
+### Configure the default language using Group Policy
 
 Now that the languages are installed on the image that users will receive, you must create a Group Policy to apply the correct pre-installed language as the default for your users.
 
@@ -83,7 +100,7 @@ The following steps configure [Group Policy Preferences](/previous-versions/wind
 3. In Server Manager, open **Group Policy Management** and create a new Group Policy object linked to the Organization Unit (OU) or domain that will contain the Cloud PCs for those users.
 4. Right-click the new Group Policy object, and select **Edit...**
 5. Navigate to **User Configuration** > **Preferences** > **Windows Settings**, right-click **Registry**, and select **New** > **Registry Item**.
-6. Enter the following details in the **General** tab. Here is an example that shows Spanish (Spain) with language code es-ES:
+6. Enter the following details in the **General** tab. Here's an example that shows Spanish (Spain) with language code es-ES:
     - Action: Replace
     - Hive: HKEY_CURRENT_USER
     - Key Path: Control Panel\Desktop
@@ -102,7 +119,7 @@ The following steps configure [Group Policy Preferences](/previous-versions/wind
 9. Select **...** next to the Group, search for the new security group, select the new security group, and hit **OK**.
 10. Select **User in group**, then select **OK** and **OK** to complete the new registry process.
 11. In the "Group Policy Management Editor", navigate to **User Configuration** > **Preferences** > **Control Panel Settings**, right-click **Regional Options**, and select **New** > **Regional Options**.
-12. Under **User Locale**, select the language and region combination that matches the registry key you created above.
+12. Under **User Locale**, select the language and region combination that matches the registry key you created in a previous step.
 13. After selecting your desired language and region combination from the dropdown, the dropdown menu may be underlined in red. This indicates that the selection isn't confirmed. Press the **F5** function key on your keyboard to confirm the selection, resulting in a green underlined dropdown menu.
 
     Before hitting **F5**: