Azure VNet – Step-by-Step to create your own Virtual Network
Virtual Network and its benefits
A virtual network is a network overlay that you can configure in Azure. VMs and services that are part of the same virtual network can access each other. However, services outside the virtual network have no way to identify or connect to services hosted within virtual networks unless you decide to configure that specific type of connection, as in the case of VNet to VNet configurations. This provides an added layer of isolation to your services. Azure Virtual Network also lets you extend your network into Azure and treat deployments as a natural extension to your on-premises network.
|Enhanced security and isolation||VNet provides an isolated and secure environment to run your VMs and applications. You can bring your private IP addresses, define subnets, access control policies and much more. With virtual networks, you get to treat Azure just as your own datacenter. Services outside the virtual network have no way to identify or connect to services hosted within virtual networks. This provides an added layer of isolation to your services.|
|Extend your on-premises network to the cloud||With VNet, you can build hybrid cloud applications that securely connect to your on-premises datacenter. You can join VMs in Azure to your domain running on-premises. You can access and leverage all on-premises investments around monitoring and identity for your services hosted in Azure.|
|IaaS and PaaS, better together||With VNet, you can build services that rely on Cloud Services and Virtual Machines. Use Azure web roles for your front end and Virtual Machines for backend databases. Combining Platform-as-a-Service (PaaS) and Infrastructure-as-a-Service (IaaS) within a Virtual Network gives you more flexibility and scalability in building apps.|
Considerations of using VNets
- When you need to create Cross-premise connection or Hybrid solution to connect your on-premise network with your Azure environment.
- When your VMs or Cloud services need to communicate directly with other within Azure.
Concepts you must know before starting with VNet
|CIDR||Classless Inter-Domain Routing is a method for allocating IP addresses and routing Internet Protocol packets. It is a way to allocate and specify the Internet addresses used in inter-domain routing more flexibly than with the original system of Internet Protocol (IP) address classes. As a result, the number of available Internet addresses has been greatly increased. CIDR is now the routing system used by virtually all gateway hosts on the Internet’s backbone network.|
|Subnet||A subnet (short for “subnetwork”) is an identifiably separate part of an organization’s network. Typically, a subnet may represent all the machines at one geographic location, in one building, or on the same local area network (LAN).|
|Address Space||An address space defines a range of discrete addresses, each of which may correspond to a network host, peripheral device, disk sector, a memory cell or other logical or physical entity.|
Step-by-step to create your own VNet
To create your own virtual network, do the following after you access to Azure Portal.
In the lower left-hand corner of the screen, click New > Network Services > Virtual Network, and then click Custom Create to begin the configuration wizard.
Type your network name and its location in Virtual Network Detail.
In next step – DNS Server and VPN Connectivity – you can input information of DNS Server or select option to connect your VNet with other network with VPN configurations. I left them blank as default and will come back and update later.
Just like a real network, the virtual network needs a range of IP addresses (known as an address space) to assign to virtual machines that you place within it. The virtual network also supports subnets, which need their own address spaces, derived from the virtual network address space. You can update configuration later of required.
Click OK button and wait for a while and you have the first VNet within Azure.