Cross Tenant Network integration over Azure VWAN in same Azure region

Question

I have Two azure tenants in same azure region. In both the tenants I have a dedicated Azure VWAN with one hub in it. I am trying to connect this two hubs across tenant so resources under both hub's spoke can talk to each other. We found that Azure Virtual WAN doesn’t support direct cross tenant integration, in that case we are looking for a right solution to achieve this integration. Below are the options we are thinking, kindly give a detailed guidance to enable one of these solutions.

 

Option A(Preferred) : VM-A have to connect with VM-B over direct VWAN integration across tenant.

 

Option B: VM-A have to connect with VM-B over direct VWAN integration across tenant through VPN.

Option C: VM-A have to connect with VM-B using Cross tenant VWAN-to-Vnet integration, where we need clarity on routing requirements.

Answer 1

Hi @Gopinath Rethinam,

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

I'm glad that you were able to resolve your issue and thank you for posting your solution so that others experiencing the same thing can easily reference this! Since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others ", I'll repost your solution in case you'd like to "Accept " the answer.

Issue: Cross Tenant Network integration over Azure VWAN in same Azure region

Solution: Below is the solution created by @erjosito , which is working perfectly fine. As of now I have implemented Option B based on below link and I hope soon MS implement Option A as it is a better solution.

https://github.com/erjosito/azcli/blob/master/vwan2vwan.azcli

For Option A,

If you wish, you may also leave your feedback in the below forum requesting this feature. All the feedback you share in these forums will be monitored and reviewed by the Microsoft engineering teams responsible for building Azure. https://feedback.azure.com/d365community/forum/8ae9bf04-8326-ec11-b6e6-000d3a4f0789

If you have any other questions or are still running into more issues, please let us know. Thank you again for your time and patience throughout this issue.

Please remember to "Accept Answer" to close this thread, so that others in the community facing similar issues can easily find the solution.

Thanks,

Sai Prasanna.

Answer 2

hi @Gopinath Rethinam , I understand that you have a requirement to connect 2 VWANs from different tenant.

Option A is not supported.

Option B can work.

Option C is not supported. One vnet can only peer to one Virtual Hub. If your vnet in Tenant B connects to Virtual Hub (Tenant A), it can't connect to Virtual Hub (Tenant B).

I'd suggest investigate further of your current landscape:

• Which vnet in Tenant B need to communicate to which vnet in Tenant A?
• Is it better to do VPN for cross-tenant VWAN communication, or migrate specific vnets from Tenant B to Tenant A (or vice versa)?
• Can Azure Private Link (Extend to your own services) help?

Please accept an answer if correct. Original posters help the community find answers faster by identifying the correct answer. Here is how.