Earlier this week, Microsoft let slip that they were working with Premier VMware partners on a tech preview to deploy a full VMware stack on Azure bare-metal hardware, co-located with other Azure services.
Initially billed as a ‘stepping-stone’ to full Azure Cloud, Microsoft have made known that “sometimes there are specific VMware workloads that can be more challenging to migrate to the cloud” – and so customers may need the option to run these workloads on a VMware stack in Azure (for the time being). What I can’t quite work out yet is what these “workloads” would be… after all, nearly every workload I’ve ever deployed on VMware can be easily re-deployed on Hyper-V!
Microsoft have mentioned that this new VMware stack on Azure will GA in 2018. What they haven’t mentioned is who they’re working with, who will own and support the service and how it would be licensed…. for a start, it’s very interesting that it’s not being developed alongside VMware, and VMware have come out to say they’re not aware of any of their partners collaborating alongside VMware engineering to deliver this service – in fact VMware have stated it’s being developed independent of VMware and is “neither certified nor supported by VMware…. VMware does not recommend and will not support customers running on the Azure announced partner offering.” – which kind of makes you wonder what happens if a customer encounters problems with this Azure service?!? I highly doubt there will be any enterprise customers taking up this un-supported Azure service!!
I’m not sure why Microsoft have stated that “running your VMware stack in the cloud doesn’t address your hybrid requirements”… surely the fact that having a common framework on-prem and off-prem (ie VMware Cloud Foundation) is that “true consistency across your cloud and on-prem environment” that Microsoft say is missing….?!? Whilst it maybe true that Azure can provide a complete hybrid cloud package, let’s face it their Azure Stack offering is pretty limited – only a select few hardware vendors, no ability for customers to use their own hardware and lack of ability to expand/upgrade – plus I’m not aware of many customers jumping on board the Azure Stack on-prem platform! Also, when it comes to networking, Microsoft’s offering lacks the features of what NSX offers to VMware customers!
Should VMware start getting worried about this new announcement…..? On the contrary, they seem to have embraced the idea and even have the audacity to spin this announcement as Microsoft “recognizing the leadership position of VMware’s offering…. as a superior and necessary solution for customers over Hyper-V…..!!” TBH, they’ve never really seen much damage done to their vSphere install base when Microsoft started releasing tools to help people migrate off VMware, so I doubt this new announcement will trouble their new VMware Cloud on AWS offering.
It’s interesting that it was announce alongside the new Azure Migrate service which helps you discover and plan the migration of your on-prem VMware workloads and then execute the migration with Azure Site Recovery (ASR).
In my opinion, it’s all just a bit of hot air coming from Microsoft to try and take some of the plaudits before next weeks AWS re:Invent conference!
However, I do hope that Microsoft swallow some pride and reach out to VMware and start a combined engineering/development effort as that will go a long way to what every man and his dog wants to see – VMware Cloud on Azure! Only when Azure comes on board will VMware be able to say they are now a “broker of cloud” as only then will customers be given the option to migrate workloads seamlessly between the 2 biggest players in the public cloud market! (TBH given the relationship VMware has with GCP, I can see VMware Cloud on GCP happening first before Azure – although hardly anyone uses GCP!)
I mean, VMware and Microsoft already partner to offer VMware Horizon Cloud on Azure, surely they can put their differences aside and produce the one thing everyone is asking for!
…. watch this space….. (in eager anticipation!)