From 263697a27f06e875e9b517f45f9ec748b122a754 Mon Sep 17 00:00:00 2001 From: tiaraquan Date: Tue, 5 Jul 2022 21:13:56 -0700 Subject: [PATCH] Updating as per Adam Nichols W365 update. --- .../windows-autopatch-register-devices.md | 38 ++++++++++++++++++- .../overview/windows-autopatch-faq.yml | 6 +++ 2 files changed, 43 insertions(+), 1 deletion(-) diff --git a/windows/deployment/windows-autopatch/deploy/windows-autopatch-register-devices.md b/windows/deployment/windows-autopatch/deploy/windows-autopatch-register-devices.md index f6dc54cf8d..28cf8a2491 100644 --- a/windows/deployment/windows-autopatch/deploy/windows-autopatch-register-devices.md +++ b/windows/deployment/windows-autopatch/deploy/windows-autopatch-register-devices.md @@ -111,7 +111,9 @@ Registering your devices in Windows Autopatch does the following: ## Steps to register devices -**To register devices into Windows Autopatch:** +### Physical devices + +**To register physical devices into Windows Autopatch:** 1. Go to the [Microsoft Endpoint Manager admin center](https://endpoint.microsoft.com/). 2. Select **Windows Autopatch** from the left navigation menu. @@ -127,6 +129,40 @@ Once devices or Azure AD groups containing devices are added to the **Windows Au > [!IMPORTANT] > It might take up to an hour for a device to change its status from **Ready for User** to **Active** in the Ready tab during the public preview. +### Virtual devices + +#### Windows Autopatch on Windows 365 Enterprise Workloads + +With Windows 365 Enterprise, you can include Windows Autopatch onboarding as part of your provision process providing a seamless experience for admins and users to ensure your Cloud PCs are always up to date. + +#### Deploy Windows Autopatch on a Windows 365 Provisioning Policy + +For general guidance, see [Create a Windows 365 Provisioning Policy](/windows-365/enterprise/create-provisioning-policy). + +**To deploy Windows Autopatch on a Windows 365 Provisioning Policy:** + +1. Go to the [Microsoft Endpoint Manager](https://endpoint.microsoft.com/) admin center. +1. In the left pane, select **Devices**. +1. Navigate to Provisioning > **Windows 365**. +1. Select Provisioning policies > **Create policy**. +1. Provide a policy name and select **Join Type**. For more information, see [Device join types](/windows-365/enterprise/identity-authentication#device-join-types). +1. Select **Next**. +1. Choose the desired image and select **Next**. +1. Under the **Microsoft managed services** section, select **Windows Autopatch**. Then, select **Next**. If the *Windows Autopatch (preview) cannot manage your Cloud PCs until a Global Admin has finished setting it up.* message appears, you must [enroll your tenant](../prepare/windows-autopatch-enroll-tenant.md) to continue. +1. Assign your policy accordingly and select **Next**. +1. Select **Create**. Now your newly provisioned Windows 365 Enterprise Cloud PCs will automatically be enrolled and managed by Windows Autopatch. + +#### Deploy Autopatch on Windows 365 for existing Cloud PC + +All your existing Windows 365 Enterprise workloads can be registered into Windows Autopatch by leveraging the same method as your physical devices. For more information, see [Physical devices](#physical-devices). + +#### Contact support + +Support is available either through Windows 365, or Windows Autopatch for update related incidents. + +- For Windows 365 support, see [Get support](/mem/get-support). +- For Windows Autopatch support, see [Submit a support request](/windows/deployment/windows-autopatch/operate/windows-autopatch-support-request). + ## Device management lifecycle scenarios There's a few more device lifecycle management scenarios to consider when planning to register devices in Windows Autopatch. diff --git a/windows/deployment/windows-autopatch/overview/windows-autopatch-faq.yml b/windows/deployment/windows-autopatch/overview/windows-autopatch-faq.yml index 3e968ceeab..5b27699c20 100644 --- a/windows/deployment/windows-autopatch/overview/windows-autopatch-faq.yml +++ b/windows/deployment/windows-autopatch/overview/windows-autopatch-faq.yml @@ -59,6 +59,12 @@ sections: - question: Can Autopatch customers individually approve or deny devices? answer: | No you can't individually approve or deny devices. Once a device is registered with Windows Autopatch, updates are rolled out to the devices according to its ring assignment. Individual device level control isn't supported. + - question: Does Autopatch on Widows 365 Cloud PCs have any feature difference from a physical device? + answer: | + No, Windows 365 Enterprise Cloud PC's support all features of Windows Autopatch. For more information, see [Virtual devices](/windows/deployment/windows-autopatch/deploy/windows-autopatch-register-devices#virtual-devices). + - question: Can I run Autopatch on my Windows 365 Business Workloads? + answer: | + No. Autopatch is only available on enterprise workloads. For more information, see [Virtual devices](/windows/deployment/windows-autopatch/deploy/windows-autopatch-register-devices#virtual-devices). - name: Update Management questions: - question: What systems does Windows Autopatch update?