From f83e209c07f6e93dedf060ef556e77ef2bcb5c19 Mon Sep 17 00:00:00 2001 From: Tiara Quan <95256667+tiaraquan@users.noreply.github.com> Date: Thu, 15 Sep 2022 10:09:05 -0700 Subject: [PATCH] Update windows-autopatch-post-reg-readiness-checks.md --- .../deploy/windows-autopatch-post-reg-readiness-checks.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/windows-autopatch/deploy/windows-autopatch-post-reg-readiness-checks.md b/windows/deployment/windows-autopatch/deploy/windows-autopatch-post-reg-readiness-checks.md index 68e7a84e49..aa5eafc5b2 100644 --- a/windows/deployment/windows-autopatch/deploy/windows-autopatch-post-reg-readiness-checks.md +++ b/windows/deployment/windows-autopatch/deploy/windows-autopatch-post-reg-readiness-checks.md @@ -29,7 +29,7 @@ Device readiness in Windows Autopatch is divided into two different scenarios: | Prerequisite checks | Ensures devices follow software-based requirements before being registered with the service. | | Post-device registration readiness checks | Provides continuous monitoring of device health for registered devices.

IT admins can easily detect and remediate configuration mismatches in their environments or issues that prevent devices from having one or more software update workloads (Windows quality, feature updates, Microsoft Office, Microsoft Teams, or Microsoft Edge) fully managed by the Windows Autopatch service. Configuration mismatches can leave devices in a vulnerable state, out of compliance and exposed to security threats.

| -### Device readiness for each scenario +### Device readiness checks available for each scenario | Required device readiness (prerequisite checks) prior to device registration (powered by Intune Graph API) | Required post-device registration readiness checks (powered by Microsoft Cloud Managed Desktop Extension) | | ----- | ----- |