Merge pull request #51838 from ramakoni1/patch-9

ktoliver · web-flow · commit 1e64246bed90 · 2020-04-07T09:51:45.000-06:00
Adding a note based on CSS SME feedback.
diff --git a/articles/sql-database/sql-database-managed-instance-create-vnet-subnet.md b/articles/sql-database/sql-database-managed-instance-create-vnet-subnet.md
@@ -23,13 +23,13 @@ Azure SQL Database Managed Instance must be deployed within an Azure [virtual ne
 - Connecting a Managed Instance to linked server or another on-premises data store
 - Connecting a Managed Instance to Azure resources  
 
-> [!Note]
+> [!NOTE]
 > You should [determine the size of the subnet for Managed Instance](sql-database-managed-instance-determine-size-vnet-subnet.md) before you deploy the first instance. You can't resize the subnet after you put the resources inside.
 >
 > If you plan to use an existing virtual network, you need to modify that network configuration to accommodate your Managed Instance. For more information, see [Modify an existing virtual network for Managed Instance](sql-database-managed-instance-configure-vnet-subnet.md).
 >
-> After a managed instance is created, moving the managed instance or VNet to another resource group or subscription is not supported.
-
+> After a managed instance is created, moving the managed instance or VNet to another resource group or subscription is not supported.  Moving the managed instance to another subnet also is not supported.
+>
 
 ## Create a virtual network
 

Original file line number	Diff line number	Diff line change
`@@ -23,13 +23,13 @@ Azure SQL Database Managed Instance must be deployed within an Azure [virtual ne`
`23`	`23`	`- Connecting a Managed Instance to linked server or another on-premises data store`
`24`	`24`	`- Connecting a Managed Instance to Azure resources`
`25`	`25`
`26`		`-> [!Note]`
	`26`	`+> [!NOTE]`
`27`	`27`	`> You should [determine the size of the subnet for Managed Instance](sql-database-managed-instance-determine-size-vnet-subnet.md) before you deploy the first instance. You can't resize the subnet after you put the resources inside.`
`28`	`28`	`>`
`29`	`29`	`> If you plan to use an existing virtual network, you need to modify that network configuration to accommodate your Managed Instance. For more information, see [Modify an existing virtual network for Managed Instance](sql-database-managed-instance-configure-vnet-subnet.md).`
`30`	`30`	`>`
`31`		`-> After a managed instance is created, moving the managed instance or VNet to another resource group or subscription is not supported.`
`32`		`-`
	`31`	`+> After a managed instance is created, moving the managed instance or VNet to another resource group or subscription is not supported. Moving the managed instance to another subnet also is not supported.`
	`32`	`+>`
`33`	`33`
`34`	`34`	`## Create a virtual network`
`35`	`35`