Azure Global VNet Peering – Microsoft beats Amazon to the line

Microsoft has just announced the public preview of Global VNet Peering which will allow seamless virtual network connectivity to across multiple Azure regions. The following regions are enabled for the preview of Global VNet Peering

  • US West Central
  • Canada Central
  • US West 2

Amazon Web Services (AWS) does not currently allow VPC peering across different regions. Both platforms allow seamless virtual network peering within the same region.

According to Microsoft’s latest financial results for the quarter ending March 2017 Azure appears to be growing faster than AWS. Source: Microsoft’s cloud business is growing almost twice as fast as Amazon’s, with Google far behind, CNBC, April 2017. 

In my opinion both AWS and Azure will continue to grow strongly, adding new functionality often in a bid to keep other competitors such as Google at bay.

Why use VNet Peering?

Virtual Network peering allows connectivity between separate virtual networks using Microsoft’s Azure backbone.  Benefits include

  • Traffic is private and it never leaves the Azure internal backbone or traverses the internet.
  • Connectivity performance improved due to fewer restrictions on bandwidth. This compares to the previous method of using VNet to VNet VPN connection
  • Ability to peer Azure Resource Manager (ARM) VNets with classic VNets (some restrictions apply)

The introduction of Global VNet Peering further increases the amount of options when designing your Azure Virtual Network infrastructure. The limitations associated with using VNet to VNet VPN connections often were a deterrent to adopting a multi region approach to designing Azure Virtual Networks.

Diagram of Azure Virtual Network peering
Azure Virtual Network peering diagram with gateway transit













For more information please see the product announcement here.

Using classic virtual networks?

We can help redesign them

We have successfully completed a number of  projects migrating Azure resources from the classic deployment model to Azure Resource Manager (ARM). During this process we can redesign your virtual networks to follow best practice and take advantage of new features such as VNet peering.

Leave a Reply