Virtual Network Gateways

Virtual network gateways are used to send encrypted traffic between an Azure virtual network and an on-premises location over the public Internet. They are also used to send encrypted traffic between Azure virtual networks.

Types of Virtual Network Gateways

Azure offers two primary types of virtual network gateways:

Key Concepts

Gateway Subnet

A dedicated subnet within your virtual network, named GatewaySubnet, is required for deploying a virtual network gateway. This subnet must be at least /27 in size.

# Example of a GatewaySubnet configuration ResourceGroup: MyResourceGroup VirtualNetwork: MyVNet SubnetName: GatewaySubnet AddressPrefix: 10.1.255.0/27

Gateway IP Configuration

A public IP address is required for a VPN gateway to allow connections from the internet. An ExpressRoute gateway requires a private IP address.

Connections

Connections are established between the virtual network gateway and the remote network (on-premises, another VNet, or a partner site). These connections define the shared key, tunnel type, and other parameters.

Deployment Considerations

Note: Deployment of a virtual network gateway can take a significant amount of time, often 45 minutes or more. Plan accordingly for your network architecture.

High Availability

Azure Virtual Network Gateways support active-dynamic and active-active configurations for enhanced availability and redundancy.

SKUs

Different SKUs (Stock Keeping Units) are available for VPN and ExpressRoute gateways, offering varying levels of performance, throughput, and features. Choose the SKU that best matches your requirements.

Use Cases

Tip: For robust and high-performance connectivity, consider using ExpressRoute for dedicated private connections to Azure.

Further Reading