For years, enterprises ran their virtual machines on VMware inside Microsoft’s cloud, a pairing that seemed permanent. Microsoft has now ended it, and the migration is on.
Microsoft will no longer provide VMware licenses within Azure, according to Techzine Global. Existing VMware workloads running on the platform must be migrated, leaving enterprises that built their infrastructure on the combination of Microsoft’s cloud and VMware’s virtualization software with a forced move. Microsoft did not announce a specific deadline in the reporting, but the direction is unambiguous: the era of VMware as a first-class citizen on Azure is over.
The decision is a quiet but significant blow to VMware’s position in the cloud. VMware, acquired by Broadcom for $61 billion in 2023, has spent years trying to convince enterprises that its virtualization software remains essential even as cloud computing has moved to containers and serverless architectures. Microsoft’s move removes Azure, one of the largest markets for VMware’s software, from its distribution channels, and it tells enterprises that the future of virtualization on Microsoft’s cloud belongs to Microsoft’s own technology.
The affected customers are not marginal. A large share of enterprises that adopted Azure early did so with VMware workloads, running their existing virtual machines in the cloud rather than rebuilding them. For those companies, the change means planning a migration they did not expect, moving applications to Microsoft’s native virtualization stack or to containers, and doing so on a timeline set by someone else. Migration projects of this kind are measured in quarters and cost real money.
The strategic logic for Microsoft is straightforward. Every workload that runs on VMware inside Azure is a workload that depends on software from Broadcom, a company that is also one of Microsoft’s competitors in several markets. Microsoft has its own virtualization technology, including Hyper-V and the Azure-native tools that manage it, and it has been steering customers toward those products for years. Removing VMware licensing from Azure completes that process: what was once a partnership is now a migration program.
The change also reflects the wider shakeout in VMware’s relationship with the cloud industry. Broadcom’s acquisition of VMware was followed by dramatic changes to VMware’s licensing model, price increases and the elimination of perpetual licenses, moves that angered many enterprise customers. Cloud providers that once resold VMware software have been reassessing those arrangements, and several have wound down joint offerings. Microsoft’s decision is the largest of those moves, and it signals that the industry’s biggest platforms no longer see VMware as a partner worth keeping.
The implications for enterprises are practical and painful. Companies that standardized on VMware face a decision: move workloads to Microsoft’s native stack, migrate to another cloud provider that still supports VMware, or bring the workloads back to their own data centers. Each option carries costs, risks and timelines. Analysts said the migration wave will create winners and losers across the industry, with Microsoft hoping customers simply move to its own tools and competitors hoping the disruption drives customers to them.
VMware’s response will be closely watched. The company has argued that its software is the most efficient way to manage large fleets of virtual machines, and it has been pushing enterprises toward its own cloud offerings. Losing Azure as a distribution channel narrows that path. Broadcom, which has been reshaping VMware into a higher-margin business, may see the Microsoft move as confirmation that its strategy of focusing on large customers, rather than the broad channel, is the right one.
The broader lesson is about dependence. Enterprises that build their infrastructure on the combination of two vendors’ products can find themselves caught when the vendors’ interests diverge. Microsoft’s decision to end VMware licensing on Azure shows that cloud platforms are businesses with their own agendas, and that the products they sell today may not be the products they offer tomorrow. For the companies affected, the migration is an expensive inconvenience. For the industry, it is a demonstration of how quickly the ground can shift beneath an established technology.
The timing of the change matters to the companies affected. Many enterprises are already in the middle of broader cloud migrations, and the VMware decision forces them to sequence two transitions at once, moving workloads off a familiar hypervisor while also rationalizing where those workloads run. Cloud consultants and managed service providers are preparing for a wave of engagements, and analysts said the migration work will generate revenue for the ecosystem that helps enterprises make the switch. For Microsoft, the calculus is about control: every workload that moves to its native virtualization stack becomes more deeply integrated with its management, billing and AI services, which is exactly where the company wants its customers to end up. The end of VMware licensing on Azure is therefore less an ending than a redirection, steering a generation of enterprise workloads toward Microsoft’s own tools by removing the alternative.
