Merge pull request #6686 from MicrosoftDocs/main

Publish 02/01/2022 3:30 PM PT

Author: Angela Fleischmann

memdocs/autopilot/autopilot-device-guidelines.md

@@ -12,7 +12,7 @@ author: greg-lindsay
 ms.author: greglin
 ms.reviewer: jubaptis
 manager: dougeby
-ms.date: 12/16/2020
+ms.date: 2/1/2022
 ms.collection: M365-modern-desktop
 ms.topic: troubleshooting
 ---
@@ -36,7 +36,7 @@ The following best practices ensure that devices can easily be provisioned as pa
 - Before shipping devices to an Autopilot customer or channel partner, the OEM should upload 4K Hardware Hashes to Microsoft by using the CBR report. The hashes should be collected using the OA3 Tool RS3+ run in Audit mode on full OS.
 - Microsoft requires that OEM shipping drivers get published to Windows Update within 30 days of the CBR submission date. System firmware and driver updates are published to Windows Update within 14 days.
 - The OEM ensures that the PKID provisioned in the SMBIOS is passed on to the channel.
-- When using a VM for Autopilot testing, assign at least 2 processors and 4gb of memory. This will help to prevent application install issues in Windows 10 devices with the [May 11, 2021 cumulative update](https://support.microsoft.com/topic/may-11-2021-kb5003173-os-builds-19041-985-19042-985-and-19043-985-2824ace2-eabe-4c3c-8a49-06e249f52527) installed. *Note: The [minimum system requirements](/windows/whats-new/windows-11-requirements#virtual-machine-support) for Windows 11 are 2 processors and 4gb memory.
+- When using a VM for Autopilot testing, assign at least 2 processors and 4gb of memory. *Note: The [minimum system requirements](/windows/whats-new/windows-11-requirements#virtual-machine-support) for Windows 11 are 2 processors and 4gb memory.
 
 ## Software best practice guidelines for Windows Autopilot
 

memdocs/intune/apps/apps-deploy.md

@@ -96,6 +96,9 @@ The following table lists the various options for *assigning* apps to users and
 
 The app is now assigned to the groups that you selected. For more information about including and excluding app assignments, see [Include and exclude app assignments](apps-inc-exl-assignments.md).
 
+> [!Tip]
+> Intune supports assigning apps to nested groups too. For example, if you assigned an app to the "Enineering Global" group and have "Engineering APAC", "Engineering EMEA" and "Engineering US" nested as child groups, the members of those child groups will also be targeted with the assignment.
+
 ## How conflicts between app intents are resolved
 
 A single group is prevented from being targeted for multiple app assignment intents, however if a user or a device is a member of multiple groups that are each assigned with different intents it will result in a conflict. Creating assignment conflicts for applications is not recommended.

memdocs/intune/enrollment/android-fully-managed-enroll.md

@@ -46,7 +46,7 @@ You must have an Intune standalone tenant to manage Android Enterprise fully man
 
 Devices must meet these requirements to be managed as an Android Enterprise fully managed device:
 
-- Android OS version 6.0 and above.
+- Android OS version 8.0 and above.
 - Devices must run a build of Android that has Google Mobile Services (GMS) connectivity. Devices must have GMS available and must be able to connect to GMS.
 
 There is no restriction on device manufacturer/OEM if the above requirements are met.
@@ -75,4 +75,4 @@ You can now [enroll your fully managed devices](android-dedicated-devices-fully-
 
 ## Next steps
 - [Add Android Enterprise fully managed device configuration policies](../configuration/device-restrictions-android-for-work.md#fully-managed-dedicated-and-corporate-owned-work-profile)
-- [Configure app configuration policies for Android Enterprise fully managed devices](../apps/app-configuration-policies-use-android.md)
+- [Configure app configuration policies for Android Enterprise fully managed devices](../apps/app-configuration-policies-use-android.md)

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

@@ -7,7 +7,7 @@ keywords:
 author: ErikjeMS  
 ms.author: erikje
 manager: dougeby
-ms.date: 02/07/2022
+ms.date: 08/02/2021
 ms.topic: how-to
 ms.service: cloudpc
 ms.subservice:
@@ -52,7 +52,6 @@ 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 drop down. 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: 02/07/2022
+ms.date: 08/02/2021
 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**, **Configuration**, and **Assignments** by selecting **Edit** next to each header.
+2. On the policy page, you can edit the **General** information, **Image**, 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

@@ -7,7 +7,7 @@ keywords:
 author: ErikjeMS  
 ms.author: erikje
 manager: dougeby
-ms.date: 02/07/2022
+ms.date: 09/03/2021
 ms.topic: how-to
 ms.service: cloudpc
 ms.subservice:
@@ -32,31 +32,14 @@ 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.
 
-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.
-
-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:
+To provide a localized Windows experience when users first sign in, there are two 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.
 
@@ -65,7 +48,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:
 
@@ -78,18 +61,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.