{"id":2807,"date":"2018-05-01T00:00:00","date_gmt":"2018-05-01T00:00:00","guid":{"rendered":"https:\/\/azure.microsoft.com\/blog\/global-vnet-peering-now-generally-available"},"modified":"2023-05-11T15:40:03","modified_gmt":"2023-05-11T22:40:03","slug":"global-vnet-peering-now-generally-available","status":"publish","type":"post","link":"https:\/\/azure.microsoft.com\/en-us\/blog\/global-vnet-peering-now-generally-available\/","title":{"rendered":"Global VNet Peering now generally available"},"content":{"rendered":"

Today, I am thrilled to announce<\/a> the general availability of Global VNet Peering in all Azure public regions<\/a>, empowering you to take the ease, simplicity, and isolation of VNet peering to the next level.<\/p>\n

Azure\u2019s Virtual Network (VNet) is a logical isolation of Azure which enables you to securely connect Azure resources to each other. VNet lets you create your own private space in Azure \u2013 your own network bubble, as I like to call it.<\/p>\n

With Global VNet Peering available, you can enable connectivity across all Azure public regions without additional bandwidth restrictions and as always keeping all your traffic on the Microsoft Backbone. Global VNet Peering provides you with the flexibility to scale and control how workloads connect across geographical boundaries, unlocking and applying global scale to a plethora of scenarios such as data replication, database failover, and disaster recovery through private IP addresses. You can also share resources across different business unit VNets, the hub-and-spoke model<\/a>, as we refer to it, through a global peering connection. As your organization grows across geographic boundaries, you can continue to share resources like firewalls or other virtual appliances via peering.<\/p>\n

We announced<\/a> VNet peering at Microsoft Ignite 2017<\/a> bringing you the ability to connect two virtual networks within any Azure region through the Azure backbone network. Once peered, the two virtual networks appear as one for a coherent connectivity experience \u2013 an expansion of your network bubble, so to speak. While the VNets are still managed as separate resources, the virtual machines in the peered networks can communicate with each other directly through their private IP addresses \u2013 no gateways, no public IP addresses, no internet, no extra hops. The limitation back then, was that both VNets needed to be in the same region, and with this announcement, that limitation have been lifted.<\/p>\n

Details<\/h2>\n