From 58414d202a77b1c5c72563d3760b4b14cb45f79c Mon Sep 17 00:00:00 2001 From: Andre Della Monica Date: Mon, 1 May 2023 13:49:06 -0500 Subject: [PATCH] Changes --- .../windows-autopatch-groups-manage-autopatch-groups.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/windows/deployment/windows-autopatch/deploy/windows-autopatch-groups-manage-autopatch-groups.md b/windows/deployment/windows-autopatch/deploy/windows-autopatch-groups-manage-autopatch-groups.md index 22620399b9..c883c01bdd 100644 --- a/windows/deployment/windows-autopatch/deploy/windows-autopatch-groups-manage-autopatch-groups.md +++ b/windows/deployment/windows-autopatch/deploy/windows-autopatch-groups-manage-autopatch-groups.md @@ -36,6 +36,8 @@ Before you start managing Autopatch groups, ensure you’ve met the following pr - Windows Autopatch – Ring2 - Windows Autopatch – Ring3 - Windows Autopatch – Last +- Additionally, **don't** modify the Azure AD group ownership of any of the groups above otherwise, Autopatch groups device registration process won't be able to add devices into these groups. + - See [assign an owner of member of a group in Azure AD](https://learn.microsoft.com/azure/active-directory/privileged-identity-management/groups-assign-member-owner#assign-an-owner-or-member-of-a-group) for more details on how to remediate Azure Azure AD group ownership. - Make sure you have [app-only auth turned on in your Windows Autopatch tenant](../operate/windows-autopatch-maintain-environment.md#windows-autopatch-tenant-actions). Otherwise, the Autopatch groups functionality won’t work properly. Autopatch uses app-only auth to: - Read device attributes to successfully register devices. - Manage all configurations related to the operation of the service. @@ -43,6 +45,9 @@ Before you start managing Autopatch groups, ensure you’ve met the following pr - Review your existing Azure AD group dynamic queries and direct device memberships to avoid having device membership overlaps in between device-based Azure AD groups that are going to be used with Autopatch groups. This can help prevent device conflicts within an Autopatch group or across several Autopatch groups. **Autopatch groups doesn't support user-based Azure AD groups**. - Ensure devices used with your existing Azure AD groups meet [device registration prerequisite checks](../deploy/windows-autopatch-register-devices.md#prerequisites-for-device-registration) when being registered with the service. Autopatch groups register devices on your behalf, and devices can be moved to **Registered** or **Not registered** tabs in the Devices blade accordingly. +> [!TIP] +> During the public preview, Autopatch groups opt-in page will show a banner to let you know when one or more pre-requisites are failing. Once you remediate the issue to meet the pre-requisites, it can take up to an hour for your tenant to have the "Use preview" button active. + ## Create a Custom Autopatch group > [!NOTE]