Design and implement a Virtual Network in Microsoft Azure

Lab scenario

Now you’re ready to deploy virtual networks in the Azure portal.

Consider the fictional organization Exceedlabs Ltd, which is in the process of migrating infrastructure and applications to Azure. In your role as network engineer, you must plan and implement three virtual networks and subnets to support resources in those virtual networks.

The CoreServicesVnet virtual network is deployed in the East US region. This virtual network will have the largest number of resources. It will have connectivity to on-premises networks through a VPN connection. This network will have web services, databases, and other systems that are key to the operations of the business. Shared services, such as domain controllers and DNS also will be located here. A large amount of growth is anticipated, so a large address space is necessary for this virtual network.

The ManufacturingVnet virtual network is deployed in the West Europe region, near the location of your organization’s manufacturing facilities. This virtual network will contain systems for the operations of the manufacturing facilities. The organization is anticipating a large number of internal connected devices for their systems to retrieve data from, such as temperature, and will need an IP address space that it can expand into.

The ResearchVnet virtual network is deployed in the Southeast Asia region, near the location of the organization’s research and development team. The research and development team uses this virtual network. The team has a small, stable set of resources that is not expected to grow. The team needs a small number of IP addresses for a few virtual machines for their work.

You will create the following resources:

Virtual NetworkRegionVirtual network address spaceSubnetSubnet
CoreServicesVnetEast US10.20.0.0/16  
   GatewaySubnet10.20.0.0/27
   SharedServicesSubnet10.20.10.0/24
   DatabaseSubnet10.20.20.0/24
   PublicWebServiceSubnet10.20.30.0/24
ManufacturingVnetWest Europe10.30.0.0/16  
   ManufacturingSystemSubnet10.30.10.0/24
   SensorSubnet110.30.20.0/24
   SensorSubnet210.30.21.0/24
   SensorSubnet310.30.22.0/24
ResearchVnetSoutheast Asia10.40.0.0/16  
   ResearchSystemSubnet10.40.0.0/24

These virtual networks and subnets are structured in a way that accommodates existing resources yet allows for projected growth. Let’s create these virtual networks and subnets to lay the foundation for our networking infrastructure.

In this exercise, you will:

  • Task 1: Create the Exceedlabs resource group
  • Task 2: Create the CoreServicesVnet virtual network and subnets
  • Task 3: Create the ManufacturingVnet virtual network and subnets
  • Task 4: Create the ResearchVnet virtual network and subnets
  • Task 5: Verify the creation of VNets and Subnets

Prerequisites for this labs : Azure Account

Task 1: Create the Exceedlabs resource group

  • Go to Azure portal.
  • On the home page, under Azure services, select Resource groups.
  • In Resource groups, select + Create.
  • Use the information in the following table to create the resource group.
TabOptionValue
BasicsResource groupExceedlabsResourceGroup
 Region(US) East US
TagsNo changes required 
Review + createReview your settings and select Create   
  • In Resource groups, verify that ExceedlabsResourceGroup appears in the list.

Task 2: Create the CoreServicesVnet virtual network and subnets On the Azure portal home page, navigate to the Global Search bar and search Virtual Networks and select virtual networks under services.

Select Create on the Virtual networks page.

Use the information in the following table to create the CoreServicesVnet virtual network.
‎Remove or overwrite the default IP Address space

TabOptionValue
BasicsResource GroupExceedlabsResourceGroup
 NameCoreServicesVnet
 Region(US) East US
IP AddressesIPv4 address space10.20.0.0/16
  • Use the information in the following table to create the CoreServicesVnet subnets.
  • To begin creating each subnet, select + Add subnet. To finish creating each subnet, select Add.
SubnetOptionValue
GatewaySubnetSubnet nameGatewaySubnet
 Subnet address range10.20.0.0/27
SharedServicesSubnetSubnet nameSharedServicesSubnet
 Subnet address range10.20.10.0/24
DatabaseSubnetSubnet nameDatabaseSubnet
 Subnet address range10.20.20.0/24
PublicWebServiceSubnetSubnet namePublicWebServiceSubnet
 Subnet address range10.20.30.0/24
  • To finish creating the CoreServicesVnet and its associated subnets, select Review + create.
  • Verify your configuration passed validation, and then select Create.
  • Repeat steps 1 -8 for each VNet based on the tables below

Task 3: Create the ManufacturingVnet virtual network and subnets

TabOptionValue
BasicsResource GroupExceedlabsResourceGroup
 NameManufacturingVnet
 Region(Europe) West Europe
IP AddressesIPv4 address space10.30.0.0/16
SubnetOptionValue
ManufacturingSystemSubnetSubnet nameManufacturingSystemSubnet
 Subnet address range10.30.10.0/24
SensorSubnet1Subnet nameSensorSubnet1
 Subnet address range10.30.20.0/24
SensorSubnet2Subnet nameSensorSubnet2
 Subnet address range10.30.21.0/24
SensorSubnet3Subnet nameSensorSubnet3
 Subnet address range10.30.22.0/24

Task 4: Create the ResearchVnet virtual network and subnets

TabOptionValue
BasicsResource GroupExceedlabsResourceGroup
 NameResearchVnet
 RegionSoutheast Asia
IP AddressesIPv4 address space10.40.0.0/16
SubnetOptionValue
ResearchSystemSubnetSubnet nameResearchSystemSubnet
 Subnet address range10.40.0.0/24

Task 5: Verify the creation of VNets and Subnets

  • On the Azure portal home page, select All resources.
  • Verify that the CoreServicesVnet, ManufacturingVnet, and ResearchVnet are listed.
  • Note that Azure creates NetworkWatchers for each region that you use.
  • Select CoreServicesVnet.
  • In CoreServicesVnet, under Settings, select Subnets
In CoreServicesVnetSubnets, verify that the subnets you created are listed, and that the IP address ranges are correct.

Repeat steps 4 -6 for each VNet.

Congratulations! You have successfully created a resource group, three VNets, and their associated subnets.

Reminder: Don’t forget to delete or shutdown all unused Azure resources after your labs for cost saving

Leave a Reply

Your email address will not be published. Required fields are marked *