Update virtual-network-concepts.md

Update text to state networking will work with peered VNets as well

Author: anotherRedbeard

articles/api-management/virtual-network-concepts.md

@@ -64,7 +64,7 @@ In the API Management Premium v2 tier, inject your instance into a delegated sub
 In this configuration: 
 
 * The API Management gateway endpoint is accessible through the virtual network at a private IP address.
-* API Management can make outbound requests to API backends that are isolated in the network. 
+* API Management can make outbound requests to API backends that are isolated in the network or any peered network, as long as network connectivity is properly configured. 
 
 This configuration is recommended for scenarios where you want to isolate both the API Management instance and the backend APIs. Virtual network injection in the Premium v2 tier automatically manages network connectivity to most service dependencies for Azure API Management.
 
@@ -74,7 +74,7 @@ For more information, see [Inject a Premium v2 instance into a virtual network](
 
 ## Virtual network integration (v2 tiers)
 
-The Standard v2 and Premium v2 tiers support outbound virtual network integration to allow your API Management instance to reach API backends that are isolated in a single connected virtual network. The API Management gateway, management plane, and developer portal remain publicly accessible from the internet. 
+The Standard v2 and Premium v2 tiers support outbound virtual network integration to allow your API Management instance to reach API backends that are isolated in a single connected virtual network or any peered virtual network, as long as network connectivity is properly configured. The API Management gateway, management plane, and developer portal remain publicly accessible from the internet. 
 
 Outbound integration enables the API Management instance to reach both public and network-isolated backend services.