Merge pull request #181922 from urosmil/patch-5

Update cross-subnet content in side articles

Author: ttorble

azure-sql/managed-instance/frequently-asked-questions-faq.yml

@@ -347,7 +347,7 @@ sections:
           
           ### Can I move my managed instance to another subnet?
           
-          No. This is a current Managed Instance design limitation. However, you can provision a new instance in another subnet and manually back up and restore data between the old and the new instance or perform cross-instance [point-in-time restore](point-in-time-restore.md?tabs=azure-powershell).
+          Yes. Instance can be moved to another subnet inside the same virtual network in an online way. Learn how to [move Azure SQL Managed Instance across subnets](./vnet-subnet-move-instance.md).
           
           ### Do I need an empty virtual network to create a Managed Instance?
           

azure-sql/managed-instance/vnet-subnet-determine-size.md

@@ -11,7 +11,7 @@ ms.topic: how-to
 author: srdan-bozovic-msft
 ms.author: srbozovi
 ms.reviewer: mathoma, bonova, srbozovi, wiassaf
-ms.date: 06/14/2021
+ms.date: 12/06/2021
 ---
 # Determine required subnet size and range for Azure SQL Managed Instance
 [!INCLUDE[appliesto-sqlmi](../includes/appliesto-sqlmi.md)]
@@ -42,7 +42,7 @@ Size your subnet according to your future needs for instance deployment and scal
 - Each scaling request temporarily allocates an additional number of addresses.
 
 > [!IMPORTANT]
-> It's not possible to change the subnet address range if any resource exists in the subnet. It's also not possible to move managed instances from one subnet to another. Consider using bigger subnets rather than smaller ones to prevent issues in the future.
+> It's not possible to change the subnet address range if any resource exists in the subnet. Consider using bigger subnets rather than smaller ones to prevent issues in the future.
 
 GP = general purpose; 
 BC = business critical;