AVS high-level architecture
AVS provides a private cloud environment that can be accessed from both on-premises and Azure-based infrastructure. Connectivity includes services such as Azure ExpressRoute, VPN connections, and Azure Virtual WAN.
Specific network address ranges and firewall ports, on the other hand, are required for these services to be enabled.
A private cloud is deployed, and private networks are constructed for management, provisioning, and VM movement (vMotion).
These private networks will be used to connect to vCenter and NSX-T Manager, as well as for VM vMotion and deployment. You can review the Microsoft documentation at this link for more information: https://learn.microsoft.com/en-us/azure/azure-vmware/tutorial-network-checklist#routing-and-subnet-considerations. A connection between private clouds and on-premises settings is made possible through the usage of ExpressRoute Global Reach. Global Reach establishes direct connections between Azure ExpressRoute circuits at the MSEE level. An ExpressRoute circuit to on-premises is required for the connection, which is included in your subscription with a VNet. The reason for this is that VNet gateways (ExpressRoute gateways) are unable to transfer traffic between circuits. This implies that you can connect two circuits to the same gateway, but the traffic will not be transferred from one circuit to the other.
Each AVS environment is deployed with its own 10 GB ExpressRoute circuit (and, thus, its own virtual MSEE device), which allows you to connect Global Reach to the “local” peering location by creating a virtual MSEE device in each environment. It enables you to connect several AVS instances in a single region to the same peering site by using a VNet interface.
See the following high-level AVS networking overview:
Figure 1.3 – An overview of high-level AVS networking
The preceding diagram shows the logical connections between AVS and the customer’s on-premises data center. It also shows the connection between AVS and Azure. Global Reach is used to connect two or more ExpressRoute circuits.
