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 the best practices for Azure Hub and Spoke network topology with multiple Azure Subscription(s).
Please note that Azure Subscription is a logical boundary for billing. It does not affect Peering between two VNETs (Hub and Spoke) in two different subscriptions.
With Regular VNET Hub and Spoke:
You can refer to the documentation on Hub-spoke network topology in Azure for more details on Hub VNet and Spoke VNet(s) topology.
- Please make sure the VNET Gateway and the Hub VNET are in the same subscription/resource group.
- Make sure Gateway Transit is enabled between the peering(s) from Spoke VNet(s) to Hub VNet.
With Azure vWAN,
This only masks the Hub from you.
It still let's you manage :
- Virtual Networks (Spokes only) to be connect to the Hub
- Azure Firewall which is directly deployed into the Hub
- ExpressRoute/VPN Gateway that is deployed into the Hub
- Define the address range of the Hub even
Almost all of the use cases of traditional Hub Spoke VNET architecture can be achieved by using a vWAN as well.
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.