Hi @Gopinath Rethinam,
Welcome to Microsoft Q&A Platform. Thank you for reaching out & hope you are doing well.
You can use Virtual WAN to connect a VNet to a virtual hub in a different subscription/tenant but connecting a Hub in VWAN A to a Hub in VWAN B across the tenants via the normal VWAN hub to hub mechanism is not currently supported today.
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
- But for workaround, we can connect vHub in VWAN A to vHub in VWAN B using VPN gateway of the Virtual Hubs.
- Refer: https://zcusa.951200.xyz/en-us/azure/virtual-wan/connect-virtual-network-gateway-vwan
To answer your question,
- You can manage cross-tenant virtual network connections only through PowerShell or the Azure CLI installed on your local machine. Because Azure Portal does not support cross-tenant operations, you can't manage cross-tenant virtual network connections through Azure portal or Azure portal CloudShell (both PowerShell and CLI).
- You can use the PowerShell to connect a Virtual Hub of a vWAN from a virtual network which is sitting in a different tenant.
- The detailed explanation is clearly mentioned step by step in the below document. Please refer to it and let us know if you have any other queries.
- For your reference: https://zcusa.951200.xyz/en-us/azure/virtual-wan/cross-tenant-vnet#prerequisites
Kindly let us know if the above helps or you need further assistance on this issue.
If this answers your query, do click **Accept Answer**
and **Yes**
for was this answer helpful.
Regards,
Sai Prasanna.