From 2868cfe7f75a9c28d2b64f10d49d9bb6019c7181 Mon Sep 17 00:00:00 2001 From: DocsPreview <49669258+DocsPreview@users.noreply.github.com> Date: Sun, 16 Apr 2023 23:54:58 -0700 Subject: [PATCH 01/17] Update check-release-health.md --- windows/deployment/update/check-release-health.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/windows/deployment/update/check-release-health.md b/windows/deployment/update/check-release-health.md index c73105ae1b..bb1a8ef402 100644 --- a/windows/deployment/update/check-release-health.md +++ b/windows/deployment/update/check-release-health.md @@ -54,6 +54,14 @@ To be informed about the latest updates and releases, follow [@WindowsUpdate](ht ![A screenshot showing issue details.](images/WRH-known-issue-detail.png) +## Sign up for email notifications + +You have the option to sign up for email notifications about Windows known issues and information updates, such as a change in status, new workarounds, and resolutions released. To subscribe, go to the [Windows release health page](https://admin.microsoft.com/Adminportal/Home?#/windowsreleasehealth), select **Preferences > Email**, click **Send me email notifications about Windows release health**, and then specify: +- Up to two email addresses. Each admin can set their Preferences. The limit of two email addresses is per admin account. +- Which Windows versions you want to be notified about. If your organization has multiple versions of Windows, we recommend selecting all that apply. +Lastly, don’t forget to click on **Save**. It might take up to 8 hours for these changes to take effect. +**Note:** If one known issue affects more than one version of Windows, you will receive only one email, even if you sign up for multiple Windows versions. We won’t send duplicate emails. + ## Status definitions In the **Windows release health** experience, every known issue is assigned as status. Those statuses are defined as follows: From 83bd2a0bc073a58d26a3666e796978cd2233304b Mon Sep 17 00:00:00 2001 From: DocsPreview <49669258+DocsPreview@users.noreply.github.com> Date: Mon, 17 Apr 2023 00:52:13 -0700 Subject: [PATCH 02/17] Update check-release-health.md --- windows/deployment/update/check-release-health.md | 1 + 1 file changed, 1 insertion(+) diff --git a/windows/deployment/update/check-release-health.md b/windows/deployment/update/check-release-health.md index bb1a8ef402..b14769c0b8 100644 --- a/windows/deployment/update/check-release-health.md +++ b/windows/deployment/update/check-release-health.md @@ -60,6 +60,7 @@ You have the option to sign up for email notifications about Windows known issue - Up to two email addresses. Each admin can set their Preferences. The limit of two email addresses is per admin account. - Which Windows versions you want to be notified about. If your organization has multiple versions of Windows, we recommend selecting all that apply. Lastly, don’t forget to click on **Save**. It might take up to 8 hours for these changes to take effect. + **Note:** If one known issue affects more than one version of Windows, you will receive only one email, even if you sign up for multiple Windows versions. We won’t send duplicate emails. ## Status definitions From df95c285b85691c1debaa090c66f3b40b7e264b5 Mon Sep 17 00:00:00 2001 From: Meghan Stewart <33289333+mestew@users.noreply.github.com> Date: Thu, 27 Apr 2023 08:42:44 -0700 Subject: [PATCH 03/17] Update windows/deployment/update/check-release-health.md --- windows/deployment/update/check-release-health.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/windows/deployment/update/check-release-health.md b/windows/deployment/update/check-release-health.md index b14769c0b8..c1f39d08e8 100644 --- a/windows/deployment/update/check-release-health.md +++ b/windows/deployment/update/check-release-health.md @@ -56,7 +56,11 @@ To be informed about the latest updates and releases, follow [@WindowsUpdate](ht ## Sign up for email notifications -You have the option to sign up for email notifications about Windows known issues and information updates, such as a change in status, new workarounds, and resolutions released. To subscribe, go to the [Windows release health page](https://admin.microsoft.com/Adminportal/Home?#/windowsreleasehealth), select **Preferences > Email**, click **Send me email notifications about Windows release health**, and then specify: +You have the option to sign up for email notifications about Windows known issues and informational updates. Notifications include changes in issue status, new workarounds, and issue resolutions. To subscribe to notifications: + +1. Go to the [Windows release health page](https://admin.microsoft.com/Adminportal/Home?#/windowsreleasehealth). +1. Select **Preferences** > **Email** then select **Send me email notifications about Windows release health**. +1. Specify the following information: - Up to two email addresses. Each admin can set their Preferences. The limit of two email addresses is per admin account. - Which Windows versions you want to be notified about. If your organization has multiple versions of Windows, we recommend selecting all that apply. Lastly, don’t forget to click on **Save**. It might take up to 8 hours for these changes to take effect. From 209d33c3ca182474ac91a29ca0b465f94420f4c5 Mon Sep 17 00:00:00 2001 From: Meghan Stewart <33289333+mestew@users.noreply.github.com> Date: Thu, 27 Apr 2023 08:42:51 -0700 Subject: [PATCH 04/17] Update windows/deployment/update/check-release-health.md --- windows/deployment/update/check-release-health.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/update/check-release-health.md b/windows/deployment/update/check-release-health.md index c1f39d08e8..93ee5ce2bc 100644 --- a/windows/deployment/update/check-release-health.md +++ b/windows/deployment/update/check-release-health.md @@ -62,7 +62,7 @@ You have the option to sign up for email notifications about Windows known issue 1. Select **Preferences** > **Email** then select **Send me email notifications about Windows release health**. 1. Specify the following information: - Up to two email addresses. Each admin can set their Preferences. The limit of two email addresses is per admin account. -- Which Windows versions you want to be notified about. If your organization has multiple versions of Windows, we recommend selecting all that apply. + - Windows versions to be notified about Lastly, don’t forget to click on **Save**. It might take up to 8 hours for these changes to take effect. **Note:** If one known issue affects more than one version of Windows, you will receive only one email, even if you sign up for multiple Windows versions. We won’t send duplicate emails. From ee853f9f1868fbef05296eb4e6174dd81f6bde4e Mon Sep 17 00:00:00 2001 From: Meghan Stewart <33289333+mestew@users.noreply.github.com> Date: Thu, 27 Apr 2023 08:42:57 -0700 Subject: [PATCH 05/17] Update windows/deployment/update/check-release-health.md --- windows/deployment/update/check-release-health.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/update/check-release-health.md b/windows/deployment/update/check-release-health.md index 93ee5ce2bc..f2a8b72d00 100644 --- a/windows/deployment/update/check-release-health.md +++ b/windows/deployment/update/check-release-health.md @@ -63,7 +63,7 @@ You have the option to sign up for email notifications about Windows known issue 1. Specify the following information: - Up to two email addresses. Each admin can set their Preferences. The limit of two email addresses is per admin account. - Windows versions to be notified about -Lastly, don’t forget to click on **Save**. It might take up to 8 hours for these changes to take effect. +1. Select **Save** when you're finished specifying email addresses and Windows versions. It may take up to 8 hours for these changes to take effect. **Note:** If one known issue affects more than one version of Windows, you will receive only one email, even if you sign up for multiple Windows versions. We won’t send duplicate emails. From f1db2b63a235aa3027ad7dda2636c59a446d0fb2 Mon Sep 17 00:00:00 2001 From: Meghan Stewart <33289333+mestew@users.noreply.github.com> Date: Thu, 27 Apr 2023 08:43:02 -0700 Subject: [PATCH 06/17] Update windows/deployment/update/check-release-health.md --- windows/deployment/update/check-release-health.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/windows/deployment/update/check-release-health.md b/windows/deployment/update/check-release-health.md index f2a8b72d00..57c9a29fb4 100644 --- a/windows/deployment/update/check-release-health.md +++ b/windows/deployment/update/check-release-health.md @@ -65,7 +65,8 @@ You have the option to sign up for email notifications about Windows known issue - Windows versions to be notified about 1. Select **Save** when you're finished specifying email addresses and Windows versions. It may take up to 8 hours for these changes to take effect. -**Note:** If one known issue affects more than one version of Windows, you will receive only one email, even if you sign up for multiple Windows versions. We won’t send duplicate emails. +> [!Note] +> When a single known issue affects multiple versions of Windows, you'll only receive one email notification, even if you've selected notifications for multiple versions. Duplicate emails won't be sent. ## Status definitions From 4086081f6d56947aa48af50162d55218631584e9 Mon Sep 17 00:00:00 2001 From: Meghan Stewart <33289333+mestew@users.noreply.github.com> Date: Thu, 27 Apr 2023 08:43:15 -0700 Subject: [PATCH 07/17] Update windows/deployment/update/check-release-health.md --- windows/deployment/update/check-release-health.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/windows/deployment/update/check-release-health.md b/windows/deployment/update/check-release-health.md index 57c9a29fb4..c11f9576cf 100644 --- a/windows/deployment/update/check-release-health.md +++ b/windows/deployment/update/check-release-health.md @@ -61,7 +61,8 @@ You have the option to sign up for email notifications about Windows known issue 1. Go to the [Windows release health page](https://admin.microsoft.com/Adminportal/Home?#/windowsreleasehealth). 1. Select **Preferences** > **Email** then select **Send me email notifications about Windows release health**. 1. Specify the following information: -- Up to two email addresses. Each admin can set their Preferences. The limit of two email addresses is per admin account. + - Email address for the notifications + -Each admin account can specify up to two email addresses under their email preferences - Windows versions to be notified about 1. Select **Save** when you're finished specifying email addresses and Windows versions. It may take up to 8 hours for these changes to take effect. From 4524005631d601b2d9a0ab58f82c9e4438f847b9 Mon Sep 17 00:00:00 2001 From: Meghan Stewart <33289333+mestew@users.noreply.github.com> Date: Thu, 27 Apr 2023 08:51:29 -0700 Subject: [PATCH 08/17] Update windows/deployment/update/check-release-health.md --- windows/deployment/update/check-release-health.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/update/check-release-health.md b/windows/deployment/update/check-release-health.md index c11f9576cf..1128f3e644 100644 --- a/windows/deployment/update/check-release-health.md +++ b/windows/deployment/update/check-release-health.md @@ -62,7 +62,7 @@ You have the option to sign up for email notifications about Windows known issue 1. Select **Preferences** > **Email** then select **Send me email notifications about Windows release health**. 1. Specify the following information: - Email address for the notifications - -Each admin account can specify up to two email addresses under their email preferences + - Each admin account can specify up to two email addresses under their email preferences - Windows versions to be notified about 1. Select **Save** when you're finished specifying email addresses and Windows versions. It may take up to 8 hours for these changes to take effect. From 5f2853513b787ffcbf756fad7286208069317d71 Mon Sep 17 00:00:00 2001 From: Meghan Stewart <33289333+mestew@users.noreply.github.com> Date: Thu, 27 Apr 2023 08:58:41 -0700 Subject: [PATCH 09/17] Update windows/deployment/update/check-release-health.md --- windows/deployment/update/check-release-health.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/update/check-release-health.md b/windows/deployment/update/check-release-health.md index 1128f3e644..c78b8d0dfb 100644 --- a/windows/deployment/update/check-release-health.md +++ b/windows/deployment/update/check-release-health.md @@ -59,7 +59,7 @@ To be informed about the latest updates and releases, follow [@WindowsUpdate](ht You have the option to sign up for email notifications about Windows known issues and informational updates. Notifications include changes in issue status, new workarounds, and issue resolutions. To subscribe to notifications: 1. Go to the [Windows release health page](https://admin.microsoft.com/Adminportal/Home?#/windowsreleasehealth). -1. Select **Preferences** > **Email** then select **Send me email notifications about Windows release health**. +1. Select **Preferences** > **Email**, then select **Send me email notifications about Windows release health**. 1. Specify the following information: - Email address for the notifications - Each admin account can specify up to two email addresses under their email preferences From 68a12d9c507c69242054a401c926bf2f59c1d334 Mon Sep 17 00:00:00 2001 From: Meghan Stewart <33289333+mestew@users.noreply.github.com> Date: Thu, 27 Apr 2023 13:51:47 -0700 Subject: [PATCH 10/17] edits --- windows/deployment/update/check-release-health.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/windows/deployment/update/check-release-health.md b/windows/deployment/update/check-release-health.md index c78b8d0dfb..5504be6122 100644 --- a/windows/deployment/update/check-release-health.md +++ b/windows/deployment/update/check-release-health.md @@ -1,7 +1,7 @@ --- title: How to check Windows release health description: Check the release health status of Microsoft 365 services before you call support to see if there's an active service interruption. -ms.date: 08/16/2022 +ms.date: 05/03/2023 ms.author: mstewart author: mestew manager: aaroncz @@ -13,7 +13,7 @@ ms.technology: itpro-updates # How to check Windows release health -The Windows release health page in the Microsoft 365 admin center enables you to view the latest information on known issues for Windows monthly and feature updates. A known issue is an issue that has been identified in a Windows monthly update or feature update that impacts Windows devices. The Windows release health page is designed to inform you about known issues. You can use this information to troubleshoot issues your users may be experiencing. You can also determine when, and at what scale, to deploy an update in your organization. +The Windows release health page in the Microsoft 365 admin center enables you to view the latest information on known issues for Windows monthly and feature updates. A known issue is an issue that impacts Windows devices and that has been identified in a Windows monthly update or feature update. The Windows release health page is designed to inform you about known issues. You can use this information to troubleshoot issues your users may be experiencing. You can also determine when, and at what scale, to deploy an update in your organization. If you're unable to sign in to the Microsoft 365 admin portal, check the [Microsoft 365 service health](https://status.office365.com) status page to check for known issues preventing you from signing into your tenant. @@ -21,7 +21,7 @@ To be informed about the latest updates and releases, follow [@WindowsUpdate](ht ## How to review Windows release health information -1. Go to the [Microsoft 365 admin center](https://admin.microsoft.com), and sign in with an administrator account. +1. Go to the [Microsoft 365 admin center](https://admin.microsoft.com) and sign in with an administrator account. > [!NOTE] > By default, the Windows release health page is available to individuals who have been assigned the global admin or service administrator role for their tenant. To allow Exchange, SharePoint, and Skype for Business admins to view the Windows release health page, you must first assign them to a Service admin role. For more information about roles that can view service health, see [About admin roles](/microsoft-365/admin/add-users/about-admin-roles#commonly-used-microsoft-365-admin-center-roles). @@ -67,7 +67,7 @@ You have the option to sign up for email notifications about Windows known issue 1. Select **Save** when you're finished specifying email addresses and Windows versions. It may take up to 8 hours for these changes to take effect. > [!Note] -> When a single known issue affects multiple versions of Windows, you'll only receive one email notification, even if you've selected notifications for multiple versions. Duplicate emails won't be sent. +> When a single known issue affects multiple versions of Windows, you'll receive only one email notification, even if you've selected notifications for multiple versions. Duplicate emails won't be sent. ## Status definitions From cb37f4eb8c49bf39e4a1562afdca2e712e4546c4 Mon Sep 17 00:00:00 2001 From: Andre Della Monica Date: Tue, 2 May 2023 22:11:53 -0500 Subject: [PATCH 11/17] More changes --- ...ws-autopatch-device-registration-overview.md | 2 +- ...-autopatch-groups-manage-autopatch-groups.md | 17 ++++++++++++++++- .../deploy/windows-autopatch-groups-overview.md | 5 ++++- ...ch-groups-windows-feature-update-overview.md | 9 +++++++++ 4 files changed, 30 insertions(+), 3 deletions(-) diff --git a/windows/deployment/windows-autopatch/deploy/windows-autopatch-device-registration-overview.md b/windows/deployment/windows-autopatch/deploy/windows-autopatch-device-registration-overview.md index a48c8331a6..3dab9cc693 100644 --- a/windows/deployment/windows-autopatch/deploy/windows-autopatch-device-registration-overview.md +++ b/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 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 85e9177b85..59f6ecb921 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 @@ -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] diff --git a/windows/deployment/windows-autopatch/deploy/windows-autopatch-groups-overview.md b/windows/deployment/windows-autopatch/deploy/windows-autopatch-groups-overview.md index b87fdbe930..afe58bf5c8 100644 --- a/windows/deployment/windows-autopatch/deploy/windows-autopatch-groups-overview.md +++ b/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). diff --git a/windows/deployment/windows-autopatch/operate/windows-autopatch-groups-windows-feature-update-overview.md b/windows/deployment/windows-autopatch/operate/windows-autopatch-groups-windows-feature-update-overview.md index 6e84d0f62b..e3cb399b18 100644 --- a/windows/deployment/windows-autopatch/operate/windows-autopatch-groups-windows-feature-update-overview.md +++ b/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). From 2eb083115d5dc1f88846b1c081c049d83716d9a4 Mon Sep 17 00:00:00 2001 From: Tiara Quan <95256667+tiaraquan@users.noreply.github.com> Date: Wed, 3 May 2023 07:58:18 -0700 Subject: [PATCH 12/17] Update windows-autopatch-groups-manage-autopatch-groups.md --- .../windows-autopatch-groups-manage-autopatch-groups.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 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 59f6ecb921..386ded613f 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 @@ -1,7 +1,7 @@ --- title: Manage Windows Autopatch groups description: This article explains how to manage Autopatch groups -ms.date: 05/02/2023 +ms.date: 05/03/2023 ms.prod: windows-client ms.technology: itpro-updates ms.topic: how-to @@ -26,12 +26,12 @@ 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: +- Ensure the following [update rings for Windows 10 and later policy in Intune](/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: +- Ensure the following [feature updates for Windows 10 and later policy in Intune](/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] @@ -56,7 +56,7 @@ Before you start managing Autopatch groups, ensure you’ve met the following pr - 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. +> [Update rings](/mem/intune/protect/windows-10-update-rings) and [feature updates](/mem/intune/protect/windows-10-feature-updates) for Windows 10 and later policies that are created and managed by Windows Autopatch can be restored using the [Policy health](../operate/windows-autopatch-policy-health-and-remediation.md) feature. For more information on remediation actions, see [restore Windows update policies](../operate/windows-autopatch-policy-health-and-remediation.md#restore-windows-update-policies). > [!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. From 442dcc211a67996e1195e069505b3829a71476f5 Mon Sep 17 00:00:00 2001 From: Tiara Quan <95256667+tiaraquan@users.noreply.github.com> Date: Wed, 3 May 2023 07:59:38 -0700 Subject: [PATCH 13/17] Update windows-autopatch-groups-manage-autopatch-groups.md --- .../deploy/windows-autopatch-groups-manage-autopatch-groups.md | 2 -- 1 file changed, 2 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 386ded613f..e1c138aaca 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 @@ -61,8 +61,6 @@ Before you start managing Autopatch groups, ensure you’ve met the following pr > [!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] From 0d8dc62094cb0918e4b85072a126ffd3998a5864 Mon Sep 17 00:00:00 2001 From: Tiara Quan <95256667+tiaraquan@users.noreply.github.com> Date: Wed, 3 May 2023 08:00:57 -0700 Subject: [PATCH 14/17] Update windows-autopatch-groups-overview.md --- .../deploy/windows-autopatch-groups-overview.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/windows/deployment/windows-autopatch/deploy/windows-autopatch-groups-overview.md b/windows/deployment/windows-autopatch/deploy/windows-autopatch-groups-overview.md index afe58bf5c8..730fc16ec4 100644 --- a/windows/deployment/windows-autopatch/deploy/windows-autopatch-groups-overview.md +++ b/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/02/2023 +ms.date: 05/03/2023 ms.prod: windows-client ms.technology: itpro-updates ms.topic: conceptual @@ -248,6 +248,6 @@ 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. +> If you reach the maximum number of Autopatch groups supported (50), and try to create more Custom Autopatch groups, the "**Create**" option 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). From bdd5426929d394e9573fd40da26c20f74a6052b7 Mon Sep 17 00:00:00 2001 From: Tiara Quan <95256667+tiaraquan@users.noreply.github.com> Date: Wed, 3 May 2023 08:02:24 -0700 Subject: [PATCH 15/17] Update windows-autopatch-groups-windows-feature-update-overview.md --- ...indows-autopatch-groups-windows-feature-update-overview.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/windows/deployment/windows-autopatch/operate/windows-autopatch-groups-windows-feature-update-overview.md b/windows/deployment/windows-autopatch/operate/windows-autopatch-groups-windows-feature-update-overview.md index e3cb399b18..ef25e4b933 100644 --- a/windows/deployment/windows-autopatch/operate/windows-autopatch-groups-windows-feature-update-overview.md +++ b/windows/deployment/windows-autopatch/operate/windows-autopatch-groups-windows-feature-update-overview.md @@ -1,7 +1,7 @@ --- title: Windows feature updates overview with Autopatch groups description: This article explains how Windows feature updates are managed with Autopatch groups -ms.date: 05/01/2023 +ms.date: 05/03/2023 ms.prod: windows-client ms.technology: itpro-updates ms.topic: conceptual @@ -44,7 +44,7 @@ Windows Autopatch’s device eligibility criteria for Windows feature updates al - 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. +- Allows for scenarios where you can deploy a single release across several Autopatch groups and its deployment rings. ## Key concepts From 12f777e8d871dda0d61d635e89900b899afb6c7a Mon Sep 17 00:00:00 2001 From: rekhanr <40372231+rekhanr@users.noreply.github.com> Date: Wed, 3 May 2023 08:33:23 -0700 Subject: [PATCH 16/17] Update windows-autopatch-policy-health-and-remediation.md @tiaraquan there is an update to the name of the tab that has alerts. --- .../windows-autopatch-policy-health-and-remediation.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/windows/deployment/windows-autopatch/operate/windows-autopatch-policy-health-and-remediation.md b/windows/deployment/windows-autopatch/operate/windows-autopatch-policy-health-and-remediation.md index 803ffa0560..8e4b4794f4 100644 --- a/windows/deployment/windows-autopatch/operate/windows-autopatch-policy-health-and-remediation.md +++ b/windows/deployment/windows-autopatch/operate/windows-autopatch-policy-health-and-remediation.md @@ -50,7 +50,7 @@ The minimum role required to restore configurations is **Intune Service Administ **To initiate remediation action for device configuration alerts:** 1. Go to the [Microsoft Intune admin center](https://go.microsoft.com/fwlink/?linkid=2109431). -1. Navigate to **Tenant administration** > **Tenant management** > **Alerts**. +1. Navigate to **Tenant administration** > **Tenant management** > **Actions**. 1. Select **Restore missing policy** to launch the workflow. 1. Review the message and select **Restore policy**. 1. If the **Change modified policy alert** appears, select this alert to launch the workflow. @@ -83,7 +83,7 @@ There will be an alert for each policy that is missing or has deviated from the **To initiate remediation action for missing groups:** 1. Go to the [Microsoft Intune admin center](https://go.microsoft.com/fwlink/?linkid=2109431). -1. Navigate to **Tenant administration** > **Tenant management** > **Alerts**. +1. Navigate to **Tenant administration** > **Tenant management** > **Actions**. 1. Select **Restore missing group** to launch the workflow. 1. Review the message and select **Restore group**. From 6fee0482c30e21da7be117b35a22bb9e54a604d5 Mon Sep 17 00:00:00 2001 From: Andre Della Monica Date: Wed, 3 May 2023 16:43:47 -0500 Subject: [PATCH 17/17] Changes --- ...topatch-groups-windows-feature-update-overview.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/windows/deployment/windows-autopatch/operate/windows-autopatch-groups-windows-feature-update-overview.md b/windows/deployment/windows-autopatch/operate/windows-autopatch-groups-windows-feature-update-overview.md index ef25e4b933..b49b0c5ba4 100644 --- a/windows/deployment/windows-autopatch/operate/windows-autopatch-groups-windows-feature-update-overview.md +++ b/windows/deployment/windows-autopatch/operate/windows-autopatch-groups-windows-feature-update-overview.md @@ -80,12 +80,12 @@ If the device is registered with Windows Autopatch, and the device is: If your tenant is enrolled with Windows Autopatch, you can see the following default policies created by the service in the [Microsoft Intune admin center](https://go.microsoft.com/fwlink/?linkid=2109431): -| Policy name | Feature update version | Rollout options | First deployment ring availability | Final deployment ring availability | Day between deployment rings | Support end date | -| ----- | ----- | ----- | ----- | ----- | ----- | ----- | -| Windows Autopatch – DSS Policy [Test] | Windows 10 21H2 | Make update available as soon as possible | May 9, 2023 | N/A | N/A | June 10, 2024 | -| Windows Autopatch – DSS Policy [Ring1] | Windows 10 21H2 | Make update available as soon as possible | May 16, 2023 | N/A | N/A | June 10, 2024 | -| Windows Autopatch – DSS Policy [Ring2] | Windows 10 21H2 | Make update available as soon as possible | May 23, 2023 | N/A | N/A | June 10, 2024 | -| Windows Autopatch – DSS Policy [Ring3] | Windows 10 21H2 | Make update available as soon as possible | May 30, 2023 | N/A | N/A | June 10, 2024 | +| Policy name | Phase mapping | Feature update version | Rollout options | First deployment ring availability | Final deployment ring availability | Day between deployment rings | Support end date | +| ----- | ----- | ----- | ----- | ----- | ----- | ----- | ----- | +| Windows Autopatch – DSS Policy [Test] | Phase 1 | Windows 10 21H2 | Make update available as soon as possible | May 9, 2023 | N/A | N/A | June 10, 2024 | +| Windows Autopatch – DSS Policy [First] | Phase 2 | Windows 10 21H2 | Make update available as soon as possible | May 16, 2023 | N/A | N/A | June 10, 2024 | +| Windows Autopatch – DSS Policy [Fast] | Phase 3 | Windows 10 21H2 | Make update available as soon as possible | May 23, 2023 | N/A | N/A | June 10, 2024 | +| Windows Autopatch – DSS Policy [Broad] | Phase 4 | Windows 10 21H2 | Make update available as soon as possible | May 30, 2023 | N/A | N/A | June 10, 2024 | > [!NOTE] > Gradual rollout settings aren't configured in the default Windows Update feature policy. If the date of the final group availability is changed to a past date, all remaining devices are offered the update as soon as possible. For more information, see [rollout options for Windows Updates in Microsoft Intune](/mem/intune/protect/windows-update-rollout-options#make-updates-available-gradually).