ExpressRoute Gateway and FastPath
What You'll Learn
You'll learn how to implement virtual network gateways for ExpressRoute and enable FastPath to optimize data plane performance.
Understanding ExpressRoute Gateways
An ExpressRoute Gateway acts as the entry point for your Azure virtual network when connecting via ExpressRoute. Think of it as a specialized router that sits at the edge of your VNet, managing traffic flow between your on-premises network and Azure resources.
When you connect an ExpressRoute circuit to a virtual network, you must provision a gateway with one of several SKU tiers (Standard, HighPerformance, UltraPerformance, or ErGw variants). Each tier offers different throughput limits—choosing the right one depends on your bandwidth requirements.
What is FastPath?
Here's where optimization becomes crucial: by default, all traffic flows through the gateway, which can create a bottleneck. FastPath is a feature that bypasses the ExpressRoute gateway for the data plane while keeping the control plane intact.
Picture FastPath like an express lane on a highway. Instead of every data packet stopping at a toll booth (the gateway), FastPath creates a direct path from your on-premises network straight to Azure VMs, dramatically reducing latency and improving throughput.
When to Use FastPath
FastPath is available on UltraPerformance and ErGw SKUs. It's ideal for:
- High-throughput workloads (databases, data transfers)
- Latency-sensitive applications
- Large-scale VM deployments
Note that FastPath doesn't bypass the gateway entirely—control plane operations like routing updates still flow through it, ensuring network policies remain enforced.
Key Takeaway: ExpressRoute Gateway connects your VNet to ExpressRoute circuits, while FastPath optimizes performance by enabling direct data paths to Azure VMs, reducing latency for bandwidth-intensive workloads.