Create virtual network peering

Azure Virtual Network peering can be configured for virtual networks by using PowerShell, the Azure CLI, and in the Azure portal. In this module, we review the steps to create the peering in the Azure portal for virtual networks deployed through Azure Resource Manager.

Things to know about creating virtual network peering

There are a few points to review before we look at how to create the peering in the Azure portal.

• To implement virtual network peering, your Azure account must be assigned to the Network Contributor role. Alternatively, your Azure account can be assigned to a custom role that can complete the necessary peering actions. For details, see Permissions.

• To create a peering, you need two virtual networks.

• The second virtual network in the peering is referred to as the remote network.

• Initially, the virtual machines in your virtual networks can't communicate with each other. After the peering is established, the machines can communicate within the peered network based on your configuration settings.

How to connect virtual networks across Azure regions with Azure Global virtual network peering

How to check your peering status

In the Azure portal, you can check the connectivity status of the virtual networks in your virtual network peering. The status conditions depend on how your virtual networks are deployed.

• The two peering status conditions are Initiated and Connected.

• When you create the initial peering to the second (remote) virtual network from the first virtual network, the peering status for the first virtual network is Initiated.