You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -19,36 +19,14 @@ ExpressRoute virtual network gateway is designed to exchange network routes and
19
19
20
20
### Circuits
21
21
22
-
FastPath is available on all ExpressRoute circuits. Support for virtual network peering and UDR over FastPath is now generally available in all regions within the public cloud and only for connections associated to ExpressRoute Direct circuits. Limited general availability (GA) support for Private Endpoint/Private Link connectivity is only available for connections associated to ExpressRoute Direct circuits and within limited regions & for limited services behind a private endpoint.
22
+
FastPath is available on ExpressRoute circuits.
23
23
24
-
### Gateways
25
-
26
-
FastPath still requires an Expressroute virtual network gateway to be created to exchange routes between a virtual network and an on-premises network. For more information about virtual network gateways and ExpressRoute, including performance information, and gateway SKUs, see [ExpressRoute virtual network gateways](expressroute-about-virtual-network-gateways.md).
27
-
28
-
To configure FastPath, the Expressroute virtual network gateway must be either of these two SKUs:
29
-
30
-
* Ultra Performance
31
-
* ErGw3AZ
32
-
33
-
### Virtual network peering
34
-
35
-
For the FastPath feature to function correctly, the hub virtual network and any peered spoke virtual networks must reside within the same region. It's important to note that FastPath doesn't support globally peered virtual networks.
36
-
37
-
## Limitations
38
-
39
-
While FastPath supports many configurations, it doesn't support the following features:
40
-
41
-
* Load Balancers: If you deploy an Azure internal load balancer in your spoke virtual network or the Azure PaaS service you deploy in your spoke virtual network, the network traffic from your on-premises network to the virtual IPs hosted on the load balancer is sent through the virtual network gateway. Load balancers within the hub virtual network are supported with FastPath.
42
-
43
-
* Gateway Transit: If you deploy two peered hub virtual networks connected to one circuit, you need to make sure to set the *Allow Gateway Transit* on the virtual network peering to false, otherwise you experience connectivity issues.
44
-
45
-
* Use Remote Gateway: If you deploy a spoke virtual network peered to two hub vnets, you can only use one hub gateway as the remote gateway. If you use both as a remote gateway, you experience connectivity issues.
46
-
47
-
* Private Link: FastPath Connectivity to a private endpoint or Private Link service over an ExpressRoute Direct circuit is supported for limited scenarios. For more information, see [enable FastPath and Private Link for 100-Gbps ExpressRoute Direct](expressroute-howto-linkvnet-arm.md#fastpath-virtual-network-peering-user-defined-routes-udrs-and-private-link-support-for-expressroute-direct-connections). FastPath connectivity to a Private endpoint/Private Link service isn't supported for ExpressRoute partner provider circuits.
48
-
49
-
* DNS Private Resolver: Azure ExpressRoute FastPath is not supported to a DNS Private Resolver in a spoke virtual network and will go through the virtual network gateway. DNS Private Resolvers within a hub virtual network are supported by FastPath. [DNS Private Resolver](../dns/dns-private-resolver-overview.md).
50
-
51
-
* For Azure NetApp Files, customers should upgrade their volumes from Basic to Standard for FastPath to work. [Supported Network Topologies](../azure-netapp-files/azure-netapp-files-network-topologies.md#supported-network-topologies).
24
+
| Feature | Availability |
25
+
|--|--|
26
+
| FastPath to Hub Vnet on ExpressRoute circuits | Available on all ExpressRoute circuits |
27
+
| Virtual Network Peering over FastPath | Generally available in all regions within the public cloud. This feature is applicable only for connections associated with ExpressRoute Direct circuits |
28
+
| User-Defined Routing (UDR) over FastPath | Generally available in all regions within the public cloud. This feature is applicable only for connections associated with ExpressRoute Direct circuits |
29
+
| Private Endpoint/Private Link over FastPath | Limited general availability (GA) support. This feature is applicable only for connections associated with ExpressRoute Direct circuits, within limited regions, and for limited services behind a private endpoint |
52
30
53
31
### IP address limits
54
32
@@ -60,10 +38,34 @@ While FastPath supports many configurations, it doesn't support the following fe
60
38
61
39
> [!NOTE]
62
40
> * ExpressRoute Direct has a cumulative limit at the port level.
63
-
> *Traffic flows through the ExpressRoute gateway when these IP limits are reached.
41
+
> *When the limits are reached, the new FastPath routes are not programmed and the traffic flows through the ExpressRoute gateway.
64
42
> * You can configure alerts through Azure Monitor to notify when the [number of FastPath routes](expressroute-monitoring-metrics-alerts.md#fastpath-routes-count-at-circuit-level) are nearing the threshold limit.
43
+
> * All other limits for the ExpressRoute Gateway, Circuits and VNET apply outside of the FastPath IP address limits.
65
44
66
-
## Limited General Availability (GA)
45
+
### Gateways
46
+
47
+
FastPath still requires an Expressroute virtual network gateway to be created to exchange routes between a virtual network and an on-premises network.
48
+
49
+
To configure FastPath, the Expressroute virtual network gateway must be one of these SKUs:
50
+
51
+
* Ultra Performance
52
+
* ErGw3AZ
53
+
* ErGwScale - with minimum of 10 scale units (Preview)
54
+
55
+
For more information about virtual network gateways and ExpressRoute, including performance information, and gateway SKUs, see [ExpressRoute virtual network gateways](expressroute-about-virtual-network-gateways.md).
56
+
57
+
### Virtual network peering over FastPath
58
+
59
+
For the FastPath feature to function correctly, the hub virtual network and any peered spoke virtual networks must reside within the same region. It's important to note that FastPath doesn't support globally peered virtual networks.
60
+
61
+
| Feature | Requirement |
62
+
|--|--|
63
+
| Hub Virtual Network | Must reside within the same region as any peered spoke virtual networks|
64
+
| Peered Spoke Virtual Networks | Must reside within the same region as the hub virtual network|
65
+
| Global Peering | Not supported by FastPath |
66
+
67
+
68
+
### Private Endpoint/Private Link over FastPath - Limited General Availability (GA)
67
69
68
70
FastPath support for Private Endpoint/Private Link connectivity is available for limited scenarios for 100/10Gbps ExpressRoute Direct connections. Private Endpoint/ Private Link connectivity is available in the following Azure regions:
69
71
- Australia East
@@ -88,15 +90,34 @@ FastPath Private endpoint/Private Link connectivity is supported for the followi
88
90
- Third Party Private Link Services
89
91
90
92
> [!NOTE]
93
+
> * Connections associated to ExpressRoute partner circuits aren't eligible for this preview.
91
94
> * Plan your deployments in advance, enabling FastPath Private Link and Private endpoint support for limited GA scenarios can take upwards of 4-6 weeks to complete.
92
-
> * Connections associated to ExpressRoute partner circuits aren't eligible for this preview. Both IPv4 and IPv6 connectivity are supported.
93
95
> * FastPath connectivity to Azure Private Link service and Private endpoint deployed to a spoke Virtual Network, peered to the Hub Virtual Network (where the ExpressRoute Virtual Network Gateway is deployed), is supported.
94
-
> * Azure Private Link pricing won't apply to traffic sent over ExpressRoute FastPath. For more information about pricing, check out the [Private Link pricing page](https://azure.microsoft.com/pricing/details/private-link/).
95
96
> * FastPath supports a max of 100Gbps connectivity to a single Availability Zone.
96
-
> * FastPath isn't supported with [Azure vWAN ExpressRoute Gateway](../virtual-wan/virtual-wan-expressroute-about.md).
97
+
> * Azure Private Link pricing won't apply to traffic sent over ExpressRoute FastPath. For more information about pricing, check out the [Private Link pricing page](https://azure.microsoft.com/pricing/details/private-link/).
98
+
97
99
98
100
> [!IMPORTANT]
99
-
> For more information about supported scenarios and to enroll in the limited GA offering, complete this [Microsoft Form](https://aka.ms/FPlimitedga). Once you've been contacted, you can run the commands in step 2 to [enable Private Link over FastPath](expressroute-howto-linkvnet-arm.md#fastpath-virtual-network-peering-user-defined-routes-udrs-and-private-link-support-for-expressroute-direct-connections).
101
+
> For more information about supported scenarios and to enroll in the limited GA offering, complete this [Microsoft Form](https://aka.ms/FPlimitedga).
102
+
> Once you've been contacted, you can run the commands in step 2 to [enable Private Link over FastPath](expressroute-howto-linkvnet-arm.md#fastpath-virtual-network-peering-user-defined-routes-udrs-and-private-link-support-for-expressroute-direct-connections).
103
+
104
+
## Limitations
105
+
106
+
While FastPath supports many configurations, it doesn't support the following features:
107
+
108
+
* Load Balancers: If you deploy an Azure internal load balancer in your spoke virtual network or the Azure PaaS service you deploy in your spoke virtual network, the network traffic from your on-premises network to the virtual IPs hosted on the load balancer is sent through the virtual network gateway. Load balancers within the hub virtual network are supported with FastPath.
109
+
110
+
* FastPath isn't supported with [Azure vWAN ExpressRoute Gateway](../virtual-wan/virtual-wan-expressroute-about.md).
111
+
112
+
* Gateway Transit: If you deploy two peered hub virtual networks connected to one circuit, you need to make sure to set the *Allow Gateway Transit* on the virtual network peering to false, otherwise you experience connectivity issues.
113
+
114
+
* Use Remote Gateway: If you deploy a spoke virtual network peered to two hub vnets, you can only use one hub gateway as the remote gateway. If you use both as a remote gateway, you experience connectivity issues.
115
+
116
+
* Private Link: FastPath Connectivity to a private endpoint or Private Link service over an ExpressRoute Direct circuit is supported for limited scenarios. For more information, see [enable FastPath and Private Link for 100-Gbps ExpressRoute Direct](expressroute-howto-linkvnet-arm.md#fastpath-virtual-network-peering-user-defined-routes-udrs-and-private-link-support-for-expressroute-direct-connections). FastPath connectivity to a Private endpoint/Private Link service isn't supported for ExpressRoute partner provider circuits.
117
+
118
+
* DNS Private Resolver: Azure ExpressRoute FastPath is not supported to a DNS Private Resolver in a spoke virtual network and will go through the virtual network gateway. DNS Private Resolvers within a hub virtual network are supported by FastPath. [DNS Private Resolver](../dns/dns-private-resolver-overview.md).
119
+
120
+
* For Azure NetApp Files, customers should upgrade their volumes from Basic to Standard for FastPath to work. [Supported Network Topologies](../azure-netapp-files/azure-netapp-files-network-topologies.md#supported-network-topologies).
0 commit comments