More changes

windows/deployment/windows-autopatch/deploy/windows-autopatch-device-registration-overview.md

@@ -1,7 +1,7 @@
 ---
 title: Device registration overview
 description: This article provides an overview on how to register devices in Autopatch
-ms.date: 05/01/2023
+ms.date: 05/02/2023
 ms.prod: windows-client
 ms.technology: itpro-updates
 ms.topic: conceptual

windows/deployment/windows-autopatch/deploy/windows-autopatch-groups-manage-autopatch-groups.md

@@ -1,7 +1,7 @@
 ---
 title: Manage Windows Autopatch groups
 description: This article explains how to manage Autopatch groups
-ms.date: 05/01/2023
+ms.date: 05/02/2023
 ms.prod: windows-client
 ms.technology: itpro-updates
 ms.topic: how-to
@@ -26,6 +26,16 @@ Autopatch groups is a logical container or unit that groups several [Azure AD gr
 Before you start managing Autopatch groups, ensure you’ve met the following prerequisites:
 
 - Review [Windows Autopatch groups overview documentation](../deploy/windows-autopatch-groups-overview.md) to understand [key benefits](../deploy/windows-autopatch-groups-overview.md#key-benefits), [concepts](../deploy/windows-autopatch-groups-overview.md#key-concepts) and [common ways to use Autopatch groups](../deploy/windows-autopatch-groups-overview.md#common-ways-to-use-autopatch-groups) within your organization.
+- Ensure the following [update rings for Windows 10 and later policy in Intune](https://learn.microsoft.com/mem/intune/protect/windows-10-update-rings) are created in your tenant:
+	- Modern Workplace Update Policy [Test]-[Windows Autopatch]
+	- Modern Workplace Update Policy [First]-[Windows Autopatch]
+	- Modern Workplace Update Policy [Fast]-[Windows Autopatch]
+	- Modern Workplace Update Policy [Broad]-[Windows Autopatch]
+- Ensure the following [feature updates for Windows 10 and later policy in Intune](https://learn.microsoft.com/mem/intune/protect/windows-10-feature-updates) are created in your tenant:
+	- Windows Autopatch – DSS Policy [Test]
+	- Windows Autopatch – DSS Policy [First]
+	- Windows Autopatch – DSS Policy [Fast]
+	- Windows Autopatch – DSS Policy [Broad]
 - Ensure the following Azure AD assigned groups are in your tenant before using Autopatch groups. **Don’t** modify the Azure AD group membership types (Assigned or Dynamic). Otherwise, the Windows Autopatch service won’t be able to read the device group membership from these groups and causes the Autopatch groups feature and other service-related operations to not work properly.
     - Modern Workplace Devices-Windows Autopatch-Test
     - Modern Workplace Devices-Windows Autopatch-First
@@ -45,9 +55,14 @@ 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]
+> [Update rings](https://learn.microsoft.com/mem/intune/protect/windows-10-update-rings) and [feature updates](https://learn.microsoft.com/mem/intune/protect/windows-10-feature-updates) for Windows 10 and later policies created and managed by the Windows Autopatch service can now be restored using the [Policy health](../operate/windows-autopatch-policy-health-and-remediation.md) feature. See [restore Windows update policies](../operate/windows-autopatch-policy-health-and-remediation.md#restore-windows-update-policies) for more information on remediation actions.
+
 > [!NOTE]
 > During the public preview, Autopatch groups opt-in page will show a banner to let you know when one or more prerequisites are failing. Once you remediate the issue to meet the prerequisites, it can take up to an hour for your tenant to have the "Use preview" button available.
 
+
+
 ## Create a Custom Autopatch group
 
 > [!NOTE]

windows/deployment/windows-autopatch/deploy/windows-autopatch-groups-overview.md

@@ -1,7 +1,7 @@
 ---
 title: Windows Autopatch groups overview
 description: This article explains what Autopatch groups are
-ms.date: 05/01/2023
+ms.date: 05/02/2023
 ms.prod: windows-client
 ms.technology: itpro-updates
 ms.topic: conceptual
@@ -247,4 +247,7 @@ Autopatch groups works with the following software update workloads:
 
 Windows Autopatch will support up to 50 Autopatch groups in your tenant. You can create up to 49 [Custom Autopatch groups](#about-custom-autopatch-groups) in addition to the [Default Autopatch group](#about-the-default-autopatch-group). Each Autopatch group supports up to 15 deployment rings.
 
+> [!TIP]
+> If you reach the maximum number of Autopatch groups supported (50), and try to create more custom Autopatch groups, the "**Create**" button in the Autopatch groups blade will be greyed out.
+
 To manage your Autopatch groups, see [Manage Windows Autopatch groups](../deploy/windows-autopatch-groups-manage-autopatch-groups.md).

windows/deployment/windows-autopatch/operate/windows-autopatch-groups-windows-feature-update-overview.md

@@ -39,6 +39,15 @@ Windows Autopatch’s device eligibility criteria for Windows feature updates al
 
 ## Key benefits
 
+- Windows Autopatch makes it easier and less expensive for you to keep your Windows devices up to date. You can focus on running your core businesses while Windows Autopatch runs update management on your behalf.
+- You’re in control of telling Windows Autopatch when your organization is ready to move to the next Windows OS version.
+	- Combined with custom releases, Autopatch Groups gives your organization great control and flexibility to help you plan your gradual rollout in a way that works for your organization.
+- Simplified end-user experience with rich controls for gradual rollouts, deployment cadence and speed.
+- No need to manually modify the default Windows feature update policies (default release) to be on the Windows OS version your organization is currently ready for.
+- Enables scenarios where you can deploy a single release across several Autopatch groups and its deployment rings.
+
+## Key concepts
+
 - A release is made of one or more deployment phases and contains the required OS version to be gradually rolled out throughout its deployment phases.
 - A phase (deployment phase) is made of one or more Autopatch group deployment rings. A phase:
     - Works as an additional layer of deployment cadence settings that can be defined by IT admins (only for Windows feature updates) on top of Autopatch group deployment rings (Windows update rings policies).