From bbf7e4f1bbc0d7349f6f9e51910e496d4d685d74 Mon Sep 17 00:00:00 2001
From: rekhanr <40372231+rekhanr@users.noreply.github.com>
Date: Tue, 4 Apr 2023 15:33:02 -0700
Subject: [PATCH] Update windows-autopatch-windows-update.md

Added text in the note that its not recommended for business critical workloads
---
 .../operate/windows-autopatch-windows-update.md                  | 1 +
 1 file changed, 1 insertion(+)

diff --git a/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-update.md b/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-update.md
index 508c99fa46..e51477b2c7 100644
--- a/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-update.md
+++ b/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-update.md
@@ -53,6 +53,7 @@ However, if an update has already started for a particular deployment ring, Wind
 #### Scheduled install
 
 > [!NOTE]
+> This feature isn't suitable for business critical workloads since Windows Autopatch cannot guarantee that devices will always update and restart in the specified window.
 > If you select the Schedule install cadence type, the devices in that ring won’t be counted towards the [Windows quality update service level objective](../operate/windows-autopatch-windows-quality-update-overview.md#service-level-objective).
 
 While the Windows Autopatch default options will meet the majority of the needs for regular users with corporate devices, we understand there are devices that run critical activities and can only receive Windows Updates at specific times. The **Scheduled install** cadence type will prevent forced restarts and interruptions to critical business activities for end users, thereby minimizing disruptions. Upon selecting the **Scheduled install** cadence type, any previously set deadlines and grace periods will be removed. The expectation is that devices would only update and restart according to the time specified.