Azure has recently launched Global VNET Peering that enables multiple Azure regions to connect to each other via Azure’s Internal backbone. This new feature is extremely handy when you have application landscapes stretched across region that needs high speed connectivity such as with SQL replication.
Previously only option was to connect to leverage Azure VPN gateways that connects multiple regions together apart from Express Route which is expensive solution to implement for most organizations. Express Route was never ideal choice for Azure to Azure connection anyway. VPN gateways had limitation in terms of bandwidth offered – VPNGW3 SKU offers bandwidth up to 1.25Gbps.
Apart from cost, VPN gateways had to be managed & they had cost involved. Azure Global VNET peering removes all these cons in the configuration. Bandwidth charges still apply but rest is part of native Azure service & doesn’t imply any cost.
Global VNET Peering is now generally available on all Azure regions.
Let us now see configuration of Global VNET Peering –
- Created a Virtual Network in West Europe with address space – 10.2.0.0/24
- Create a Virtual Network in US West 2 with address space – 10.3.0.0/24
- Creates VMs on these subnets
Go to the West Europe Virtual Network and click on Peerings on the left pane
Give a name to the Peering such as “Europe-to-US” , select your Virtual Network you want to peer with – in this case Virtual Network in US West 2
Repeat the above process for US West 2 Virtual Network as well to peer with Virtual Network in West Europe
Once the VNET Peering is created you would see it as “connected” in the Peerings configuration
To validate the configuration you could now login to both Virtual Machines & see if they are able to connect or you could also go to the Network Interface that is connected to Virtual Machine or the Virtual Subnet to see the effective routes as show below –
You would see above that traffic to remote Virtual Network is via Global VNET peering