Skip to content

Commit 6113126

Browse files
authored
Merge pull request #186474 from tanuballa/patch-187
v4 and v6 limit udpate
2 parents 5fc808d + c6687fe commit 6113126

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

includes/expressroute-limits.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -19,8 +19,10 @@
1919
| Maximum number of IPv6 routes advertised to Azure private peering with ExpressRoute Premium add-on |100 |
2020
| Maximum number of IPv4 routes advertised from Azure private peering from the VNet address space for an ExpressRoute connection | 1,000 |
2121
| Maximum number of IPv6 routes advertised from Azure private peering from the VNet address space for an ExpressRoute connection | 1,000 |
22-
| Maximum number of routes advertised to Microsoft peering with ExpressRoute Standard |200 |
23-
| Maximum number of routes advertised to Microsoft peering with ExpressRoute Premium add-on |200 |
22+
| Maximum number of IPv4 routes advertised to Microsoft peering with ExpressRoute Standard |200 |
23+
| Maximum number of IPv4 routes advertised to Microsoft peering with ExpressRoute Premium add-on |200 |
24+
| Maximum number of IPv6 routes advertised to Microsoft peering with ExpressRoute Standard |200 |
25+
| Maximum number of IPv6 routes advertised to Microsoft peering with ExpressRoute Premium add-on |200 |
2426
| Maximum number of ExpressRoute circuits linked to the same virtual network in the same peering location |4 |
2527
| Maximum number of ExpressRoute circuits linked to the same virtual network in different peering locations |16 (For more information, see [Gateway SKU](../articles/expressroute/expressroute-about-virtual-network-gateways.md#aggthroughput).) |
2628
| Number of virtual network links allowed per ExpressRoute circuit |See the [Number of virtual networks per ExpressRoute circuit](#vnetpercircuit) table. |

0 commit comments

Comments
 (0)