Skip to content

Commit d1b01b5

Browse files
denreadenrea
authored
Merge pull request #176427 from jaidharosenblatt/s2s-100-connection
Update S2S connection limit for VpnGW4 and VpnGw5 from 30 to 100 tunnels
2 parents b76af69 + b01861e commit d1b01b5

File tree

3 files changed

+23
-23
lines changed

3 files changed

+23
-23
lines changed

‎articles/vpn-gateway/vpn-gateway-connect-multiple-policybased-rm-ps.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -33,12 +33,12 @@ The following diagrams highlight the two models:
3333
### Azure support for policy-based VPN
3434
Currently, Azure supports both modes of VPN gateways: route-based VPN gateways and policy-based VPN gateways. They are built on different internal platforms, which result in different specifications:
3535

36-
| Category | PolicyBased VPN Gateway | RouteBased VPN Gateway | RouteBased VPN Gateway |
37-
| -------- | ----------------------- | ---------------------- | ---------------------- |--- |
38-
| **Azure Gateway SKU** | Basic | Basic | VpnGw1, VpnGw2, VpnGw3, VpnGw4, VpnGw5 |
39-
| **IKE version** | IKEv1 | IKEv2 | IKEv1 and IKEv2 |
40-
| **Max. S2S connections** | **1** | 10 | 30 |
41-
| | | | |
36+
| Category | PolicyBased VPN Gateway | RouteBased VPN Gateway | RouteBased VPN Gateway | RouteBased VPN Gateway
37+
| -------- | ----------------------- | ---------------------- | ---------------------- | ----------------------- |
38+
| **Azure Gateway SKU** | Basic | Basic | VpnGw1, VpnGw2, VpnGw3 | VpnGw4 and VpnGw5 |
39+
| **IKE version** | IKEv1 | IKEv2 | IKEv1 and IKEv2 | IKEv1 and IKEv2 |
40+
| **Max. S2S connections** | **1** | 10 | 30 | 100 |
41+
| | | | | |
4242

4343
With the custom IPsec/IKE policy, you can now configure Azure route-based VPN gateways to use prefix-based traffic selectors with option "**PolicyBasedTrafficSelectors**", to connect to on-premises policy-based VPN devices. This capability allows you to connect from an Azure virtual network and VPN gateway to multiple on-premises policy-based VPN/firewall devices, removing the single connection limit from the current Azure policy-based VPN gateways.
4444

‎includes/vpn-gateway-gwsku-include.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ The new VPN gateway SKUs streamline the feature sets offered on the gateways:
2929
| **SKU**| **Features**|
3030
| --- | --- |
3131
|**Basic** (**) | **Route-based VPN**: 10 tunnels for S2S/connections; no RADIUS authentication for P2S; no IKEv2 for P2S<br>**Policy-based VPN**: (IKEv1): 1 S2S/connection tunnel; no P2S|
32-
| **All Generation1 and Generation2 SKUs except Basic** | **Route-based VPN**: up to 30 tunnels (*), P2S, BGP, active-active, custom IPsec/IKE policy, ExpressRoute/VPN coexistence |
32+
| **All Generation1 and Generation2 SKUs except Basic** | **Route-based VPN**: up to 100 tunnels (*), P2S, BGP, active-active, custom IPsec/IKE policy, ExpressRoute/VPN coexistence |
3333
| | |
3434

3535
(*) You can configure "PolicyBasedTrafficSelectors" to connect a route-based VPN gateway to multiple on-premises policy-based firewall devices. Refer to [Connect VPN gateways to multiple on-premises policy-based VPN devices using PowerShell](../articles/vpn-gateway/vpn-gateway-connect-multiple-policybased-rm-ps.md) for details.

‎includes/vpn-gateway-table-gwtype-aggtput-include.md

