![](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(96, 20%, 19%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ENW%3C/text%3E%3C/svg%3E)
Azure Virtual Network
An Azure networking service that is used to provision private networks and optionally to connect to on-premises datacenters.
2,775 questions
![](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(134.4, 59%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ECM%3C/text%3E%3C/svg%3E)
Thank you for reaching out.
I understand your facing connectivity issue from your on-prem to Azure via Express Route.
Based on your statement above.
Could you please help how DMZ network can reach to Azure VM. can we add this route in express route peering.? or is there any way were we can auto propagate routes ?
Yes you need to add this route to your peering so that eBGP can advertise the route in Azure. In Azure express route routing exchange is over eBGP protocol. EBGP sessions are established between the MSEEs and your routers. For connectivity between on-prem DMZ network to Azure you must advertise the routes from your on-premises Edge router to Azure via BGP.
Currently there is no way to auto-propagate this route.
You can follow the guide here, just in case you face any connectivity issue even after advertising the DMZ route.
Hope this helps! Please let me know if you have any additional questions. Thanks!