Skip to content

Commit e7bce07

Browse files
authored
add direction for table with routes
1 parent b441bb3 commit e7bce07

File tree

1 file changed

+6
-7
lines changed

1 file changed

+6
-7
lines changed

includes/expressroute-limits.md

Lines changed: 6 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -25,13 +25,12 @@
2525

2626
| Resource | Local / Standard SKU | Premium SKU |
2727
|--|--|--|
28-
| Maximum number of IPv4 routes advertised to Azure private peering | 4,000 | 10,000 |
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 | 1,000 |
31-
| Maximum number of IPv6 routes advertised from Azure private peering from the VNet address space | 100 | 100 |
32-
| Maximum number of IPv4 routes advertised to Microsoft peering | 200 | 200 |
33-
| Maximum number of IPv6 routes advertised to Microsoft peering | 200 | 200 |
34-
28+
| Maximum number of IPv4 routes advertised to Azure private peering from on-premises | 4,000 | 10,000 |
29+
| Maximum number of IPv6 routes advertised to Azure private peering from on-premises | 100 | 100 |
30+
| Maximum number of IPv4 routes advertised from Azure private peering from the VNet address space to ExpressRoute virtual network gateway | 1,000 | 1,000 |
31+
| Maximum number of IPv6 routes advertised from Azure private peering from the VNet address space to ExpressRoute virtual network gateway | 100 | 100 |
32+
| Maximum number of IPv4 routes advertised to Microsoft peering from on-premises | 200 | 200 |
33+
| Maximum number of IPv6 routes advertised to Microsoft peering from on-premises | 200 | 200 |
3534

3635
#### Virtual networks links allowed for each ExpressRoute circuit limit
3736

0 commit comments

Comments
 (0)