Lines changed: 16 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -13,23 +13,23 @@
1313
|**VPN<br>Gateway<br>Generation** |**SKU** | **S2S/VNet-to-VNet<br>Tunnels** | **P2S<br> SSTP Connections** | **P2S<br> IKEv2/OpenVPN Connections** | **Aggregate<br>Throughput Benchmark** | **BGP** | **Zone-redundant** |
1414
|--- |--- | --- | --- | --- | --- | --- | ---|
1515
|**Generation1**|**Basic** | Max. 10 | Max. 128 | Not Supported | 100 Mbps | Not Supported| No |
16-
|**Generation1**|**VpnGw1** | Max. 30* | Max. 128 | Max. 250 | 650 Mbps | Supported | No |
17-
|**Generation1**|**VpnGw2** | Max. 30* | Max. 128 | Max. 500 | 1 Gbps | Supported | No |
18-
|**Generation1**|**VpnGw3** | Max. 30* | Max. 128 | Max. 1000 | 1.25 Gbps | Supported | No |
19-
|**Generation1**|**VpnGw1AZ**| Max. 30* | Max. 128 | Max. 250 | 650 Mbps | Supported | Yes |
20-
|**Generation1**|**VpnGw2AZ**| Max. 30* | Max. 128 | Max. 500 | 1 Gbps | Supported | Yes |
21-
|**Generation1**|**VpnGw3AZ**| Max. 30* | Max. 128 | Max. 1000 | 1.25 Gbps | Supported | Yes |
16+
|**Generation1**|**VpnGw1** | Max. 30 | Max. 128 | Max. 250 | 650 Mbps | Supported | No |
17+
|**Generation1**|**VpnGw2** | Max. 30 | Max. 128 | Max. 500 | 1 Gbps | Supported | No |
18+
|**Generation1**|**VpnGw3** | Max. 30 | Max. 128 | Max. 1000 | 1.25 Gbps | Supported | No |
19+
|**Generation1**|**VpnGw1AZ**| Max. 30 | Max. 128 | Max. 250 | 650 Mbps | Supported | Yes |
20+
|**Generation1**|**VpnGw2AZ**| Max. 30 | Max. 128 | Max. 500 | 1 Gbps | Supported | Yes |
21+
|**Generation1**|**VpnGw3AZ**| Max. 30 | Max. 128 | Max. 1000 | 1.25 Gbps | Supported | Yes |
2222
| | | | | | | | |
23-
|**Generation2**|**VpnGw2** | Max. 30* | Max. 128 | Max. 500 | 1.25 Gbps | Supported | No |
24-
|**Generation2**|**VpnGw3** | Max. 30* | Max. 128 | Max. 1000 | 2.5 Gbps | Supported | No |
25-
|**Generation2**|**VpnGw4** | Max. 30* | Max. 128 | Max. 5000 | 5 Gbps | Supported | No |
26-
|**Generation2**|**VpnGw5** | Max. 30* | Max. 128 | Max. 10000 | 10 Gbps | Supported | No |
27-
|**Generation2**|**VpnGw2AZ**| Max. 30* | Max. 128 | Max. 500 | 1.25 Gbps | Supported | Yes |
28-
|**Generation2**|**VpnGw3AZ**| Max. 30* | Max. 128 | Max. 1000 | 2.5 Gbps | Supported | Yes |
29-
|**Generation2**|**VpnGw4AZ**| Max. 30* | Max. 128 | Max. 5000 | 5 Gbps | Supported | Yes |
30-
|**Generation2**|**VpnGw5AZ**| Max. 30* | Max. 128 | Max. 10000 | 10 Gbps | Supported | Yes |
31-
32-
(*) Use [Virtual WAN](../articles/virtual-wan/virtual-wan-about.md) if you need more than 30 S2S VPN tunnels.
23+
|**Generation2**|**VpnGw2** | Max. 30 | Max. 128 | Max. 500 | 1.25 Gbps | Supported | No |
24+
|**Generation2**|**VpnGw3** | Max. 30 | Max. 128 | Max. 1000 | 2.5 Gbps | Supported | No |
25+
|**Generation2**|**VpnGw4** | Max. 100* | Max. 128 | Max. 5000 | 5 Gbps | Supported | No |
26+
|**Generation2**|**VpnGw5** | Max. 100* | Max. 128 | Max. 10000 | 10 Gbps | Supported | No |
27+
|**Generation2**|**VpnGw2AZ**| Max. 30 | Max. 128 | Max. 500 | 1.25 Gbps | Supported | Yes |
28+
|**Generation2**|**VpnGw3AZ**| Max. 30 | Max. 128 | Max. 1000 | 2.5 Gbps | Supported | Yes |
29+
|**Generation2**|**VpnGw4AZ**| Max. 100* | Max. 128 | Max. 5000 | 5 Gbps | Supported | Yes |
30+
|**Generation2**|**VpnGw5AZ**| Max. 100* | Max. 128 | Max. 10000 | 10 Gbps | Supported | Yes |
31+
32+
(*) Use [Virtual WAN](../articles/virtual-wan/virtual-wan-about.md) if you need more than 100 S2S VPN tunnels.
3333

3434
* The resizing of VpnGw SKUs is allowed within the same generation, except resizing of the Basic SKU. The Basic SKU is a legacy SKU and has feature limitations. In order to move from Basic to another VpnGw SKU, you must delete the Basic SKU VPN gateway and create a new gateway with the desired Generation and SKU size combination. You can only resize a Basic gateway to another legacy SKU (see [Working with Legacy SKUs](../articles/vpn-gateway/vpn-gateway-about-skus-legacy.md)).
3535

0 commit comments

Comments
 (0)