Azure VNet is a representation of network in the cloud and is a logical isolation of Azure Cloud dedicated to subscription ability to fully control IP Address blocks, DNS settings, security policies and route tables.
VNet can be further segmented into subnets, each subnets will have a logical collection of Virtual Machines. VNets are completed isolated from one another and this provides the ability to create disjoint networks for development, testing and production that use the same CIDR(Classless Inter-Domain Routing) address blocks. In order to connect VNet to on-premise data center we can use site-to-site VPN connection or Express Route connection.
It is important to note that before creating Virtual Machines and installing software first plan VNet. This is because an existing virtual machine CANNOT be added to a newly created virtual network.
This article will go through the steps involved in creating a VNet having SubNets and AzureVM’s attached to different SubNet(s). The topology for the sample lab set up is as per below:
The artifacts in the above diagram include:
- FrontEnd-SubNet containing Azure VM resource AZ-FE01
- BackEnd-SubNet containing Azure VM resource AZ-BE01
- Management-SubNet containing Azure VM resource AZ-MGMT01
All AZure VM’s can be configured to be accessed through RDP connection by allowing traffic through port 3389. Best practice is to have a Management SubNet with an VM allocated so that external users login to that Virtual Machine and proceed from there on.
There are two addresses associated to each VM viz., Public IP Address and Private IP Address. All the VM’s in the SubNet that need to be accessed from internet need to have Public IP Address. For internal communication between resources in a virtual network Private IP Address is needed.
For setting up the lab the following IP Addressing scheme will be used:
Creating Azure Virtual Network (VNet):
Logon to AzurePortal and search Virtual Networks
Enter the Resource Group and Name
Allocate the IP Address
After allocating the IP Addresses 10.0.0.0/16 proceed to add the SubNets as per the table.
Click on Review + Create once all the SubNets are created.
Once successfully deployed
In the next article we will look at creating Azure resources within the various SubNets.