Merge pull request #127258 from VitaliyKurokhtin/master

Update virtual network requirements and addressPrefix property for workspace gateways

Author: v-dirichards

articles/api-management/virtual-network-workspaces-resources.md

@@ -30,6 +30,8 @@ The virtual network must be in the same region and Azure subscription as the API
 
 * The subnet used for virtual network integration or injection can only be used by a single workspace gateway. It can't be shared with another Azure resource.
 
+[!INCLUDE [api-management-virtual-network-address-prefix](../../includes/api-management-virtual-network-address-prefix.md)]
+
 ## Subnet size 
 
 * Minimum: /27 (32 addresses)

includes/api-management-virtual-network-address-prefix.md

@@ -8,7 +8,7 @@ ms.author: danlep
 
 ### addressPrefix property
 
-Virtual network injection in the Premium v2 tier requires that the `addressPrefix` subnet property is set to a valid CIDR block. 
+Virtual network injection in the Premium v2 tier and workspace gateways require that the `addressPrefix` subnet property is set to a valid CIDR block. 
 
 If you configure the subnet using the Azure portal, the subnet sets an `addressPrefixes` (plural) property consisting of a list of address prefixes. However, API Management requires a single CIDR block as the value of the `addressPrefix` property.