Skip to content

Commit

Permalink
Merge pull request #16141 from MicrosoftDocs/main
Browse files Browse the repository at this point in the history
Publish main to live, Monday 10:30AM PDT, 09/16
  • Loading branch information
Stacyrch140 authored Sep 16, 2024
2 parents 0b45bef + 76114ef commit 7203272
Showing 1 changed file with 7 additions and 4 deletions.
11 changes: 7 additions & 4 deletions windows-365/enterprise/create-provisioning-policy.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ keywords:
author: ErikjeMS
ms.author: erikje
manager: dougeby
ms.date: 10/17/2023
ms.date: 09/16/2024
ms.topic: how-to
ms.service: windows-365
ms.subservice: windows-365-enterprise
Expand Down Expand Up @@ -94,7 +94,7 @@ To select an ANC, follow these steps:
- **Custom image**: Choose **Select** > select an image from the list > **Select**. The page displays the list of images that you uploaded using the [Add device images](add-device-images.md) workflow.
4. Select **Next**.
5. On the **Configuration** page, under **Windows settings**, choose a **Language & Region**. The selected language pack is installed on Cloud PCs provisioned with this policy.
6. Optional. Select **Apply device name template** to create a Cloud PC naming template to use when naming all Cloud CPs that are provisioned with this policy. This naming template updates the NETBIOS name and doesn't affect the display name of the Cloud PC. When creating the template, follow these rules:
6. Optional. Select **Apply device name template** to create a Cloud PC naming template to use when naming all Cloud PCs that are provisioned with this policy. This naming template updates the NETBIOS name and doesn't affect the display name of the Cloud PC. When creating the template, follow these rules:
- Names must be between 5 and 15 characters.
- Names can contain letters, numbers, and hyphens.
- Names can't include blank spaces or underscores.
Expand All @@ -108,10 +108,13 @@ To select an ANC, follow these steps:
- ABC-%USERNAME:5%-%RAND:5%
7. Optional. Under **Additional services**, choose a service to be installed on Cloud PCs provisioned with this policy:
- **Windows Autopatch** is a cloud service that automates updates for Windows, Microsoft 365 Apps for enterprise, Microsoft Edge, and Microsoft Teams on both physical and virtual devices. For more information, see [What is What is Windows Autopatch?](/windows/deployment/windows-autopatch/overview/windows-autopatch-overview) and the [Windows Autopatch FAQ](https://go.microsoft.com/fwlink/?linkid=2200228).
- **Microsoft Managed Desktop** is a cloud service that helps with device deployment, service management and operations, and security. For more information, see [What is Microsoft Managed Desktop?](/managed-desktop/intro/).
- If you already have Windows Autopatch configured to manage your cloud PCs, this option replaces the existing policy. This replacement might disrupt any dynamic distribution that is already configured in Autopatch.
- When this option is selected, the system assigns devices to a new ring as the last ring of the Autopatch group.
- To manually enable dynamic distribution for your Cloud PCs, modify your Autopatch Groups dynamic distribution list to include the Entra ID group to which your Cloud PCs are being added.
- **None**. Manage and update Cloud PCs manually.
8. Select **Next**.
9. On the **Assignments** page, choose **Select groups** > choose the groups you want this policy assigned to > **Select**. Nested groups aren't currently supported.
10. For Windows 365 Frontline, you must also select a Cloud PC size for each group in the policy. Choose **Select one** > select a size under **Available sizes** > **Select**. After you've selected a size for each group, select **Next**.
10. For Windows 365 Frontline, you must also select a Cloud PC size for each group in the policy. Choose **Select one** > select a size under **Available sizes** > **Select**. After you select a size for each group, select **Next**.
11. On the **Review + create** page, select **Create**. If you used Microsoft Entra hybrid join as the join type, it can take up to 60 minutes for the policy creation process to complete. The time depends on when the Microsoft Entra Connect sync last happened.

After the provisioning policy is created and assigned, Windows 365 automatically starts to provision Cloud PCs and assigns them to users in the assigned groups.
Expand Down

0 comments on commit 7203272

Please sign in to comment.