Skip to content

Commit 673cbd2

Browse files
duongauduongau
committed
content dev review
1 parent 521e2f1 commit 673cbd2

File tree

2 files changed

+66
-52
lines changed

2 files changed

+66
-52
lines changed

‎articles/expressroute/about-fastpath.md

Lines changed: 66 additions & 52 deletions
Original file line numberDiff line numberDiff line change
@@ -9,65 +9,80 @@ ms.date: 03/20/2025
99
ms.author: rmareddy
1010
ms.custom: template-concept, references_regions, engagement-fy23
1111
---
12+
1213
# About ExpressRoute FastPath
1314

14-
ExpressRoute virtual network gateway is designed to exchange network routes and route network traffic. FastPath is designed to improve the data path performance between your on-premises network and your virtual network. When enabled, FastPath sends network traffic directly to virtual machines in the virtual network, bypassing the Expressroute virtual network gateway.
15+
ExpressRoute virtual network gateway facilitates the exchange of network routes and directs network traffic. ExpressRoute FastPath enhances data path performance between your on-premises network and your virtual networks. When enabled, ExpressRoute FastPath routes network traffic directly to virtual machines, bypassing the ExpressRoute virtual network gateway.
16+
17+
:::image type="content" source=".\media\about-fastpath\fastpath-vnet-peering.png" alt-text="Diagram of an ExpressRoute connection with ExpressRoute FastPath and virtual network peering.":::
1518

16-
:::image type="content" source=".\media\about-fastpath\fastpath-vnet-peering.png" alt-text="Diagram of an ExpressRoute connection with Fastpath and virtual network peering.":::
19+
## Availability and features
1720

18-
## Requirements
21+
ExpressRoute FastPath is available for ExpressRoute Direct and ExpressRoute provider circuits. ExpressRoute FastPath is generally available in all public cloud regions, with limited general availability for Private Link and Private endpoint connectivity.
1922

2023
### Circuits
2124

22-
FastPath is available on ExpressRoute circuits.
25+
The following table lists the availability of ExpressRoute FastPath for the different type of ExpressRoute circuit:
2326

2427
| Feature | Availability |
2528
|--|--|
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 |
29+
| ExpressRoute FastPath to Hub virtual network on ExpressRoute circuits | Available on all ExpressRoute circuits |
30+
| Virtual network peering over ExpressRoute FastPath | Generally available in all public cloud regions and only for ExpressRoute Direct. |
31+
| User-Defined Routing (UDR) over ExpressRoute FastPath | Generally available in all public cloud regions and only for ExpressRoute Direct. |
32+
| Private endpoint and Private Link over ExpressRoute FastPath | Limited general availability and only for ExpressRoute Direct. |
33+
34+
#### IP address limits
35+
36+
ExpressRoute FastPath has IP address limits that are based on the type of ExpressRoute circuit.
3037

31-
### IP address limits
38+
> [!IMPORTANT]
39+
> - Azure ExpressRoute Direct has a cumulative limit at the port level.
40+
> - When the limit is reached, new ExpressRoute FastPath routes don't get configured, and instead traffic flows through the ExpressRoute gateway.
41+
> - All other limits for the ExpressRoute gateway, the ExpressRoute circuit, and the virtual network still apply.
42+
43+
The following table lists bandwidth and ExpressRoute FastPath IP limits for ExpressRoute circuits:
3244

33-
| ExpressRoute SKU | Bandwidth | FastPath IP limit |
45+
| ExpressRoute port type | Bandwidth | ExpressRoute FastPath IP limit |
3446
|--|--|--|
35-
| ExpressRoute Direct Port | 100 Gbps | 200,000 |
36-
| ExpressRoute Direct Port | 10 Gbps | 100,000 |
37-
| ExpressRoute provider circuit | 10 Gbps and lower | 25,000 |
47+
| ExpressRoute Direct | 100 Gbps | 200,000 |
48+
| ExpressRoute Direct | 10 Gbps | 100,000 |
49+
| ExpressRoute provider | 10 Gbps and lower | 25,000 |
3850

39-
> [!NOTE]
40-
> * ExpressRoute Direct has a cumulative limit at the port level.
41-
> * When the limits are reached, the new FastPath routes are not programmed and the traffic flows through the ExpressRoute gateway.
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.
51+
> [!TIP]
52+
> You can configure alerts using Azure Monitor to notify you when the number of ExpressRoute FastPath routes approaches the threshold limit.
4453
4554
### Gateways
4655

47-
FastPath still requires an Expressroute virtual network gateway to be created to exchange routes between a virtual network and an on-premises network.
56+
To use ExpressRoute FastPath, you need to create an ExpressRoute virtual network gateway to facilitate route exchange between your virtual network and on-premises network.
4857

49-
To configure FastPath, the Expressroute virtual network gateway must be one of these SKUs:
58+
The ExpressRoute virtual network gateway must be one of the following SKUs to configure ExpressRoute FastPath:
5059

5160
* Ultra Performance
5261
* ErGw3AZ
53-
* ErGwScale - with minimum of 10 scale units (Preview)
62+
* ErGwScale - with a minimum of 10 scale units (Preview)
5463

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).
64+
For more information on virtual network gateways, including performance metrics, and available gateway SKUs, see [ExpressRoute virtual network gateways](expressroute-about-virtual-network-gateways.md).
5665

57-
### Virtual network peering over FastPath
66+
### Virtual network peering over ExpressRoute FastPath (ExpressRoute Direct only)
5867

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.
68+
The following table lists the requirements for virtual network peering over ExpressRoute FastPath:
6069

