Last week Microsoft unlocked one of the biggest features an Enterprise could ask for in Azure – VNet Peering.
What is a VNet?
A VNet is a foundational building block in Azure, and although many organizations will manage fine with a single subscription and a single VNet, Enterprises usually require more separation.
Why use a VNet?
There can be many reasons multiple VNets are required; different business units, Dev/Test/Prod separation and billing are all examples of why VNet separation may be required.
Until now, in order to connect 2 VNets together would have needed either an appliance or an Azure Gateway – both of which incur cost and require management, and neither will perform as well as a VM to VM Communication on the same VNet.
With VNet Peering Microsoft has enabled 2 or more VNets to be logically separate, and traffic between them being controlled, but with all the benefits of a single VNet.
What does this mean?
This once again shows Microsoft is listening is making improvements that Enterprises require.
VNet Peering is currently in Preview – right now it’s free, however when it goes GA there will be a nominal charge for traffic between VNets.