The Azure Virtual WAN solution seems compelling for organizations that are moving to Azure who are also currently using MPLS and are looking at SD-WAN.
A shortcoming seems to be that global vNet peering is not yet supported.
It would be great if global vNet peering support for Azure Virtual WAN was in the roadmap.20 votes
Currently we are unable to efficiently verify what routes have been learnt when BGP has been established for Virtual WAN.
Could the team consider the creation of a PS Cmdlet or AZ CLI cmd to allow for engineers to check what routes have been learnt when BGP has been established for Virtual WAN.12 votes
VNET to VNET peering is not available when VNETs are connected to Azure WAN, Also no connectivity between two Azure WAN hubs. Having this option will help to manage both Azure network and branch network centrally12 votes
Right now Azure Virtual WAN uses a fixed predefined BGP AS Number "65515"
I would like to have the possibility to change that AS Number.12 votes
- Don't see your idea?