From 18c609214e15f3201e2110caa74e8449bb6a7cfd Mon Sep 17 00:00:00 2001 From: rekhanr <40372231+rekhanr@users.noreply.github.com> Date: Wed, 29 Mar 2023 11:09:35 -0700 Subject: [PATCH] Update windows-autopatch-windows-quality-update-end-user-exp.md @tiaraquan need a quick to this document until we match UX updates. @Russw44 @mounicabattula FYI. --- .../windows-autopatch-windows-quality-update-end-user-exp.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-end-user-exp.md b/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-end-user-exp.md index e18ee9ef48..f87f880bee 100644 --- a/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-end-user-exp.md +++ b/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-end-user-exp.md @@ -76,4 +76,4 @@ Windows Autopatch understands the importance of not disrupting end users but als A device won't restart during active hours unless it has passed the date specified by the update deadline policy. Once the device has passed the deadline policy, the device will update as soon as possible. > [!IMPORTANT] -> If your devices must be updated at a specific date or time, they aren't suitable for Windows Autopatch. Allowing you to choose specific dates to update devices would disrupt the rollout schedule, and prevent us from delivering the service level objective. The use of any of the following CSPs on a managed device will render it ineligible for management: +> If your devices must be updated at a specific date or time, they aren't suitable for Windows Autopatch. Allowing you to choose specific dates to update devices would disrupt the rollout schedule, and prevent us from delivering the service level objective(SKO). The use of any of the following CSPs on a managed device will render it ineligible for SLO: