Azure VMware Solution Reviews & Insights

We are using it to build a DR solution. This is a project that is under testing and not complete yet, but the final goal is to have a copy of all of our VMs in our VMware cluster in Azure using the Azure VMware Solution.

It is a very robust solution for implementing DR and it is validated by Microsoft and VmWare. You can build the solution with only 3 hosts and expand later.

We need to have an open catalog for where to deploy our solutions, some on premise some in cloud. For cloud solution one of our prefered options to go is azure vmware to manage all our virtual computers on the cloud, our common are windows server and centOS, somethimes other but those two are our main.

Azure VMware Solution is best suited for rapid VMware lift-and-shift migrations, datacenter exits, disaster recovery, and regulatory workloads without refactoring. It is less appropriate for cloud-native applications, cost-optimized architectures, startups, or greenfield projects due to higher costs, architectural rigidity, and limited use of Azure PaaS services. We adapt to our client needs and almost always this is the winner!

Fast transition from on prem old server infrastructure to full cloud ready VMware solution. Optimizes labour cost and replaces old school on premises servers. This has improved our projected disaster recovery times and overall resiliency.

Best suited when existing on prem infrastructure going out of date/warranty and in need of big lump sun investment. Plus - predictable data recovery and backups. It is less appropriate for small business and light workloads (too expensive)

We migrated the VMware infrastructure to the Azure environment.It was a change. Although all the lock and feel is the same as the VMware environment, it's now a Microsoft service.Since we have mainly virtualized Windows servers and processes, the changeover is not noticeable to the user.On the technical side, the points are different but manageable.

Cloud-Native Applications: If you are building cloud-native applications that are designed to run on Azure, AVS may not be the best solution. In this case, you should consider using Azure-native services, such as Azure Kubernetes Service (AKS) or Azure Functions.Minimal Workloads: If you have a small number of workloads, it may not be cost-effective to use AVS. In this case, you can consider using Azure Virtual Machines (VMs) or other Azure services that are better suited for small workloads.Custom Hardware Configurations: If you require custom hardware configurations or specialized hardware, AVS may not be able to meet your requirements. In this case, you can consider using other Azure services, such as Azure Dedicated Hosts, that offer more flexibility in terms of hardware configurations.Cost-Sensitive Workloads: If you have cost-sensitive workloads, AVS may not be the best solution. While AVS offers many benefits, it can also be more expensive than other Azure services. In this case, you should consider using Azure services that are more cost-effective, such as Azure Virtual Machines.