Allow separate VLAN tags when peering to ExpressRoute circuits
Currently ExpressRoute requires two client subnets, but restricts these to the same VLAN tag. It would be helpful if each of these VLANs could be tagged individually.
e.g. currently I can specify "172.16.1.0/30" as the primary and "172.16.2.0/30" as the secondary but they have to have the same ID
Charles A commented
Has there any progress on this? For our company this requirement adds extra cost and complexity when building out ExpressRoute.
Jake V. commented
I ran across the same issue and the documentation threw me off when it spoke about using 2 VLAN ID's. I could only use one for the peering portion of the ExpressRoute circuit configuration.