61-
| Feature | Requirement |
70+
| Requirement | Description |
6271
|--|--|
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 |
72+
| Hub virtual network | Must be in the same region as any peered spoke virtual networks. |
73+
| Peered spoke virtual networks | Must be in the same region as the hub virtual network. |
74+
| Global virtual network peering | Not supported by ExpressRoute FastPath. |
75+
76+
### Azure Private Link and Private endpoint over ExpressRoute FastPath (ExpressRoute Direct only)
6677

78+
> [!IMPORTANT]
79+
> - This feature is in limited GA (General Availability).
80+
> - This feature requires you to enroll in the limited GA offering by completing this [Microsoft Form](https://aka.ms/FPlimitedga). Once contacted, you can run the commands in step 2 to [enable Private Link over ExpressRoute FastPath](expressroute-howto-linkvnet-arm.md#fastpath-virtual-network-peering-user-defined-routes-udrs-and-private-link-support-for-expressroute-direct-connections).
81+
82+
ExpressRoute FastPath support for Private Link and Private endpoint connectivity is available for specific scenarios with 100 Gbps and 10-Gbps ExpressRoute Direct connections.
6783

68-
### Private Endpoint/Private Link over FastPath - Limited General Availability (GA)
84+
The supported Azure regions are:
6985

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:
7186
- Australia East
7287
- East Asia
7388
- East US
@@ -83,42 +98,41 @@ FastPath support for Private Endpoint/Private Link connectivity is available for
8398
- West US 2
8499
- West US 3
85100

86-
FastPath Private endpoint/Private Link connectivity is supported for the following Azure Services:
101+
The following Azure services are supported:
102+
87103
- Azure Cosmos DB
88104
- Azure Key Vault
89105
- Azure Storage
90-
- Third Party Private Link Services
106+
- Third-party Private Link services
91107

92108
> [!NOTE]
93-
> * Connections associated to ExpressRoute partner circuits aren't eligible for this preview.
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.
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.
96-
> * FastPath supports a max of 100Gbps connectivity to a single Availability Zone.
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-
99-
100-
> [!IMPORTANT]
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).
109+
> * Connections associated with ExpressRoute partner circuits aren't eligible for this preview.
110+
> * Plan your deployments in advance; enabling ExpressRoute FastPath Private Link and Private endpoint support for limited GA scenarios can take 4-6 weeks to complete.
111+
> * ExpressRoute FastPath connectivity to Azure Private Link service and Private endpoint deployed in a spoke Virtual Network, peered to the Hub Virtual Network (where the ExpressRoute Virtual Network Gateway is deployed), is supported.
112+
> * ExpressRoute FastPath supports a maximum of 100-Gbps connectivity to a single availability zone.
113+
> * Azure Private Link pricing doesn't apply to traffic sent over ExpressRoute FastPath. For more information about pricing, see the [Private Link pricing page](https://azure.microsoft.com/pricing/details/private-link/).
103114
104115
## Limitations
105116

106-
While FastPath supports many configurations, it doesn't support the following features:
117+
While ExpressRoute FastPath supports many configurations, it might not be suitable for all scenarios. The following limitations apply to ExpressRoute FastPath:
107118

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.
119+
- **Azure Internal Load Balancer**: ExpressRoute FastPath doesn't support Azure internal load balancers or Azure PaaS services in spoke virtual networks. Network traffic from your on-premises network to the private IP addresses of these services in the spoke virtual network gets routed through the ExpressRoute virtual network gateway. Internal load balancers within the hub virtual network aren't affected.
109120

110-
* FastPath isn't supported with [Azure vWAN ExpressRoute Gateway](../virtual-wan/virtual-wan-expressroute-about.md).
121+
- **Azure Virtual WAN ExpressRoute Gateway**: ExpressRoute FastPath isn't supported with [Azure Virtual WAN ExpressRoute Gateway](../virtual-wan/virtual-wan-expressroute-about.md).
111122

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.
123+
- **Virtual network peering**:
124+
125+
- **Gateway transit**: If you have two hub virtual networks that are peered and connected to a single circuit, set the *Allow Gateway Transit* option in the virtual network peering configuration to false to avoid connectivity issues.
113126

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.
127+
- **Use remote gateway**: If a spoke virtual network is peered to two different hub virtual networks, only one hub gateway can be used as the remote gateway. Using both as remote gateways causes connectivity issues.
115128

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.
129+
* **Azure DNS Private Resolver**: ExpressRoute FastPath supports DNS Private Resolvers in the hub virtual network. However, it doesn't support DNS Private Resolvers in spoke virtual networks, so traffic flows through the virtual network gateway instead. For more information, see [DNS Private Resolver](../dns/dns-private-resolver-overview.md).
117130

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).
131+
* **Azure NetApp Files**: To use ExpressRoute FastPath, upgrade your Azure NetApp Files volumes from Basic to Standard. For more information, see [Supported Network Topologies](../azure-netapp-files/azure-netapp-files-network-topologies.md#supported-network-topologies).
121132

122133
## Next steps
123134

124-
- To enable FastPath, see configure ExpressRoute FastPath using the [Azure portal](expressroute-howto-linkvnet-portal-resource-manager.md#configure-expressroute-fastpath) or using [Azure PowerShell](expressroute-howto-linkvnet-arm.md#configure-expressroute-fastpath).
135+
To enable ExpressRoute FastPath, follow these guides:
136+
137+
- [Configure ExpressRoute FastPath using the Azure portal](expressroute-howto-linkvnet-portal-resource-manager.md#configure-expressroute-fastpath)
138+
- [Configure ExpressRoute FastPath using Azure PowerShell](expressroute-howto-linkvnet-arm.md#configure-expressroute-fastpath)

‎bullet-list.md

Whitespace-only changes.

0 commit comments

Comments
 (0)