Azure Virtual Network (VNet) is a fundamental building block for private network in Azure. VNet enables many types of Azure resources, such as Azure Virtual Machines (VMs), to securely communicate with each other, the internet, and on-premises networks.
Provided you were given an IP Address 192.148.30.0/26 to create four subnets for it, With the step to step guide written below, you will be able to successfully create VNet.
Step 1: Login to Azure Portal
- Go to Azure Portal and log in with your credentials.
- From the Azure display screen, choose the virtual network icon or in the Search the Marketplace search box, type Virtual Network and select Virtual Network from the results.
- Click Create.
Step 2: Configure the Virtual Network
Basics Tab:
- Resource Group:Select an existing resource group or create a new one.
- Name: Enter a name for your virtual network.
- Region: Select the region where you want to deploy the virtual network.
IP Addresses Tab:
- IPv4 Address Space: Define the address space (e.g.,192.148.30.0/26).
- Add the four Subnets(accounting, marketing, finance and banking departments)
- Subnet Name: Enter a name for the first subnet (e.g.,Accounting-dept).
- Subnet Address Range: Define the address range for the subnet (e.g., 192.148.30.0/26).
- Click + Add subnet to add additional subnets.
- Repeat the process to create the remaining three subnets with different address ranges (e.g.,192.148.30.0/26,192.148.30.64/26, 192.148.30.128/26 and 192.148.30.192/26)
Step 3: Review + Create, Leave the security and tags tabs at default.
- Review the settings in the Review + create tab and click on create to deploy.
Step 4 After deployment of the virtual network with the specified subnets, click on “Go to resource” and overview to see it running.
NOTE: Click on subnets to view the four subnets you created ,you can always create another subnet by clicking on the +Subnet tab.
Azure Virtual Network provides isolation, security, scalability, high availability, subnet segmentation, internet connectivity, and seamless integration with on-premises networks.