|
17 | 17 | | Maximum number of circuits in the same peering location linked to the same virtual network | 4 | |
18 | 18 | | Maximum number of circuits in different peering locations linked to the same virtual network |Standard / ERGw1Az - 4 </br> High Perf / ERGw2Az - 8 </br> Ultra Performance / ErGw3Az - 16 | |
19 | 19 | | Maximum number of IPs for ExpressRoute provider circuit with Fastpath | 25,000 | |
20 | | -| Maximum number of IPs for ExpressRoute Direct 10-Gbps with Fastpath | 100,000 | |
21 | | -| Maximum number of IPs for ExpressRoute Direct 100-Gbps with Fastpath | 200,000 | |
| 20 | +| Maximum number of IPs for ExpressRoute Direct 10 Gbps with Fastpath | 100,000 | |
| 21 | +| Maximum number of IPs for ExpressRoute Direct 100 Gbps with Fastpath | 200,000 | |
22 | 22 | | Maximum number of flows for ExpressRoute Traffic Collector | 30,000 | |
23 | 23 |
|
24 | 24 | #### Route advertisement limits |
25 | 25 |
|
26 | 26 | | Resource | Local / Standard SKU | Premium SKU | |
27 | | -| -- | -- | -- | |
28 | | -| Maximum number of IPv4 routes advertised to Azure private peering | 4000 | 10000 | |
| 27 | +|--|--|--| |
| 28 | +| Maximum number of IPv4 routes advertised to Azure private peering | 4,000 | 10,000 | |
29 | 29 | | Maximum number of IPv6 routes advertised to Azure private peering | 100 | 100 | |
30 | | -| Maximum number of IPv4 routes advertised from Azure private peering from the VNet address space | 1,000 | 1000 | |
31 | | -| Maximum number of IPv6 routes advertised from Azure private peering from the VNet address space | 1,000 | 1000 | |
| 30 | +| Maximum number of IPv4 routes advertised from Azure private peering from the VNet address space | 1,000 | 1,000 | |
| 31 | +| Maximum number of IPv6 routes advertised from Azure private peering from the VNet address space | 1,000 | 1,000 | |
32 | 32 | | Maximum number of IPv4 routes advertised to Microsoft peering | 200 | 200 | |
33 | 33 | | Maximum number of IPv6 routes advertised to Microsoft peering | 200 | 200 | |
34 | 34 |
|
35 | 35 |
|
36 | | -#### Virtual networks links allowed for each ExpressRoute circuit limits |
| 36 | +#### Virtual networks links allowed for each ExpressRoute circuit limit |
37 | 37 |
|
38 | 38 | | Circuit size | Local / Standard SKU | Premium SKU | |
39 | | -| --- | --- | -- | |
| 39 | +| --- | --- |--| |
40 | 40 | | 50 Mbps | 10 | 20 | |
41 | 41 | | 100 Mbps | 10 | 25 | |
42 | 42 | | 200 Mbps | 10 | 25 | |
|
48 | 48 | | 40 Gbps* | 10 | 100 | |
49 | 49 | | 100 Gbps* | 10| 100 | |
50 | 50 |
|
51 | | -**100 Gbps ExpressRoute Direct Only* |
| 51 | +**100-Gbps ExpressRoute Direct Only* |
52 | 52 |
|
53 | 53 | > [!NOTE] |
54 | 54 | > Global Reach connections count against the limit of virtual network connections per ExpressRoute Circuit. For example, a 10 Gbps Premium Circuit would allow for 5 Global Reach connections and 95 connections to the ExpressRoute Gateways or 95 Global Reach connections and 5 connections to the ExpressRoute Gateways or any other combination up to the limit of 100 connections for the circuit. |
|
0 commit comments