Virtual WAN Branches Route Table

LukeCloudWalker-6128 36 Reputation points
2022-06-03T07:36:48.327+00:00

Hi there,

Documentation says :
"All branch connections need to propagate their routes to the same set of route tables" link

Is it planned to allow custom routing for branches ?

For example, i have 2 VPN connections with 2 differents partners, and i dont wont them to learn each other routes ? Knowing that Azure Firewall is not usable for branch to branch connectivity, how can i achieve that ?

Another use case, would be route isolation for Production Express Route and Non Production Express Route to same DC for example.

Azure Virtual WAN
Azure Virtual WAN
An Azure virtual networking service that provides optimized and automated branch-to-branch connectivity.
186 questions
Azure VPN Gateway
Azure VPN Gateway
An Azure service that enables the connection of on-premises networks to Azure through site-to-site virtual private networks.
1,375 questions
Azure Virtual Network
Azure Virtual Network
An Azure networking service that is used to provision private networks and optionally to connect to on-premises datacenters.
2,135 questions
Azure ExpressRoute
Azure ExpressRoute
An Azure service that provides private connections between Azure datacenters and infrastructure, either on premises or in a colocation environment.
322 questions
0 comments
Accepted answer
  1. GitaraniSharma-MSFT 47,011 Reputation points Microsoft Employee
    2022-06-07T09:35:27.667+00:00

    Hello @LukeCloudWalker-6128 ,

    Apologies for the delay in response.

    I understand that you would like to know if custom routing for branches in vWAN is planned and how to prevent the branches from learning each other routes.

    As of today, we don’t have custom routing for branches where branch connections could be S2S VPN, NVA branches, P2S/remote user VPN, ER/Direct connect equivalent but we have custom routing for VNETs (available in vWAN).
    Custom routing for branches is in the roadmap and the Product team has started working on it but we won't have it until CY2023 sometime.

    In your case, multiple vWAN hubs is a good way to overcome this issue. If you are looking to do isolation, then you have to create more hubs and switch off branch to branch flag on the Virtual WAN setting (this disables branch to branch but keep the VNET to VNET path on for inter-hub).

    Also, If you want to filter what routes are advertised to Express Route, you can soon use one of our upcoming features called "route maps", which will give you control over what prefixes each connection learns. The estimated ETA for this feature release is July 2022 (subject to change).

    Kindly let us know if the above helps or you need further assistance on this issue.

    ----------------------------------------------------------------------------------------------------------------

    Please "Accept the answer" if the information helped you. This will help us and others in the community as well.

    0 comments

0 additional answers

Sort by: Most helpful
Most helpful Newest Oldest