Skip to content

Commit 637d3d4

Browse files
Merge pull request #280370 from mbender-ms/vnet-peering
virtual network - Update peering docs RE can't move vnet in peering connection
2 parents 2483a64 + 1482b01 commit 637d3d4

File tree

2 files changed

+6
-0
lines changed

2 files changed

+6
-0
lines changed

articles/virtual-network/virtual-network-manage-peering.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -306,6 +306,8 @@ az network vnet peering delete \
306306
- <a name="cross-region"></a>You can peer virtual networks in the same region, or different regions. Peering virtual networks in different regions is also referred to as **Global Virtual Network Peering**.
307307

308308
- When creating a global peering, the peered virtual networks can exist in any Azure public cloud region or China cloud regions or Government cloud regions. You can't peer across clouds. For example, a virtual network in Azure public cloud can't be peered to a virtual network in Microsoft Azure operated by 21Vianet cloud.
309+
310+
- When part of a peering, a virtual network cannot be moved. If you need to move a virtual network to a different resource group or subscription, you must delete the peering, move the virtual network, and then recreate the peering.
309311

310312
- Resources in one virtual network can't communicate with the front-end IP address of a basic load balancer (internal or public) in a globally peered virtual network. Support for basic load balancer only exists within the same region. Support for standard load balancer exists for both, Virtual Network Peering and Global Virtual Network Peering. Some services that use a basic load balancer don't work over global virtual network peering. For more information, see [Constraints related to Global Virtual Network Peering and Load Balancers](virtual-networks-faq.md#what-are-the-constraints-related-to-global-virtual-network-peering-and-load-balancers).
311313

articles/virtual-network/virtual-networks-faq.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -430,6 +430,10 @@ No. You can't enable virtual network peering if address spaces overlap.
430430

431431
No. You can enable the **Use Remote Gateway** option on only one peering to one of the virtual networks.
432432

433+
### Can I move a virtual network that has a peering connection to another virtual network?
434+
435+
No. You can't move a virtual network that has a peering connection to another virtual network. You must delete the peering connection before moving the virtual network.
436+
433437
### How much do virtual network peering links cost?
434438

435439
There's no charge for creating a virtual network peering connection. Data transfer across peering connections is charged. For more information, see the [Azure Virtual Network pricing page](https://azure.microsoft.com/pricing/details/virtual-network/).

0 commit comments

Comments
 (0)