Azure VMware Solution

Overview of Azure VMware Solution Next Evolution

Originally posted on 

This post provides an overview of Azure VMware Solution, its components, and resources to help customers get started.

The general availability (GA) for the next evolution of Azure VMware Solution (AVS) was announced yesterday during the Microsoft Ignite 2020 virtual conference. This is a joint partnership between Microsoft and VMware, where Azure VMware Solution is a Microsoft managed service built on Azure bare metal infrastructure and cloud verified by VMware. The initial launch of the Azure VMware Solution in May of 2019 was by CloudSimple; this latest release is built and architected by Microsoft, providing an integrated experience with Azure services. Azure VMware Solution is currently available in the following 10 regions: East US, North Central US, West US, UK South, Japan East, West Europe, North Europe, Canada Central, Australia East, and Southeast Asia. More regions will be available in the future; additional details can be found by searching the Microsoft Products available by region page. Customers running the CloudSimple Azure VMware Solution version also have a migration path to this latest release, leveraging VMware HCX.

Azure VMware Solution is powered by VMware Cloud Foundation: vCenter Server, vSphere, vSAN, and NSX-T. Also included is VMware HCX, the Swiss army knife of workload mobility. Customers can securely extend their networks and migrate workloads from on-premises (vSphere 6.x -7.x) to AVS or between AVS private clouds in different regions using a combination of migration options. Microsoft will handle the billing, lifecycle operations (upgrades), and troubleshooting of the service, allowing customers to focus on their workloads.

Getting Started

There are a few things you need to have in place before you can deploy an Azure VMware Solution private cloud. First, an Azure account, which you can get for FREE. Next, your account must be associated with a subscription that is either part of a Microsoft enterprise agreement or a Cloud Solution Provider (CSP). Finally, is requesting host quota for your subscription. Once quota is applied to a subscription, search for “Azure VMware Solution” in the Azure portal’s search box. Alright, you don’t need to type out the entire thing; it will appear within the first couple of characters in VMware. An option to deploy your first private cloud in your subscription will be displayed on the next screen. As part of the private cloud creation, there is some basic information needed:

  • Subscription – Billing framework that provides entitlement to deploy and consume Azure resources
  • Resource Group – Logical way to group Azure services
  • Location – Where to deploy the private cloud
  • Resource Name – Name of your private cloud
  • SKU – Node type used during deployment
  • ESXi Hosts – Number of hosts to deploy, min of 3 by default with the option to increase to a max of 16 per cluster
  • vCenter Admin Password – password used to log in vCenter with cloudadmin@vsphere.local
  • NSX-T Manager Password – password used to log in NSX-T manager with admin 
  • Address Block – CIDR block used when deploying management components, requires a /22
  • Virtual Network – A representation of cloud networking and provides abstraction and logical isolation. An Azure environment can contain multiple VNets.

Note: Providing vCenter Server and NSX-T credentials during a private cloud deployment is no longer required, they are now auto generated. If they need to be rotated you will currently need to open a support request.

[Previous private cloud creation screen]

[Updated private cloud creation screen]

Private Cloud

* ExpressRoute – Is a private and secure connection from a customer’s physical datacenter providing dedicated bandwidth into Microsoft Azure.

* Global Reach – Connects ExpressRoute bi-directionally from a customer’s environment to Azure VMware Solution.

A subscription can have 1-4 private clouds, each with a maximum of 4 clusters per cloud. An initial private cloud deployment starts with a 3-node minimum with the opportunity to add additional nodes during or scale-up later to a maximum of 16 nodes per cluster in the Azure portal. The hardware specification dropdown lists AVS36 as the current selectable node type. Below is a visual representation of the hardware specs for the AVS36, but it does not represent the actual server 🙂 An Azure Virtual Network (VNet) can be created during the initial private cloud deployment or afterward. If an existing VNet exists, it can also be used. A VNet is created to support an ExpressRoute from Azure VMware Solution to connect to other Azure services and allow connectivity back to an on-premises environment via Azure Global Reach. Once ready, click review and create. After you verify everything entered is correct, click the magical create button and wait for roughly 2+hrs for the process to complete. The process is mostly self-service from the Azure portal allowing you to get from zero to a private cloud which includes:

  • Provisioning of hardware and backbone networking
  • Installation and configuration of ESXi, vCenter Server, vSAN, NSX-T, and HCX
  • Creation of initial cluster including vSAN datastore encryption

Note: if you don’t have an Azure ExpressRoute, you can use a site-to-site VPN to connect to Azure VMware Solution private cloud, but you will not be able to use HCX for workload migration as this is not supported.

Post Deployment

When your private cloud is ready, you’ll be redirected to the overview page in the resource menu. This page is handy with valuable information; you can always come back here by searching your private cloud name or simply bookmarking. The first section we’ll want to select is identity. Here is where you’ll find your login information for NSX Manager and vCenter Server. Next is clustering, where you can edit (aka increase/decrease) the number of nodes in a private cloud, with 3 being the magic number of minimum nodes. Keep in mind increasing the number of nodes is tied to your allocation associated with the subscription used.

The NSX T-1 router is where all workload network segments need to be created before VMs are deployed or being migrated to a new segment. These segments can be created in NSX manager or directly in the Azure Portal under segments, including the ability to create DHCP servers to handle DHCP requests and DHCP relay services to relay DHCP traffic to external DHCP servers. Additional workload networking options such as port mirroring and DNS are also available.

I’ve mentioned VMware HCX; the good news, it’s automatically deployed as part of the private cloud provisioning. The HCX Cloud manager is where you’ll get the necessary HCX Connector bits to deploy in your on-premises environment, which can be found under the connectivity section in the Azure portal of your private cloud. The HCX Cloud manager address is provided, and you will use cloudadmin@vsphere.local credentials to login and download the HCX connector bits. Licensing your HCX connector is also part of the self-service offering, allowing you to request up to 3 advanced licenses. Additionally, there is an option to upgrade your HCX advanced license to an HCX enterprise license by opening a support request with Microsoft. HCX enterprise will provide features like mobility groups, replication assisted vMotion, mobility optimized networking, and more. These features make use cases like datacenter extension and evacuation easier to any VMware powered cloud.

Once the HCX connector is deployed and configured on-premises, customers can access and manage directly from the vSphere client, the dedicated HCX Client, or via automation using PowerCLI or REST APIs. A site pairing can then be established with on-premises environments and an Azure VMware Solution private cloud, followed by L2 connectivity for workloads that will retain their IP addresses. Let the migration planning begin!

There are additional support and licensing benefits that come with Azure VMware Solution. Microsoft is providing extended support for Windows Server 2008 and SQL SQL 2008 workloads when they are migrated to Azure, including the Azure VMware Solution. There is also the Azure Hybrid Benefit which is a licensing benefit allowing customers to use their on-premises Windows Server and SQL Server licenses on Azure.

Check out the upcoming Azure VMware Solution Digital Event on March 23rd for more details.


Here are a few resources help get you started in learning more about Azure VMware Solution and more will be added as they are available. Also please reach out if you know of any others!