Azure VWAN Inter-region traffic filtering when using Secured Virtual HUBs

Veerraju Gopalli 20 Reputation points
2023-03-22T13:27:40.8033333+00:00

Hi Microsoft team,

we have configured Azure VWAN with Secure virtual hubs( With Azure firewall), but as per the Microsoft documentation, we see inter-region traffic filtering is not possible on the firewall.

We have tested the below in our lab:

We have two on prem datacenters ( Seatle and washington DC), these data centers are connected to Azure regions in West US2 and East US2 using express route circuits.

We have also configured express route cross connect. Now using the express route cross connect we see that we can send the inter-region traffic over express route path and achieve inter-region traffic filtering.

When we are sending inter-region traffic over the express route path we see only 10ms of latency added( with two firewalls, ERGW and one MSEE device in the path) compared to inter-region link(only two hops in the path: hub virtual routers).

I couldn't find documentation on the Microsoft side which shows the use of express-route cross connect to overcome the inter-region traffic limitation. I would like to check whether it is recommended to use the express-route cross connect for inter-region traffic when latency is not making big difference.

Please advise.

Azure Virtual WAN
Azure Virtual WAN
An Azure virtual networking service that provides optimized and automated branch-to-branch connectivity.
189 questions
{count} votes

1 answer

Sort by: Most helpful
  1. KapilAnanth-MSFT 35,246 Reputation points Microsoft Employee
    2023-03-28T09:27:59.51+00:00

    @Veerraju Gopalli

    Welcome to the Microsoft Q&A Platform. Thank you for reaching out & I hope you are doing well.

    I understand that you would like to know about the use of Express-Route Cross Connect to overcome the Inter-region Firewall Filtering traffic limitation

    I discussed this with the Azure Virtual WAN Product Group team and below is their update:

    Yes, but this only applies for VNET to VNET traffic and is not an architecture we recommend to customers.

    For more details, you can reach out to previewinterhub@microsoft.com

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

    Thanks,

    Kapil


    Please don’t forget to close the thread by clicking "Accept the answer" wherever the information provided helps you, as this can be beneficial to other community members.

    0 comments No comments