Azure virtual networks (VNet) allow users to logically isolate their Azure resources and expand their on-premises network to Azure. A VNet acts as a representation of a user's network in the cloud, allowing them to control IP addresses, DNS settings, security policies, and more. VNets can be segmented into subnets and connected to on-premises networks through options like site-to-site VPNs or Azure ExpressRoute. This provides enterprise-scale networking capabilities with connectivity and isolation similar to a traditional on-premises environment.

1. Azure Network Configuration
By: Lalit Rawat

2. AZURE VIRTUAL NETWORK
Azure virtual network (VNet) is a representation of your own network in the cloud. It is a logical isolation of the
Azure cloud dedicated to your subscription. You can fully control the IP address blocks, DNS settings, security
policies, and route tables within this network. You can also further segment your VNet into subnets and launch
Azure IaaS virtual machines (VMs) and/or Cloud services (PaaS role instances). Additionally, you can connect the
virtual network to your on-premises network using one of the connectivity options available in Azure. In essence,
you can expand your network to Azure, with complete control on IP address blocks with the benefit of enterprise
scale Azure provides.

3. •Isolation. VNets are completely isolated from one another. That allows you to create disjoint networks for development, testing,
and production that use the same CIDR address blocks.
•Access to the public Internet. All IaaS VMs and PaaS role instances in a VNet can access the public Internet by default. You can
control access by using Network Security Groups (NSGs).
•Access to VMs within the VNet. PaaS role instances and IaaS VMs can be launched in the same virtual network and they can
connect to each other using private IP addresses even if they are in different subnets without the need to configure a gateway or
use public IP addresses.
•Name resolution. Azure provides internal name resolution for IaaS VMs and PaaS role instances deployed in your VNet. You can
also deploy your own DNS servers and configure the VNet to use them.
•Security. Traffic entering and exiting the virtual machines and PaaS role instances in a VNet can be controlled using Network
Security groups.
•Connectivity. VNets can be connected to each other using network gateways or VNet peering. VNets can be connected to on-
premises data centers through site-to-site VPN networks or Azure ExpressRoute.

4. Site-to-Site VPN gateway connection is used to connect to your on-premises network using the Azure Resource Manager deployment model and the
Azure portal. Site-to-Site connections can be used for cross-premises and hybrid configurations.
Point-to-Site (P2S) configuration lets you create a secure connection from an individual client computer to a virtual network. A P2S connection is
useful when you want to connect to your VNet from a remote location, such as from home or a conference
Connecting a virtual network to another virtual network (VNet-to-VNet) is similar to connecting a VNet to an on-premises site location. Both
connectivity types use an Azure VPN gateway to provide a secure tunnel using IPsec/IKE. The VNets you connect can be in different regions, or in
different subscription
Microsoft Azure ExpressRoute extend our on-premises networks into the Microsoft cloud over a dedicated private connection facilitated by a
connectivity provider. With ExpressRoute, We can establish connections to Microsoft cloud services, such as Microsoft Azure, Office 365, and CRM
Online. Connectivity can be from an any-to-any (IP VPN) network, a point-to-point Ethernet network, or a virtual cross-connection through a
connectivity provider at a co-location facility. ExpressRoute connections do not go over the public Internet. ExpressRoute connections allows more
reliability, faster speeds, lower latencies, and higher security than typical connections over the Internet.

5.  Azure subscription.
 Validated VPN devices.
 IP Address Range located to On-premises Network.
 Externally facing public IP address for your VPN device
 Subnet Address Space
 DNS Server.
 SSL Certificate if Customer wants to create the P2S VPN.

6.  We need to create a virtual network.
 Please add address space
 We need to create the subnets from Azure
portal.
 Specify a DNS server
 Create a gateway subnet
 Create a gateway subnet
 We will create a virtual network gateway
 Create a local network gateway
 Customer need Configure VPN device.
 Create a Site-to-Site VPN connection
 Create the VPN connection
 Verify the VPN connection