If you don't already have a virtual network, create one.
Create a virtual network and a gateway subnet You can use these values to create a test environment, or refer to them to better understand the examples in this article. The examples in this article use the following values. None of the subnets of your on-premises network can over lap with the virtual network subnets that you want to connect to. When you create this configuration, you must specify the IP address range prefixes that Azure will route to your on-premises location. If you are unfamiliar with the IP address ranges located in your on-premises network configuration, you need to coordinate with someone who can provide those details for you.Verify that you have an externally facing public IPv4 address for your VPN device.For more information about compatible VPN devices and device configuration, see About VPN Devices. Make sure you have a compatible VPN device and someone who is able to configure it.Verify that you have met the following criteria before beginning your configuration:
For more information about VPN gateways, see About VPN gateway. This type of connection requires a VPN device located on-premises that has an externally facing public IP address assigned to it. You can also create this configuration using a different deployment tool or deployment model by selecting a different option from the following list:Ī Site-to-Site VPN gateway connection is used to connect your on-premises network to an Azure virtual network over an IPsec/IKE (IKEv1 or IKEv2) VPN tunnel. The steps in this article apply to the Resource Manager deployment model. This article shows you how to use PowerShell to create a Site-to-Site VPN gateway connection from your on-premises network to the VNet. Create a VNet with a Site-to-Site VPN connection using PowerShell
0 kommentar(er)
