T-Mobile gets extended VMware support through Aug 3, 2026, pays $5.28M for the fight

T-Mobile is still on the hook for a major VMware dependency, and the clock is now measured in months, not years. According to court documents seen by The Register, the carrier runs VMware products on at least 303,000 CPU cores, described in court as “the base of the entire internal network” and “the place where 1,000 applications reside.” And even after Broadcom’s acquisition of VMware changed the licensing and support landscape, T-Mobile pushed back hard enough to win an injunction.

That injunction forces Broadcom to offer support beyond August 2025, but it comes with a price tag and a deadline. The court granted the injunction requiring T-Mobile to pay $5.28 million and post a $500,000 undertaking. The matter is now “somewhat urgent” because the injunction expires on August 3, 2026, which means T-Mobile may soon be unable to get support for its very substantial VMware estate unless a new arrangement is reached or support is extended again.

To understand why this is more than an IT procurement story, you have to look at how Broadcom restructured VMware’s product and commercial options after the 2023 acquisition. Broadcom stopped selling perpetual licenses and standalone support deals for customers with those licenses, and reduced VMware’s product range from over 150 products down to two subscription-only bundles. Broadcom now mostly sells its Cloud Foundation (VCF) private cloud suite.

That shift is what triggered the familiar “support rights” fight. When customers tried to exercise rights to extended support, Broadcom declined. The Register notes that AT&T tried as well and settled on confidential terms, while Tesco is pursuing its case in court. Broadcom’s position, as summarized in the reporting, is essentially an availability problem: when customers exercise an option for extended support, it argues it cannot deliver because the products covered by the contract no longer exist, contracts allow it to deny support for “dead products,” and subscriptions are now the industry standard.

T-Mobile’s story is the opposite of a passive customer exiting quietly. The telco began using VMware’s products in 2008, and court materials allege that in 2024 Broadcom notified T-Mobile it would not renew support after the initial two-year deal expired in 2025. The two parties kept talking about possible new arrangements, but T-Mobile also sought an injunction that would compel Broadcom to provide extended support. Broadcom opposed it, arguing T-Mobile waited too long to seek it. In one proposal discussed in court, T-Mobile suggested a $20 million deal for another two years of support.

Then came the pricing and the power play. In an affirmation filed last week, T-Mobile vice president of technology Kevin Luu says the carrier sought the arrangement “to be able to complete T-Mobile’s transition away from VMware at a more deliberate pace.” The court agreed to compel support beyond August 2025, but the settlement conditions did not settle everything. Broadcom kept providing support and also sought damages, arguing that the injunction meant it missed out on a new deal with T-Mobile. T-Mobile “rubbished” that argument in part because the parties were still in talks about a new deal.

As negotiations sharpened, Broadcom later proposed charging $24 million for extended support covering six products, saying it would cover over 20 staff needed to support T-Mobile. T-Mobile pushed back by pointing to its own support footprint, saying it has made just two support calls in 2026, which hardly justifies such a large staff and expense.

One reason this case is being watched beyond T-Mobile and Broadcom is that the presiding judge, The Honorable Jennifer G. Shecter, previously heard the dispute between VMware and AT&T. That earlier case ended in a confidential settlement, but in an October 2025 hearing Shecter indicated she thought T-Mobile’s case was stronger than AT&T’s: “I think this case is even more compelling and to be sure I was very compelled both in AT&T and very convinced.” VMware’s counsel argued the cases differ because AT&T moved quickly, while T-Mobile waited months before seeking extended support and an injunction.

The judge was not fully persuaded by the “outlier” framing. VMware’s counsel argued that “there are 10,000 customers,” and that thousands upon thousands have migrated to subscription. The reporting says Shecter suggested another possibility: some customers “don’t just want to fight Broadcom. I don't know. Or it's not worth it and maybe they're smaller scale and transitioning is easier.” The Register also notes that VMware last week named Nationwide Building Society as a customer that signed up for VCF, underscoring Broadcom’s “subscription transition” story even as T-Mobile fights for contractual continuity.

Broadcom’s broader argument is that customers moving to VCF subscriptions end up with a more efficient infrastructure that can improve business performance, pointing to strong VMware revenue growth as evidence. But for telecom operators and other large VM-dependent enterprises, the practical risk is immediate and operational: when the injunction ends on August 3, 2026, the question becomes whether support can continue, whether T-Mobile can finish its transition fast enough, and whether the “dead products” problem ends up mattering in court and in data centers.

Executives reading this should treat it like a governance and resilience lesson, not just a vendor dispute. If you have perpetual-license-era commitments, this case is a live reminder that commercial changes after an acquisition can collide with the mechanics of running critical systems. And if you rely on VMware at T-Mobile’s scale, the deadline is not abstract, it is calendar specific.