From 41c6e5fb10251d98c462e2300298256291b3a294 Mon Sep 17 00:00:00 2001
From: chrisjlin <36452239+chrisjlin@users.noreply.github.com>
Date: Mon, 17 Mar 2025 14:26:01 -0700
Subject: [PATCH] Tweaks to resource move compliance note in mcc docs

---
 windows/deployment/do/mcc-ent-create-resource-and-cache.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/windows/deployment/do/mcc-ent-create-resource-and-cache.md b/windows/deployment/do/mcc-ent-create-resource-and-cache.md
index bf9743e78e..2385b1a3fd 100644
--- a/windows/deployment/do/mcc-ent-create-resource-and-cache.md
+++ b/windows/deployment/do/mcc-ent-create-resource-and-cache.md
@@ -29,7 +29,7 @@ For more information on sizing and OS requirements, see [the prerequisites for u
 ## Create Connected Cache Azure resource
 
 >[!Note]
-   >* You cannot move your Connected Cache Azure resource to a different subscription after creation.
+   >* Resource move is not currently supported for Connected Cache Azure resources. If you need to move your Connected Cache Azure resource, you can consider deleting the existing resource and create another one in another location.
 
 # [Azure portal](#tab/portal)