Merge pull request #230336 from flang-msft/fxl---An-existing-redis-cache-instance-cannot-be-to-a-Virtual-Network-105826

Fxl---an existing redis cache instance cannot be to a virtual network 105826

Author: prmerger-automator[bot]

articles/azure-cache-for-redis/cache-network-isolation.md

@@ -5,7 +5,9 @@ author: flang-msft
 ms.author: franlanglois
 ms.service: cache
 ms.topic: conceptual
-ms.date: 03/09/2023
+ms.date: 03/10/2023
+
+
 ---
 
 # Azure Cache for Redis network isolation options
@@ -47,7 +49,8 @@ VNet is the fundamental building block for your private network in Azure. VNet e
 ### Limitations of VNet injection
 
 - VNet injected caches are only available for Premium Azure Cache for Redis.
-- When using a VNet injected cache, you must change your VNet to cache dependencies such as CRLs/PKI, AKV, Azure Storage, Azure Monitor, and more.  
+- When using a VNet injected cache, you must change your VNet to cache dependencies such as CRLs/PKI, AKV, Azure Storage, Azure Monitor, and more.
+- You can't inject an Azure Cache for Redis instance into a Virtual Network. You can only select this option when you _create_ the cache. 
 
 ## Azure Firewall rules