Create a VNet with a Site-to-Site connection using the Azure classic portal
This article walks you through creating a virtual network and a site-to-site VPN connection to your on-premises network using the classic deployment model and the classic portal. Site-to-Site connections can be used for cross-premises and hybrid configurations. Currently, you cannot create an end-to-end Site-to-Site configuration for the classic deployment model using the Azure portal.
It's important to know that Azure currently works with two deployment models: Resource Manager and classic. Before you begin your configuration, make sure that you understand the deployment models and tools. You'll need to know which model that you want to work in. Not all networking features are supported yet for both models. For information about the deployment models, see Understanding Resource Manager deployment and classic deployment.
|Classic Deployment||Resource Manager Deployment|
|Classic Portal||Article*||Not Supported|
(*) denotes that the classic portal can only support creating one S2S VPN connection.
(**) denotes that an end-to-end scenario is not yet available for the Azure portal.
(+) denotes that this article is written for multi-site connections.
If you want to connect VNets together, see Configure a VNet-to-VNet connection for the classic deployment model.
Verify that you have the following items before beginning configuration.
A compatible VPN device and someone who is able to configure it. See About VPN Devices. If you aren't familiar with configuring your VPN device, or 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.
An externally facing public IP address for your VPN device. This IP address cannot be located behind a NAT.
Log in to the Azure classic portal.
In the lower left corner of the screen, click New. In the navigation pane, click Network Services, and then click Virtual Network. Click Custom Create to begin the configuration wizard.
To create your VNet, enter your configuration settings on the following pages:
Enter the following information:
- Name: Name your virtual network. For example, EastUSVNet. You'll use this virtual network name when you deploy your VMs and PaaS instances, so you may not want to make the name too complicated.
- Location: The location is directly related to the physical location (region) where you want your resources (VMs) to reside. For example, if you want the VMs that you deploy to this virtual network to be physically located in East US, select that location. You can't change the region associated with your virtual network after you create it.
Enter the following information, and then click the next arrow on the lower right.
- DNS Servers: Enter the DNS server name and IP address, or select a previously registered DNS server from the shortcut menu. This setting does not create a DNS server. It allows you to specify the DNS servers that you want to use for name resolution for this virtual network.
- Configure Site-To-Site VPN: Select the checkbox for Configure a site-to-site VPN.
- Local Network: A local network represents your physical on-premises location. You can select a local network that you've previously created, or you can create a new local network. However, if you select to use a local network that you previously created, go to the Local Networks configuration page and verify that the VPN Device IP address (public facing IPv4 address) for the VPN device is accurate.
If you're creating a new local network, you'll see the Site-To-Site Connectivity page. If you want to use a local network that you previously created, this page will not appear in the wizard and you can move on to the next section.
Enter the following information, and then click the next arrow.
- Name: The name you want to call your local (on-premises) network site.
- VPN Device IP Address: The public facing IPv4 address of your on-premises VPN device that you use to connect to Azure. The VPN device cannot be located behind a NAT.
- Address Space: Include Starting IP and CIDR (Address Count). You specify the address range(s) that you want to be sent through the virtual network gateway to your local on-premises location. If a destination IP address falls within the ranges that you specify here, it is routed through the virtual network gateway.
- Add address space: If you have multiple address ranges that you want to be sent through the virtual network gateway, specify each additional address range. You can add or remove ranges later on the Local Network page.
Specify the address range that you want to use for your virtual network. These are the dynamic IP addresses (DIPS) that will be assigned to the VMs and other role instances that you deploy to this virtual network.
It's especially important to select a range that does not overlap with any of the ranges that are used for your on-premises network. You need to coordinate with your network administrator. Your network administrator may need to carve out a range of IP addresses from your on-premises network address space for you to use for your virtual network.
Enter the following information, and then click the checkmark on the lower right to configure your network.
- Address Space: Include Starting IP and Address Count. Verify that the address spaces you specify don't overlap any of the address spaces that you have on your on-premises network.
- Add subnet: Include Starting IP and Address Count. Additional subnets are not required, but you may want to create a separate subnet for VMs that will have static DIPS. Or you might want to have your VMs in a subnet that is separate from your other role instances.
- Add gateway subnet: Click to add the gateway subnet. The gateway subnet is used only for the virtual network gateway and is required for this configuration.
Click the checkmark on the bottom of the page and your virtual network will begin to create. When it completes, you will see Created listed under Status on the Networks page in the Azure Classic Portal. After the VNet has been created, you can then configure your virtual network gateway.
Associating a Network Security Group (NSG) to the GatewaySubnet will cause your VPN gateway to stop functioning as expected. DO NOT associate NSGs to Gateway subnets.
Configure the virtual network gateway to create a secure site-to-site connection. See Configure a virtual network gateway in the Azure classic portal.
Once your connection is complete, you can add virtual machines to your virtual networks. See the Virtual Machines documentation for more information.