Hey guys! This may have been answered a couple of times.. I´ve read a bunch of other topics related to peering vMX to Azure Route Server, but at this point - I´m kind of confused. So, we are trying to achieve a PoC with two vMX´s peered to a Azure Route Server. So far, I´ve been able to peer them, but only one at a time. To my understanding, vMX only support one peer at a time? I did a test by disabling BGP on the first vMX, and the other one were able to peer to the ASR just fine. Pretty neat, but it´s not possible to peer both of them at the same time? It would be nice to have same routes advertised in both vMX. So that the traffic load would be balanced and a branch site could choose the vMX that has the closest azure resources. Which would save some unnecessary Azure traffic. Not sure if Meraki support that kind path-selection? Like, the vMX can announce to every branch site that it has the closest path. Made a quick diagram of the intended design. I´ll add some bulletpoints to clarify what we would like to achieve: vMX in each geographical location (Europe and Asia for instance) Each branch site will route to the vMX that has the closest path to the intended resource in Azure. Hence dynamic routing. This is to save unnecessary Azure traffic - So that London branch site won´t have to send traffic first to Europe region and then across to Asia in order to reach the resources. It can just send it directly to vMX-02 (Green) The vMXs will both act as a backup for each geographical location.       Cheers! ... View more