From 355de9f8b9066eff923416011eea5d063493decb Mon Sep 17 00:00:00 2001 From: Andre Della Monica Date: Fri, 5 May 2023 18:01:21 -0500 Subject: [PATCH 1/5] Changes --- .../windows-autopatch-groups-manage-autopatch-groups.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) 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 2eed6eee26..3829c25f13 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 @@ -127,7 +127,7 @@ You **can’t** delete the Default Autopatch group. However, you can delete a Cu > [!IMPORTANT] > The Windows Autopatch groups functionaliy is in **public preview**. This feature is being actively developed and not all device conflict detection and resolution scenarios are working as expected. -> Fore more information on what to expect for this scenario during public preview, see [Known issues](#known-issues). +> For more information on what to expect for this scenario during public preview, see [Known issues](#known-issues). Overlap in device membership is a common scenario when working with device-based Azure AD groups since sometimes dynamic queries can be large in scope or the same assigned device membership can be used across different Azure AD groups. @@ -190,6 +190,12 @@ The Windows Autopatch team is aware that all device conflict scenarios listed be - Device conflict detection and resolution within an Autopatch group. - Custom to Cstom Autopatch group device conflict detection. +> [!TIP] +> Follow these two best practices to minimize device conflict scenarios when using Autopatch groups during the public preview: +> +> - Review your software update deployment requirements thoroughly, and if your deployment requirements allow, try using the default Autopatch group as much as possible, instead of start creating custom Autopatch groups. You can customize the default Autopatch to have up to 15 deployment rings, and using your existing device-based Azure AD groups with custom update deployment cadences. +> - If creating custom Autopatch groups, try to avoid using device-based Azure AD groups that have device membership overlaps with the devices that are already registered with the Windows Autopatch service, and already belong to the default Autopatch group. + ### Autopatch group Azure AD group remediator - **Status: Active** From 3d125559793f81b405514f2e77a1da2225379cd9 Mon Sep 17 00:00:00 2001 From: Andre Della Monica Date: Fri, 5 May 2023 18:06:44 -0500 Subject: [PATCH 2/5] Changes --- .../deploy/windows-autopatch-groups-manage-autopatch-groups.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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 3829c25f13..44b449f3c7 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 @@ -191,7 +191,7 @@ The Windows Autopatch team is aware that all device conflict scenarios listed be - Custom to Cstom Autopatch group device conflict detection. > [!TIP] -> Follow these two best practices to minimize device conflict scenarios when using Autopatch groups during the public preview: +> Follow these two best practices to help minimize device conflict scenarios when using Autopatch groups during the public preview: > > - Review your software update deployment requirements thoroughly, and if your deployment requirements allow, try using the default Autopatch group as much as possible, instead of start creating custom Autopatch groups. You can customize the default Autopatch to have up to 15 deployment rings, and using your existing device-based Azure AD groups with custom update deployment cadences. > - If creating custom Autopatch groups, try to avoid using device-based Azure AD groups that have device membership overlaps with the devices that are already registered with the Windows Autopatch service, and already belong to the default Autopatch group. From 15902826a416b3d028c8700c20530a21a3c56359 Mon Sep 17 00:00:00 2001 From: Andre Della Monica Date: Fri, 5 May 2023 18:10:13 -0500 Subject: [PATCH 3/5] Changes --- .../deploy/windows-autopatch-groups-manage-autopatch-groups.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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 44b449f3c7..0e01af10eb 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 @@ -193,7 +193,7 @@ The Windows Autopatch team is aware that all device conflict scenarios listed be > [!TIP] > Follow these two best practices to help minimize device conflict scenarios when using Autopatch groups during the public preview: > -> - Review your software update deployment requirements thoroughly, and if your deployment requirements allow, try using the default Autopatch group as much as possible, instead of start creating custom Autopatch groups. You can customize the default Autopatch to have up to 15 deployment rings, and using your existing device-based Azure AD groups with custom update deployment cadences. +> - Review your software update deployment requirements thoroughly, and if your deployment requirements allow, try using the default Autopatch group as much as possible, instead of start creating custom Autopatch groups. You can customize the default Autopatch to have up to 15 deployment rings, and you can use your existing device-based Azure AD groups with custom update deployment cadences. > - If creating custom Autopatch groups, try to avoid using device-based Azure AD groups that have device membership overlaps with the devices that are already registered with the Windows Autopatch service, and already belong to the default Autopatch group. ### Autopatch group Azure AD group remediator From fbbfabfedf8683cdeec1e17abb883f1c0be754a1 Mon Sep 17 00:00:00 2001 From: Arnab Mitra <38724550+msarnabm@users.noreply.github.com> Date: Sat, 6 May 2023 14:02:13 -0500 Subject: [PATCH 4/5] Fixing typo in Custom to Cstom FYI @andredm7 --- .../deploy/windows-autopatch-groups-manage-autopatch-groups.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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 2eed6eee26..7776ca2706 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 @@ -188,7 +188,7 @@ The Windows Autopatch team is aware that all device conflict scenarios listed be - Default to Custom Autopatch device conflict detection and resolution. - Device conflict detection and resolution within an Autopatch group. -- Custom to Cstom Autopatch group device conflict detection. +- Custom to Custom Autopatch group device conflict detection. ### Autopatch group Azure AD group remediator From 22df2b95142394eb5a351868331666903ad077da Mon Sep 17 00:00:00 2001 From: Tiara Quan <95256667+tiaraquan@users.noreply.github.com> Date: Mon, 8 May 2023 07:32:03 -0700 Subject: [PATCH 5/5] Update windows-autopatch-groups-manage-autopatch-groups.md --- .../windows-autopatch-groups-manage-autopatch-groups.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) 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 0e01af10eb..cb21c2f54e 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 @@ -191,10 +191,10 @@ The Windows Autopatch team is aware that all device conflict scenarios listed be - Custom to Cstom Autopatch group device conflict detection. > [!TIP] -> Follow these two best practices to help minimize device conflict scenarios when using Autopatch groups during the public preview: +> Use the following two best practices to help minimize device conflict scenarios when using Autopatch groups during the public preview: > -> - Review your software update deployment requirements thoroughly, and if your deployment requirements allow, try using the default Autopatch group as much as possible, instead of start creating custom Autopatch groups. You can customize the default Autopatch to have up to 15 deployment rings, and you can use your existing device-based Azure AD groups with custom update deployment cadences. -> - If creating custom Autopatch groups, try to avoid using device-based Azure AD groups that have device membership overlaps with the devices that are already registered with the Windows Autopatch service, and already belong to the default Autopatch group. +> - Review your software update deployment requirements thoroughly. If your deployment requirements allow, try using the Default Autopatch group as much as possible, instead of start creating Custom Autopatch groups. You can customize the Default Autopatch to have up to 15 deployment rings, and you can use your existing device-based Azure AD groups with custom update deployment cadences. +> - If creating Custom Autopatch groups, try to avoid using device-based Azure AD groups that have device membership overlaps with the devices that are already registered with Windows Autopatch, and already belong to the Default Autopatch group. ### Autopatch group Azure AD group remediator