Configure a VPN gateway in the classic portal

If you want to create a secure cross-premises connection between Azure and your on-premises location, you need to create a virtual network gateway. A VPN gateway is a specific type of virtual network gateway. In the classic deployment model, a VPN gateway can be one of two VPN routing types: static, or dynamic. The VPN type you choose depends on both your network design plan, and the on-premises VPN device you want to use. For more information about VPN devices, see About VPN Devices.

About Azure deployment models

Azure currently works with two deployment models: Resource Manager and classic. The two models are not completely compatible with each other. Before you begin, you need to know which model that you want to work in. For information about the deployment models, see Understanding deployment models. If you are new to Azure, we recommend that you use the Resource Manager deployment model.

Configuration overview

The following steps walk you through configuring your VPN gateway in the classic portal. These steps apply to gateways for virtual networks that were created using the classic deployment model. Currently, not all of the configuration settings for gateways are available in the Azure portal. When they are, we will create a new set of instructions that apply to the Azure portal.

Before you begin

Before you configure your gateway, you first need to create your virtual network. For steps to create a virtual network for cross-premises connectivity, see Configure a virtual network with a site-to-site VPN connection, or Configure a virtual network with a point-to-site VPN connection. Then, use the following steps to configure the VPN gateway and gather the information you need to configure your VPN device.

If you already have a VPN gateway and you want to change the VPN routing type, see How to change the VPN routing type for your gateway.

Create a VPN gateway

  1. In the Azure classic portal, on the Networks page, verify that the status column for your virtual network is Created.
  2. In the Name column, click the name of your virtual network.
  3. On the Dashboard page, notice that this VNet doesn't have a gateway configured yet. You'll see this status as you go through the steps to configure your gateway.

Gateway Not Created

Next, at the bottom of the page, click Create Gateway. You can select either Static Routing or Dynamic Routing. The VPN routing type you select depends on few factors. For example, what your VPN device supports and whether you need to support point-to-site connections. Check About VPN Devices for Virtual Network Connectivity to verify the VPN routing type that you need. Once the gateway has been created, you can't change between gateway VPN routing types without deleting and re-creating the gateway. When the system prompts you to confirm that you want the gateway created, click Yes.

Gateway VPN routing type

When your gateway is creating, notice the gateway graphic on the page changes to yellow and says Creating Gateway. It may take up to 45 minutes for the gateway to create. Wait until the gateway is complete before you can move forward with other configuration settings.

Gateway Creating

When the gateway changes to Connecting, you can gather the information you'll need for your VPN device.

Gateway Connecting

Site-to-Site connections

Step 1. Gather information for your VPN device configuration

If you are creating a Site-to-Site connection, after the gateway has been created, gather information for your VPN device configuration. This information is located on the Dashboard page for your virtual network:

  1. Gateway IP address - The IP address can be found on the Dashboard page. You won't be able to see it until after your gateway has finished creating.
  2. Shared key - Click Manage Key at the bottom of the screen. Click the icon next to the key to copy it to your clipboard, and then paste and save the key. This button only works when there is a single S2S VPN tunnel. If you have multiple S2S VPN tunnels, use the Get Virtual Network Gateway Shared Key API or PowerShell cmdlet.

Manage Key

Step 2. Configure your VPN device

Site-to-Site connections to an on-premises network require a VPN device. While we don't provide configuration steps for all VPN devices, you may find the information in the following links helpful:

  • For information about compatible VPN devices, see VPN Devices.
  • For links to device configuration settings, see Validated VPN Devices. These links are provided on a best-effort basis. It's always best to check with your device manufacturer for the latest configuration information.
  • For information about editing device configuration samples, see Editing samples.
  • For IPsec/IKE parameters, see Parameters.
  • Before configuring your VPN device, check for any Known device compatibility issues for the VPN device that you want to use.

