deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-06-16 02:43:43 +00:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

Changes

Browse Source
This commit is contained in:
Andre Della Monica
2023-05-05 18:01:21 -05:00
parent 3eeca6ab2a
commit 355de9f8b9
1 changed files with 7 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
windows/deployment/windows-autopatch/deploy/windows-autopatch-groups-manage-autopatch-groups.md
View File

@ -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**