Create a virtual network using the Azure portal
An Azure virtual network (VNet) is a representation of your own network in the cloud. You can control your Azure network settings and define DHCP address blocks, DNS settings, security policies, and routing. You can also further segment your VNet into subnets and deploy Azure IaaS virtual machines (VMs) and PaaS role instances, in the same way you can deploy physical and virtual machines to your on-premises datacenter. In essence, you can expand your network to Azure, bringing your own IP address blocks. Read the virtual network overview if you are not familiar with VNets.
Before you work with Azure resources, it's important to understand that Azure currently has two deployment models: Azure Resource Manager and classic. Make sure you understand deployment models and tools before you work with any Azure resource. You can view the documentation for different tools by clicking the tabs at the top of this article.
This document covers creating a VNet by using the Resource Manager deployment model. You can also create a virtual network in the classic deployment model by using the Azure preview portal.
To better illustrate how to create a VNet and subnets, this document will use the scenario below.
In this scenario you will create a VNet named TestVNet with a reserved CIDR block of 192.168.0.0./16. Your VNet will contain the following subnets:
- FrontEnd, using 192.168.1.0/24 as its CIDR block.
- BackEnd, using 192.168.2.0/24 as its CIDR block.
To create a VNet based on the scenario above by using the Azure preview portal, follow the steps below.
- From a browser, navigate to http://portal.azure.com and, if necessary, sign in with your Azure account.
Click NEW > Networking > Virtual network, then click Resource Manager from the Select a deployment model list, and then click Create, as seen in the figure below.
On the Create virtual network blade, configure the VNet settings as shown in the figure below.
Click Resource group and select a resource group to add the VNet to, or click Create new to add the VNet to a new resource group. The figure below shows the resource group settings for a new resource group called TestRG. For more information about resource groups, visit Azure Resource Manager Overview.
If necessary, change the Subscription and Location settings for your VNet.
If you do not want to see the VNet as a tile in the Startboard, disable Pin to Startboard.
Click Create and notice the tile named Creating Virtual network as shown in the figure below.
Wait for the VNet to be created, then in the Virtual network blade, click All settings > Subnets > Add as seen below.
Specify the subnet settings for the BackEnd subnet, as shown below, and then click OK.
Notice the list of subnets, as shown in the figure below.