From 9041007ced760fe6fd8f4d7cc156bbf1f94e5fb2 Mon Sep 17 00:00:00 2001
From: Vignesh Mitsume <48824590+VigneshMitsume@users.noreply.github.com>
Date: Mon, 5 Sep 2022 16:15:34 +0900
Subject: [PATCH] Add warning notes

Regarding autopatch, adding the devices directly to the autopatch groups are unsupported and might cause unexpected impact to the service. But system allows to do so. Hence updating the docs accordingly.
---
 .../operate/windows-autopatch-update-management.md             | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/windows/deployment/windows-autopatch/operate/windows-autopatch-update-management.md b/windows/deployment/windows-autopatch/operate/windows-autopatch-update-management.md
index 982440f7ea..ae88d14238 100644
--- a/windows/deployment/windows-autopatch/operate/windows-autopatch-update-management.md
+++ b/windows/deployment/windows-autopatch/operate/windows-autopatch-update-management.md
@@ -40,6 +40,9 @@ During the [tenant enrollment process](../prepare/windows-autopatch-enroll-tenan
 
 Each deployment ring has a different set of update deployment policies to control the updates rollout.
 
+> [!Warning]
+> Adding/Importing devices into any of these groups directly is not supported and doing so might cause unexpected impact to the autopatch service. To add/move devices between these groups see [Moving devices in between deployment rings](../operate/windows-autopatch-update-management.md#moving-devices-in-between-deployment-rings).
+
 > [!IMPORTANT]
 > Windows Autopatch device registration doesn't assign devices to its test deployment ring (**Modern Workplace Devices-Windows Autopatch-Test**). This is intended to prevent devices that are essential to a business from being affected or devices that are used by executives from receiving early software update deployments.