An Azure service that provides private connections between Azure datacenters and infrastructure, either on premises or in a colocation environment.
Hello @Boshardy, Tom ,
Thank you for your question.
Based on the scenario you described, simply connecting both ExpressRoute circuits to the same Virtual WAN hub does not automatically enable route transit between them. Virtual WAN provides connectivity between supported connection types, but it does not advertise routes directly from one ExpressRoute circuit to another by default.
For Azure VMware Solution (AVS), the supported approach is to use ExpressRoute Global Reach, which enables BGP route exchange between ExpressRoute circuits over the Microsoft backbone. Once Global Reach is configured between the AVS ExpressRoute circuit and the ExpressRoute circuit connected to your on-premises environment, routes learned from the AVS private cloud can be advertised to your on-premises network.
If your ExpressRoute circuits are located in different Azure subscriptions, you'll also need to generate an authorization key from the circuit owner and use the corresponding circuit resource ID when establishing the Global Reach connection.
After the Global Reach connection has been created, verify that its status is Connected and confirm that the expected BGP prefixes are being advertised and received on both ExpressRoute peerings.
You can find the configuration steps and prerequisites in the Microsoft documentation:
- ExpressRoute Global Reach: https://learn.microsoft.com/azure/expressroute/expressroute-global-reach
- Azure VMware Solution networking: https://learn.microsoft.com/azure/azure-vmware/networking-concepts
- Azure Virtual WAN documentation: https://learn.microsoft.com/azure/virtual-wan/
I hope this helps.