
close
close
Want to know about the security benefits of Microsoft's E5 license?
In today’s Ask the Admin, I’ll show you how to create two virtual networks (VNets) and link them together using a Virtual Private Network (VPN) in the new Azure Management Portal.
The new Azure management portal reached General Availability in December last year, and because it’s based on Azure Resource Management (ARM) rather than the classic deployment methods supported by the original management GUI, almost all configuration tasks have changed.
The process involves the following steps:
If you still prefer to use the old management console, take a look at Aidan Finn’s article Deploying VNet-to-VNet VPNs in Azure on the Petri IT Knowledgebase.
Start by creating a virtual network. For the purposes of this article, I’ll create the first virtual network with an address space of 10.8.0.0/16 and default subnet using the 10.8.0.0/24 address range. The second subnet will have an address space of 192.168.0.0/16 and default subnet with the address range 192.168.0.0/24.
Create a virtual network in the Azure management portal (Image Credit: Russell Smith)
Before we can connect two virtual networks using a VPN, each VNet must have a small gateway subnet. In this example, I’ve chosen 10.8.1.0/28 as the gateway address space, giving 16 available addresses.
The chosen address space shouldn’t overlap with an existing address space in the virtual network, or have a subnet mask smaller than /16 or greater than /29.
Add a subnet to the virtual network in the Azure management portal (Image Credit: Russell Smith)
The new subnet will now appear in the Subnets pane.
To connect the two VNets to each other we need to give each one a unique public IP address.
Wait for the completion message in the Azure portal. You can view messages by clicking the alarm icon in the top right of the portal window.
Add a public IP address to the virtual network in the Azure management portal (Image Credit: Russell Smith)
Now all that’s left to do is create a VNet gateway for the virtual network.
Create a virtual network gateway in the Azure management portal (Image Credit: Russell Smith)
While the new gateway is being deployed, repeat the above procedures to create a second VNet. Virtual network gateways can take up to 30 minutes to be provisioned.
Once both the VNets and their virtual network gateways have been deployed, we need to create a connection object between the two gateways.
Create a connection in the Azure management portal (Image Credit: Russell Smith)
More in Microsoft Azure
Microsoft's New Azure Fluid Relay Service Lets Developers Build Collaborative Apps
Aug 5, 2022 | Rabia Noureen
Oracle Teams Up with Microsoft to Launch New Database Service for Azure
Jul 21, 2022 | Rabia Noureen
Most popular on petri