edit

Author: gitName

articles/api-management/inject-vnet-v2.md

@@ -72,7 +72,7 @@ For more information about configuring subnet delegation, see [Add or remove a s
 
 ### Permissions
 
-You must have at least the following role-based access control permissions on the subnet or at a higher level to configure virtual network integration:
+You must have at least the following role-based access control permissions on the subnet or at a higher level to configure virtual network injection:
 
 | Action | Description |
 |-|-|

articles/api-management/integrate-vnet-outbound.md

@@ -63,6 +63,8 @@ The subnet needs to be delegated to the **Microsoft.Web/serverFarms** service.
 
 For more information about configuring subnet delegation, see [Add or remove a subnet delegation](../virtual-network/manage-subnet-delegation.md).
 
+[!INCLUDE [api-management-virtual-network-address-prefix](../../includes/api-management-virtual-network-address-prefix.md)]
+
 ### Permissions
 
 You must have at least the following role-based access control permissions on the subnet or at a higher level to configure virtual network integration:

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

@@ -8,7 +8,7 @@ ms.author: danlep
 
 ### addressPrefix property
 
-The `addressPrefix` subnet property must be set to a valid CIDR block. 
+Networking in the Premium v2 tier requires 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.