Skip to content

Commit cd3c9ea

Browse files
Merge pull request #310284 from tracsman/main
Update Advanced Connectivity VPN Gateway for GA
2 parents 7b7d3a3 + d3c5f5a commit cd3c9ea

1 file changed

Lines changed: 38 additions & 4 deletions

File tree

articles/vpn-gateway/site-to-site-high-bandwidth-tunnel.md

Lines changed: 38 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,24 +1,27 @@
11
---
2-
title: 'Create a site-to-site high bandwidth tunnels in the Azure portal'
2+
title: 'Create site-to-site high bandwidth tunnels in the Azure portal'
33
description: In this article, you learn how to create a VPN Gateway site-to-site IPsec with High Bandwidth tunnels to establish connection between your on-premises network and a virtual network through the ExpressRoute private peering.
44
titleSuffix: Azure VPN Gateway
55
author: fabferri
66
ms.author: jonor
77
ms.service: azure-vpn-gateway
88
ms.topic: tutorial
9-
ms.date: 07/18/2025
9+
ms.date: 01/08/2026
1010

1111
#customer intent: As a network engineer, I want to create a site-to-site VPN connection between my on-premises location and my Azure virtual network with High Bandwidth tunnels with transit through ExpressRoute private peering.
1212
---
1313

14-
# Create a site-to-site high bandwidth tunnels in the Azure portal **(Preview)**
14+
# Create site-to-site high bandwidth tunnels in the Azure portal
1515

1616
The Azure VPN Gateway High Bandwidth tunnels feature, part of the Advanced Connectivity capabilities, delivers enhanced tunnel throughput for high-performance IPsec connections between your on-premises network and Azure virtual network. These tunnels are established between your on-premises VPN device and the Azure VPN Gateway, with traffic transiting through ExpressRoute private peering. High Bandwidth tunnels use private IP addresses on-premises to establish a secure, encrypted overlay network between your on-premises infrastructure and Azure.
1717

1818
High Bandwidth tunnels provide end-to-end encryption to meet security compliance requirements and eliminate encryption bottlenecks. This feature enables you to establish up to four IPsec tunnels between the Azure VPN Gateway and your on-premises VPN device—organized as two Connections, each supporting two tunnels. Each tunnel can deliver up to 5 Gbps of encrypted throughput, for a combined maximum of 20 Gbps. The following network diagram illustrates this configuration:
1919

2020
:::image type="content" source="media/site-to-site-high-bandwidth-tunnel/transit-high-bandwidth-tunnels.png" alt-text="Diagram showing Transit High Bandwidth IPsec tunnels architecture.":::
2121

22+
> [!IMPORTANT]
23+
> There are know issues and regional limitations with this VPN Gateway. Ensure you're familiar with the limitations listed at the end of this document!
24+
2225
## Prerequisites
2326

2427
To use VPN Gateway High Bandwidth tunnels, your ExpressRoute Connection must have FastPath enabled. FastPath is currently supported only on ExpressRoute Direct port pairs. As a result, your ExpressRoute circuit must be provisioned on an ExpressRoute Direct port pair to support this solution.
@@ -217,7 +220,7 @@ Configuring your on-premises VPN device is the final step. At this stage, you sh
217220

218221
When configuring your VPN device, you need the following details:
219222

220-
- **Shared key (preshared key)**: This key is specified when you create your site-to-site VPN connections. While the examples use a simple key, we recommend generating a complex, secure key for production environments.
223+
- **Shared key (pre-shared key)**: This key is specified when you create your site-to-site VPN connections. While the examples use a simple key, we recommend generating a complex, secure key for production environments.
221224
- **Private tunnel IP addresses of the Azure VPN Gateway**: Each VPN Gateway instance provides two private tunnel IPs, for a total of four IPsec tunnels in a High Bandwidth configuration. Many VPN devices support this setup using Virtual Tunnel Interfaces (VTIs), allowing each on-premises outbound interface IP to be associated with up to two VTIs.
222225
- **Azure virtual network address space**: The address range assigned to your Azure virtual network.
223226

@@ -286,6 +289,37 @@ If you no longer need the resources you created, you can delete them to avoid un
286289
3. When prompted, type the name of the resource group to confirm, then select **Delete**.
287290
This action permanently removes the resource group and all resources it contains.
288291

292+
## Unsupported Regions
293+
The advanced functionality of this gateway requires some of the latest hardware components. These components are available in most but not all Azure Regions. As of January 8, 2026, the Advanced Connectivity VPN Gateway WILL NOT deploy in the following regions:
294+
- Australia Central
295+
- Brazil South
296+
- Central US
297+
- Denmark East
298+
- East US 2
299+
- East US 2 EUAP
300+
- Korea Central
301+
- Malaysia South
302+
- Mexico Central
303+
- North Central US
304+
- North Europe
305+
- Qatar Central
306+
- South Central US
307+
- Southeast US 5
308+
- West Europe
309+
- West India
310+
- West US 2
311+
- West US 3
312+
313+
## Known Issues
314+
The first release of the Advanced Connectivity VPN Gateway doesn't support some VPN Gateway functions. This list is on our backlog and will be delivered as quickly as possible. The currently unsupported functions are:
315+
- Internet based VPN, currently this Gateway is only available over ExpressRoute Private Peering
316+
- IKEv1 and P2S aren't supported
317+
- No migration path from existing gateways
318+
- No APIPA support for BGP sessions
319+
- No NAT support
320+
- No IPv6 support
321+
- No interoperability with Virtual WAN (vWAN)
322+
289323
## Next steps
290324

291325
For more information about VPN Gateway, see the [VPN Gateway FAQ](vpn-gateway-vpn-faq.md).

0 commit comments

Comments
 (0)