Configure Azure Site-to-Site VPN Configuration Step by Step DEMO

This lecture Demos step by step Azure Site-to-Site (S2-S2) VPN Configuration DEMO
Configure a Point-to-Site VPN connection to a VNet DEMO
Step by Step How to Creating and Configuring Site-to-Site DEMO
Connecting to Microsoft Azure Using Site-to-Site VPN DEMO
How to Create A Site to Site (S2S) VPN In Azure DEMO
A step-by-Step guide to configuring site-to-site VPN Gateway DEMO
A step-by-Step guide to Azure Point-to-Site VPN DEMO

Azure VPN gateways provide cross-premises connectivity between customer premises and Azure. This tutorial shows you how to use the Azure portal to create a Site-to-Site VPN gateway connection from your on-premises network to the VNet

What is VPN Gateway?
A VPN gateway is a specific type of virtual network gateway that is used to send encrypted traffic between an Azure virtual network and an on-premises location over the public Internet. You can also use a VPN gateway to send encrypted traffic between Azure virtual networks over the Microsoft network. Each virtual network can have only one VPN gateway. However, you can create multiple connections to the same VPN gateway. When you create multiple connections to the same VPN gateway, all VPN tunnels share the available gateway bandwidth.
What is a virtual network gateway?
A virtual network gateway is composed of two or more VMs that are deployed to a specific subnet you create called the gateway subnet. Virtual network gateway VMs contain routing tables and run specific gateway services. These VMs are created when you create the virtual network gateway. You can't directly configure the VMs that are part of the virtual network gateway.

When you configure a virtual network gateway, you configure a setting that specifies the gateway type. The gateway type determines how the virtual network gateway will be used and the actions that the gateway takes. The gateway type 'Vpn' specifies that the type of virtual network gateway created is a 'VPN gateway'. This distinguishes it from an ExpressRoute gateway, which uses a different gateway type. A virtual network can have two virtual network gateways; one VPN gateway and one ExpressRoute gateway. For more information, see Gateway types.

Creating a virtual network gateway can take up to 45 minutes to complete. When you create a virtual network gateway, gateway VMs are deployed to the gateway subnet and configured with the settings that you specify. After you create a VPN gateway, you can create an IPsec/IKE VPN tunnel connection between that VPN gateway and another VPN gateway (VNet-to-VNet), or create a cross-premises IPsec/IKE VPN tunnel connection between the VPN gateway and an on-premises VPN device (Site-to-Site). You can also create a Point-to-Site VPN connection (VPN over OpenVPN, IKEv2, or SSTP), which lets you connect to your virtual network from a remote location, such as from a conference or from home.

The virtual network gateway uses specific subnet called the gateway subnet. The gateway subnet is part of the virtual network IP address range that you specify when configuring your virtual network. It contains the IP addresses that the virtual network gateway resources and services use.

When you create the gateway subnet, you specify the number of IP addresses that the subnet contains. The number of IP addresses needed depends on the VPN gateway configuration that you want to create. Some configurations require more IP addresses than others. We recommend that you create a gateway subnet that uses a /27 or /28.

If you see an error that specifies that the address space overlaps with a subnet, or that the subnet is not contained within the address space for your virtual network, check your VNet address range. You may not have enough IP addresses available in the address range you created for your virtual network. For example, if your default subnet encompasses the entire address range, there are no IP addresses left to create additional subnets. You can either adjust your subnets within the existing address space to free up IP addresses, or specify an additional address range and create the gateway subnet there.

The local network gateway is a specific object that represents your on-premises location (the site) for routing purposes. You give the site a name by which Azure can refer to it, then specify the IP address of the on-premises VPN device to which you will create a connection. You also specify the IP address prefixes that will be routed through the VPN gateway to the VPN device. The address prefixes you specify are the prefixes located on your on-premises network.

Timestamps:
0:00 -Intro

#PaddyMaddy #cloudComputing #azuretutorial #microsoftazuretutorialforbeginners #azureforbeginners #azurebasics #microsoftazuretraining #Az900 #AZ500, #microsoftazurecertification, #AZ303 #300 #104 #paddyMaddy #azuretraining #AZ104

[PaddyMaddy]

Your Comments helps me to do more and more videos to

[asifsmu]

Wonderful Explanation, It has cleared all of my doubts.!!

[roshansharma]

Thanks for Sharing wonderful Videos. Could you please make a detailed video on Azure Subscription and Tenant with different real-time scenario. For example how to give access to a single user in different subscription. How a single user can be a member of multiple tenants, how to switch, pros and cons. It would be a great help 🙂. Thanks again and Stay Safe..!!

[rashidamin]

Why not just create virtual network pairing from shell? Is that the same thing?

[chandugamingyt]

Even site to site same process right? Bro ..?

[srich]

Is it possible for Azure VPN users to get company wallpaper? if it is possible how to do that please help?

[srich]

Is it possible to configure Azure to Azure (site 2 site VPN)

[srich]

if you provide online classes please provide contact details. not Udemy. thank you