Azure offers a Networking Service called VPN Gateway. Customers can connect to their cloud resources and on-premises systems using network services. They also help in managing and protecting the network. They also assist customers in delivering their apps.

Azure Virtual Network
Azure Virtual Network is the representation of the physical network infrastructure using two Virtual Machines located in Azure. Virtual Network is responsible for enabling customers to manage, monitor, secure, and create connectivity between Azure resources and their on-premise environment. They can be broken down into smaller segments called Subnets. Subnets serve two main purposes:
Customers can manage their IP addresses more effectively.
To apply security rules and filters across multiple resources within the subnet, group similar resources together.

You have the option to choose how to manage Subnets or Virtual Networks, and how to represent your Networking Infrastructure. Multiple resources can be grouped within the same subnet. Virtual Networks are only allowed to reside in a particular region and can only spawn resources there. To make your multi-regional application work, it would be helpful if there were multiple virtual networks. There are two ways to connect multiple virtual network:
VNet Peering is a way to combine multiple virtual networks into one virtual network.
VPN Gateway: It allows cross-communication between virtual networks on-premise.
Azure VPN Gateway
A VPN Gateway is a special type of virtual network gateway used to transmit encrypted traffic between an Azure virtual network area and an on-premise area via the public internet. These gateways provide cross-premises connectivity between Azure and customer premises. You can also use a VPN gateway for encrypted traffic between Azure virtual networks via the Microsoft network. VPN gateways can be used to connect virtual networks to one another. One VPN gateway can be used to connect a single virtual network. Multiple connections can be made to the same VPN gateway. This allows all VPN tunnels to share the gateway bandwidth.

Azure VPN Gateway Configuration
A VPN gateway connection depends on multiple resources that have been configured with specific settings. Although some resources need to be ordered, most resources can be configured separately. For example:
Settings: These settings are a great example of how to make a successful connection.
Tools for deployment
You can create and configure resources using any configuration tool such as the Azure portal. Later, you can decide to use PowerShell to modify existing resources or to make them more useful. It is not possible to configure every resource or resource setting in Azure portal. Azure currently offers two deployment models:
Resource Manager
The key characteristics of VPN Gateway
It connects on-premise traffic to Azure traffic via the public web service.
It is used for cross-regional communication in Azure virtual networks.
It is used to connect virtual networks.
It is used to transmit encrypted traffic between Azure virtual network.
It can be deployed in Azure availability areas.

Azure VPN Gateway Setup
These are the elements of the VPN Gateway setup:
Virtual network gateway
Gateway to the local network
Gateway subnet
Azure VPN Gateway Topology
Azure VPN Gateways are configurable in many ways:
Site-to-Site: This VPN gateway connection, also known as an S2S connection, is used for cross-premises or hybrid configurations. This connection is made over IPsec/IKE (IKEv1 VPN tunnel or IKEv2). It involves a VP