Deploy and configure Azure VMware Solution
Once you've planned your deployment, you'll deploy and configure your Azure VMware Solution private cloud.
The diagram shows the deployment workflow of Azure VMware Solution.
In this how-to, you'll:
- Register the resource provider and create a private cloud
- Connect to a new or existing ExpressRoute virtual network gateway
- Validate the network connect
After you're finished, follow the recommended next steps at the end to continue with the steps of this getting started guide.
Register the Microsoft.AVS resource provider
To use Azure VMware Solution, you must first register the resource provider with your subscription. For more information about resource providers, see Azure resource providers and types.
Sign in to the Azure portal.
On the Azure portal menu, select All services.
In the All services box, enter subscription, and then select Subscriptions.
Select the subscription from the subscription list to view.
Select Resource providers and enter Microsoft.AVS into the search.
If the resource provider is not registered, select Register.
Create an Azure VMware Solution private cloud
You can create an Azure VMware Solution private cloud using the Azure portal or the Azure CLI.
Sign in to the Azure portal.
Select Create a resource.
In the Search services and marketplace text box, type
Azure VMware Solutionand select it from the search results.
On the Azure VMware Solution window, select Create.
If you need more hosts, request a host quota increase.
On the Basics tab, enter values for the fields and then select Review + Create.
You gathered this information during the planning phase of this quick start.
Field Value Subscription Select the subscription you plan to use for the deployment. All resources in an Azure subscription are billed together. Resource group Select the resource group for your private cloud. An Azure resource group is a logical container into which Azure resources are deployed and managed. Alternatively, you can create a new resource group for your private cloud. Resource name Provide the name of your Azure VMware Solution private cloud. Location Select a location, such as east us. It's the region you defined during the planning phase. Size of host Select AV36. Number of hosts Number of hosts allocated for the private cloud cluster. The default value is 3, which you can increase or decrease after deployment. If these nodes are not listed as available, please contact to support to request a quota increase (https://docs.microsoft.com/azure/azure-vmware/request-host-quota-azure-vmware-solution?WT.mc_id=Portal-VMCP). You can also click the "If you need more hosts, request a quota increase" link in the Azure portal. Address block for private cloud Provide an IP address block for the private cloud. The CIDR represents the private cloud management network and is used for the cluster management services, such as vCenter Server and NSX-T Manager. Use /22 address space, for example, 10.175.0.0/22. The address should be unique and not overlap with other Azure Virtual Networks and with on-premises networks.
Verify the information entered, and if correct, select Create.
This step takes roughly 3-4 hours. Adding a single host in an existing or the same cluster takes between 30 - 45 minutes.
Verify that the deployment was successful. Navigate to the resource group you created and select your private cloud. You'll see the status of Succeeded when the deployment has finished.
For an end-to-end overview of this step, view the Azure VMware Solution: Deployment video.
Connect to Azure Virtual Network with ExpressRoute
In the planning phase, you defined whether to use an existing or new ExpressRoute virtual network gateway.
If you plan to scale your Azure VMware Solution hosts using Azure disk pools, deploying the vNet close to your hosts with an ExpressRoute virtual network gateway is crucial. The closer the storage is to your hosts, the better the performance.
Use a new ExpressRoute virtual network gateway
You must have a virtual network with a GatewaySubnet that does not already have a virtual network gateway.
|You don't already have a virtual network...||Create the following:|
|You already have a virtual network without a GatewaySubnet...||Create the following:|
|You already have a virtual network with a GatewaySubnet...||Create the following:|
Use an existing virtual network gateway
Request an ExpressRoute authorization key:
In the Azure portal, navigate to the Azure VMware Solution private cloud. Select Manage > Connectivity > ExpressRoute and then select + Request an authorization key.
Provide a name for it and select Create.
It may take about 30 seconds to create the key. Once created, the new key appears in the list of authorization keys for the private cloud.
Copy the authorization key and ExpressRoute ID. You'll need them to complete the peering. The authorization key disappears after some time, so copy it as soon as it appears.
Navigate to the virtual network gateway you plan to use and select Connections > + Add.
On the Add connection page, provide values for the fields, and select OK.
Field Value Name Enter a name for the connection. Connection type Select ExpressRoute. Redeem authorization Ensure this box is selected. Virtual network gateway The virtual network gateway you intend to use. Authorization key Paste the authorization key you copied earlier. Peer circuit URI Paste the ExpressRoute ID you copied earlier.
The connection between your ExpressRoute circuit and your Virtual Network is created.
Validate the connection
You should have connectivity between the Azure Virtual Network where the ExpressRoute terminates and the Azure VMware Solution private cloud.
Use a virtual machine within the Azure Virtual Network where the Azure VMware Solution ExpressRoute terminates. For more information, see Connect to Azure Virtual Network with ExpressRoute.
Log into the Azure portal.
Navigate to a VM that is in the running state, and under Settings, select Networking and select the network interface resource.
On the left, select Effective routes. You'll see a list of address prefixes that are contained within the
/22CIDR block you entered during the deployment phase.
If you want to log into both vCenter and NSX-T Manager, open a web browser and log into the same virtual machine used for network route validation.
You can identify the vCenter and NSX-T Manager console's IP addresses and credentials in the Azure portal. Select your private cloud and then Manage > Identity.
In the next tutorial, you'll connect Azure VMware Solution to your on-premises network through ExpressRoute.
Submit and view feedback for