When configuring your VPN device, you will need the following items:

  • The Public IP address of your virtual network gateway. You can locate this by going to the Overview blade for your virtual network.
  • A shared key. This is the same shared key that you specify when creating your Site-to-Site VPN connection. In our examples, we use a very basic shared key. You should generate a more complex key to use.

After the VPN device has been configured, you can view your updated connection information on the Dashboard page for your VNet.

Step 3. Verify your local network ranges and VPN gateway IP address

Verify your VPN gateway IP address

For gateway to connect properly, the IP address for your VPN device must be correctly configured for the Local Network that you specified for your cross-premises configuration. Typically, this is configured during the site-to-site configuration process. However, if you previously used this local network with a different device, or the IP address has changed for this local network, edit the settings to specify the correct Gateway IP address.

  1. To verify your gateway IP address, click Networks on the left portal pane and then select Local Networks at the top of the page. You'll see the VPN Gateway Address for each local network that you have created. To edit the IP address, select the VNet and click Edit at the bottom of the page.
  2. On the Specify your local network details page, edit the IP address, and then click the next arrow at the bottom of the page.
  3. On the Specify the address space page, click the checkmark on the lower right to save your settings.

Verify the address ranges for your local networks

For the correct traffic to flow through the gateway to your on-premises location, you need to verify that each IP address range is specified. Each range must be listed in your Azure Local Networks configuration. Depending on the network configuration of your on-premises location, this can be a somewhat large task. Traffic that is bound for an IP address that is contained within the listed ranges will be sent through the virtual network VPN gateway. The ranges that you list don't have to be private ranges, although you will want to verify that your on-premises configuration can receive the inbound traffic.

To add or edit the ranges for a Local Network, use the following steps:

  1. To edit the IP address ranges for a local network, click Networks on the left portal pane and then select Local Networks at the top of the page. In the portal, the easiest way to view the ranges that you've listed is on the Edit page. To see your ranges, select the VNet and click Edit at the bottom of the page.
  2. On the Specify your local network details page, don't make any changes. Click the next arrow at the bottom of the page.
  3. On the Specify the address space page, make your network address space changes. Then click the checkmark to save your configuration.

How to view gateway traffic

You can view your gateway and gateway traffic from your Virtual Network Dashboard page.

On the Dashboard page you can view the following:

  • The amount of data that is flowing through your gateway, both data in and data out.
  • The names of the DNS servers that are specified for your virtual network.
  • The connection between your gateway and your VPN device.
  • The shared key that is used to configure your gateway connection to your VPN device.

How to change the VPN routing type for your gateway

Because some connectivity configurations are only available for certain gateway routing types, you may find that you need to change the gateway VPN routing type of an existing VPN gateway. For example, you may want to add point-to-site connectivity to an already existing site-to-site connection that has a static gateway. Point-to-site connections require a dynamic gateway. This means to configure a P2S connection, you have to change your gateway VPN routing type from static to dynamic.

If you need to change a gateway VPN routing type, you'll delete the existing gateway, and then create a new gateway with the new routing type. You don't need to delete the entire virtual network to change the gateway routing type.

Before changing your gateway VPN routing type, be sure to verify that your VPN device supports the routing type that you want to use. To download new routing configuration samples and check VPN device requirements, see About VPN Devices for Virtual Network Connectivity.


When you delete a virtual network VPN gateway, the VIP assigned to the gateway is released. When you recreate the gateway, a new VIP is assigned to it.

  1. Delete the existing VPN gateway.

    On the Dashboard page for your virtual network, navigate to the bottom of the page and click Delete Gateway. Wait for the notification that the gateway has been deleted. Once you receive the notification on the screen that your gateway has been deleted, you can create a new gateway.

  2. Create a new VPN gateway.

    Use the procedure at the top of the page to create a new gateway: Create a VPN gateway.

Next steps

You can add virtual machines to your virtual network. See How to create a custom virtual machine.

If you want to configure a point-to-site VPN connection, see Configure a point-to-site VPN connection.