AVS Hands-on Labs - Lab Environment
Azure VMware Solution Environment
The deployment of the Azure VMware Solution takes at least 2 hours to complete. If you are doing this on your own, visit the appendix section for instructions on how to configure the environment. However, If you are in a Microsoft organized event, usually it is pre-deployed for you with the following components and settings.
- Internet Access (outbound connectivity from AVS to the Internet)
- Public IP Addresses - 10 IPs (inbound connectivity from Internet to AVS)
- Azure VM used as Jumpbox (used for AVS management and as DNS Forwarder)
- Azure VNet with its corresponding Subnets and connectivity to AVS through an Azure Express Route Virtual Network Gateway.
Lab Architecture Diagram
On-Premises Connectivity
For testing purposes, you can connect the provided lab environment with your on-premises environment through Site-to-Site VPN to the Azure vWAN Hub, and that will allow on-premises connectivity to Azure VMware Solution. This is a self-paced exercise, and instructions are out of the scope of this lab guide. However, the following are some resources you can use to establish the VPN connectivity.
It’s important to mention that Express Route to on-premises is the recommended method to perform integrations and migrations through VMware HCX. The VPN approach is just for testing purposes.
Resources
Create an IPSec tunnel into Azure VMware Solution - Azure VMware Solution | Microsoft Docs
Connect to Azure VMware Solution (AVS) using VPN - Microsoft Tech Community
Site-to-Site VPN between NSX-T and Azure VMware Solution – Part 1 – vElements.net
Site-to-Site VPN between NSX-T and Azure VMware Solution – Part 2 – vElements.net
Architecture Diagram
