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 ->Tweet about this on Twitter20Share on Facebook0Share on LinkedIn0Share on Google+0Email this to someone

One thought on “Comparing VMware Cloud on AWS and Azure

Leave a Reply

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