Book Image

The Ins and Outs of Azure VMware Solution

By : Dr. Kevin Jellow D.H.L (h.c)
Book Image

The Ins and Outs of Azure VMware Solution

By: Dr. Kevin Jellow D.H.L (h.c)

Overview of this book

Organizations over the world are migrating partially or fully to the cloud, but with the whole slew of providers, tools, and platforms available, knowing where to start can be quite challenging. If you know Microsoft Azure VMware Solution, you know it is the quickest way to migrate to the cloud without needing application modernization or rework. You can retain the same VMware tools to manage your environment while moving to Azure. But how does it work? The Ins and Outs of Azure VMware Solution has the answer. This high-level, comprehensive yet concise guide to Azure VMware Solution starts by taking you through the architecture and its applicable use cases. It will help you hit the ground running by getting straight to the important steps: planning, deploying, configuring, and managing your Azure VMware Solution instance. You’ll be able to extend your existing knowledge of Azure and VMware by covering advanced topics such as SRM and governance, setting up a hybrid connection to your on-premises datacenter, and scaling up using disk pools. By the end of the VMware book, you’ll have gone over everything you need to transition to the cloud with ease using Azure VMware Solution.
Table of Contents (20 chapters)
1
Part 1: Getting Started with Azure VMware Solution (AVS)
4
Part 2: Planning and Deploying AVS
9
Part 3: Configuring Your AVS
14
Part 4: Governance and Management for AVS

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

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.