Azure VMware Solution
An Azure service that runs native VMware workloads on Azure.
379 questions
Azure VMware Solution - Need for ARS in Transit VNet
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(12.8, 48%, 11%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ENR%3C/text%3E%3C/svg%3E)
Nithin Radhakrishnan
0
Reputation points
We are deploying Azure VMware Solution in region with ER Global Reach is not supported. Also, we've limitations in using Azure Virtual WAN to the existing landing zone. Due to these factors, we've decided to proceed with Transit VNet approach. https://learn.microsoft.com/en-us/azure/cloud-adoption-framework/scenarios/azure-vmware/example-architectures#scenario-2-an-nva-in-virtual-network-inspects-all-network-traffic
I've few confusions wrt the architecture, for eg: how the routes are propagated and why a separate ARS is needed in the Transit VNet since ARS in hub will propagate the on-premises routes to the transit VNet which in-turn will automatically propagate to the ExpressRoute gateway in the transit VNet and finally reaches AVS.
Can someone please help me with this ?
Sign in to answer