PROVIDE A SHARED SERVICES HUB VIRTUAL NETWORK WITH ISOLATION AND SEGMENTATION

Open a browser and navigate to the Azure portal and login.
To create a Virtual Network, in the search bar at the top of the portal type “Virtual Networks” and select “Virtual Networks” from the results.
In the “Virtual Networks” portal pane, select ““+ Create”.

Fill out all the tabs of the creation process by using the values in the following table:

Resource group: RG1
Name: app-vnet
Region: East US
IPv4 address space: 10.1.0.0/16
Subnet name: frontend
Subnet address range: 10.1.0.0/24
Subnet name: backend
Subnet address range: 10.1.1.0/24
Note: Leave all other settings as their defaults. Select “Next” to advance to the next tab, and Create to create the virtual network.

Following the same steps as above, create the Azure virtual network Hub-vnet by using the values in the following table:

Resource group: RG1
Name: Hub-vnet
Region: East US
IPv4 address space: 10.0.0.0/16
Subnet name: AzureFirewallSubnet
Subnet address range: 10.0.0.0/24

Once the deployment is complete. Navigate back to the portal, in the search bar type “resource groups” and select Resource Groups” from the results. Select on “RG1” in the main pane and comfirm both virtual networks have been deployed.

SETUP A PEER RELATIONSHIP BETWEEN THE VIRTUAL NETWORKS:
Setting up a peer relationship between the two virtual networks will allow traffic to flow in both directions between the app-vnet and hub-vnet virtual networks.
In the Portal in the RG1 resource group view. Select on the “app-vnet” virtual network.
On the app-vnet context menu on the left hand side of the portal scroll down and select on peerings
In the app-vnet peerings pane, Select + Add.

Fill out the form using the values in the following table:

This virtual network Peering link name: app-vnet-to-hub
Remote virtual network Peering link name: hub-to-app-vnet
Virtual network: hub-vnet

Note: Leave all other settings as their defaults. Select “Add” to create the virtual network peering.

Once the process completes, and after the configuration updates. Validate that the Peering status is set to Connected. (you may have to refresh the page to see the updated status).