Diverse Azure ER VCs from different Metros
T
Tom Leisner
It would be great to have the option to create redundant Virtual Connections from different Metros. Currently, the only way to do this would be to create mutliple ER circuits on Azure side, which would be connected with a single connection each (or have double-redundancy end to end with double the costs on both sides)
Steffen Gelessus
To explain the issue in more detail:
We have one colocation in DC with a primary Fabric port and another colocation in NY with a secondary Fabric port.
When ordering a new ExpressRoute circuit, the S-Key provided by Microsoft is only valid for a single order, so we have to order both ExpressRoute circuits within a single order. Equinix Portal does not allow to include Fabric Ports from two different metro areas into the same ExpressRoute circuit order. When ordering a single connection from one metro area, the S-Key cannot be used anymore for the second single connection.