Modify or Delete Virtual Network Peering – Intersite Connectivity

Modifying or deleting the virtual network peering will disrupt connectivity between the peered networks. You should have a valid business reason before you modify or delete the peering. Some scenarios where you modify or delete the peering include the following:

• The networks no longer require communicating with each other.
• Resources have been migrated to another virtual network, and the current peering is not required.
• You are implementing VPN/ExpressRoute connectivity between the virtual networks.
• New gateways were added to the network, and you plan to implement the gateway transit feature.
• You need to allow or block traffic from a certain peered network.

Modifying the peering is easy; you can navigate to one of the peered virtual networks and switch to the Peerings blade. In the Peerings blade, all peering connections will be listed. Clicking any of the connections will help you modify the properties such as traffic to the remote virtual network and traffic forwarded from the remote virtual network or route server. However, properties such as link names and the remote network cannot be changed. Similarly, you can navigate to the Peerings blade of the peered network to modify its properties, as shown in Figure 4.5.

Deleting virtual network peering can be also accomplished from the Peering blade. Find the peering you would like to delete and click the three dots in the far-right corner of the connection. You will be presented with the option to delete, as shown in Figure 4.6.

Once you click Delete, a confirmation window will pop up, and you need to select Yes. The connection that you have selected and the reciprocal connection in the other virtual network will be deleted in a single shot. Your resources in the virtual networks will no longer be able to communicate with each other.

Since you have completed virtual network peering, let’s jump to the next method, which can be used to connect two Azure sites: a VPN gateway.