Connect Azure VMware Solution to your on-premises environment
In this article, you'll continue using the information gathered during planning to connect Azure VMware Solution to your on-premises environment.
Before you begin, there are two prerequisites for connecting Azure VMware Solution to your on-premises environment:
- An ExpressRoute circuit from your on-premises environment to Azure.
- A /29 non-overlapping network address block for the ExpressRoute Global Reach peering, which you defined as part of the planning phase.
You can connect via VPN, but that's out of scope for this quick start document.
Establish an ExpressRoute Global Reach connection
To establish on-premises connectivity to your Azure VMware Solution private cloud using ExpressRoute Global Reach, follow the Peer on-premises environments to a private cloud tutorial.
Verify on-premises network connectivity
You should now see in your on-premises edge router where the ExpressRoute connects the NSX-T network segments and the Azure VMware Solution management segments.
Everyone has a different environment, and some will need to allow these routes to propagate back into the on-premises network.
Some environments will have firewalls protecting the ExpressRoute circuit. If no firewalls and no route pruning are occurring, you can ping your Azure VMware Solution vCenter server or a VM on the NSX-T segment from your on-premises environment.
Additionally, from the VM on the NSX-T segment, you can reach resources in your on-premises environment.
Continue to the next section to deploy and configure VMware HCX