Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
After you deploy Azure VMware Solution Generation 2 (Gen 2) private cloud, you need network connectivity between the private cloud and other networks you have in an Azure Virtual Network. In this article, you learn how to connect the Gen 2 private cloud to Azure Virtual Networks.
Prerequisites
- Gen 2 private cloud deployed successfully.
- Multiple Virtual Networks to establish connectivity to your Gen 2 private cloud Azure Virtual Network.
Azure VMware Solution Hosted (Local) Virtual Network
This Azure VMware Solution private cloud deployment is hosted in an Azure Virtual Network. This means the connectivity to the local Virtual Network from an Azure VMware Solution private cloud is established during deployment, with no other configuration required. This private cloud follows the same network connectivity constructs as other Azure services. This means VMware NSX workload segments created in this private cloud will be systematically programmed as Virtual Network address spaces in the Virtual Network domain for routing purposes.
Azure VMware Solution creates the following read-only management subnets within the hosted Virtual Network to host required private cloud components. These Management Subnets are allocated from the management address block specified for private cloud creation. The following are sample subnets derived from an SDDC with a 10.74.64.0/22 address block.
Other Virtual Networks
Azure VMware Solution's connectivity to nonlocal Virtual Networks follows the same procedure as Azure Virtual Network users use to connect their workloads between Virtual Networks. The Virtual Network can be connected to other nonlocal Virtual Networks using Azure Virtual Network peering as described in the following Azure documentation.
Both regional Virtual Network peering and global Virtual Network peering is supported for Azure VMware Solution.
Note
The standard Azure peer Virtual Network peering resync needs to be done to propagate any NSX segment, subnet and route changes on Azure VMware Solution private cloud.
Related topics
- Connect to on-premises environment
- Internet connectivity options
- Connect multiple Azure VMware Solution in an Azure Virtual Network private clouds
- Connect Azure VMware Solution private cloud in a Virtual Network to the previous edition of Azure VMware Solution private cloud
- Public and Private DNS forward lookup zone configuration