Comparing VMware Cloud on AWS and Azure

While working with customers I get this question a lot so I wanted to share with you some of the differences between the two offerings. Please note this is not a competitive bashathon. Let’s face it, we live in a multi-cloud world and customers are leveraging both public and private clouds where it makes sense for them to grow and enhance their businesses or organizations. This post is intended to illustrate the technical differences between the two services.


VMware Cloud on AWS

Use vCenter client the same way you do in your data center. Leverage all your existing integration like Automation, CMDB, PowerCLI and scripts with no rework.


Separate client to manage anything deployed in Azure. Different API’s and requires you to port your existing integration’s over to Azure. Two systems of record and skill sets.

Migrating Workloads

VMware Cloud on AWS

Non disruptive vMotion. IP address stays intact.


File based copy, export import ovf or complete reinstall. IP address will need to change, no easy way back.


VMware Cloud on AWS -Host based pricing

All You Can Eat – Run as many VM’s as you want! Storage and licenses included in cost. Full Price List here

Azure – Per instance pricing

Priced per virtual machine -additional cost for storage Full Price List Here

DR Service

VMware Cloud on AWS – Full image and IP address mirrored

Host based replication, same IP address. Power on and business as usual.

Azure – File based backup and restore

File based, new virtual hardware and new IP address, lot’s of work to restore application.

Remember sharing is caring!

3 Replies to “Comparing VMware Cloud on AWS and Azure”

  1. I’m sorry, but this article is stupid. You should compare EC2 to Azure VMs. VMware Cloud on AWS is just for you to easily move to the cloud and abandon these expensive licenses as soon as you’ve come to mind that it does not make sense 😉 In addition, Azure has replication of virtual machines, including VMware and physical machines.

    • I think the article is relevant. Azure ‘replication’ is more like migration from VMware, Physical, as the machines must be Azure ready, better know as HyperV.

      Zerto does a good job at the block level replication from VMware to Azure by spinning up th machines in the flavor MS likes. It does the same for AWS, VMware. Howrver, like the article reads, failback on Azure is not pretty and very manual.

      I don’t think it’s feasible to think of moving VMware to AWS with every intention of dumping your on prem DC as the only reason to try this. DR makes a compelling scenerio on that platform. That would make it plausabe to dump a secondary DC in favor of a ‘pay as you need it’ DR site. But everyone knows that, right?

      Keep writing ‘ stupid’ articles. There are CIOs out there that need to see a simple way of learning to ask the correct questions. 😉


Leave a Reply

Your email address will not be published. Required fields are marked *


This site uses Akismet to reduce spam. Learn how your comment data is processed.