Australian IT teams are being asked to pick a private-cloud direction while VMware licensing, Azure Local maturity and public-cloud landing zones all move at once. The useful question is not “which hypervisor wins”. It is which operating model your organisation can staff, support and fund for the next five years.
VMware remains familiar. Clusters, storage policies, backups and operational runbooks already exist. That familiarity is an asset if you have people who still know the stack well and a licence position you can live with. It becomes a liability if the commercial terms force a rushed move, or if the remaining skills sit with two people who are already overloaded.
Azure Local (the current name for Azure-operated infrastructure on customer hardware) is attractive when you need Azure control-plane consistency close to a plant, hospital, mine site or latency-sensitive application. It is not a drop-in VMware replacement. Hardware qualification, networking, identity, patching and support boundaries are different. Teams that treat it as “Hyper-V with a new badge” usually discover the gaps during the first cluster upgrade.
Public Azure still wins for burst, new greenfield platforms, and workloads that benefit from PaaS. It loses when egress, data gravity, or a regulator’s interpretation of residency make a private footprint cheaper or simpler. Many Australian estates will stay hybrid for a decade. Design for that, rather than pretending a single destination will absorb everything.
A practical comparison should include: licence trajectory, cluster operations, backup and DR, identity, network paths to existing WAN and ExpressRoute, skills you can hire, and the cost of running two platforms during transition. North Ark typically starts with an application and dependency map, not a hypervisor bake-off. If a system cannot move without rewriting storage or licensing assumptions, that constraint belongs on the first slide, not the last.
All technical perspectives