When your global provider changes ownership: what changes, and what doesn’t
- Ciaran Roche
In June, BT and Verizon announced they will combine their international enterprise businesses into a 50:50 joint venture. Around 3,000 multinational customers, more than 180 countries, roughly $4 billion in combined revenue, and a target completion date sometime in 2027. If your organization buys global connectivity from either company, you’re now part of one of the larger customer migrations this industry has attempted in years – whether you signed up for it or not.
There’s been plenty of commentary on what this means for BT and Verizon shareholders. I’m much more interested in the question that matters to the people I talk to every week: what does it mean for you as the customer?
The diagram versus the reality
Every global provider has a version of the same slide: a single cloud stretched across a world map, with your sites neatly connected into it. The joint venture announcement leans on this imagery too – one unified, AI-ready, platform that has answers to all the questions around resilience, compliance and data sovereignty.
That cloud has never really existed, and understanding why is the key to understanding what happens next. Underneath it sits the machinery that actually delivers your service, and that machinery is where mergers get complicated:
- Two OSS/BSS stacks. Ordering, provisioning, inventory, fault management, and billing systems that have each evolved over decades (including previous mergers and acquisitions), full of exceptions and workarounds. Consolidating these is a multi-year program, and while it runs, every order and every ticket you raise is crossing a landscape under construction. It’s not a seamless process.
- Two overlapping product portfolios. Both companies sell SD-WAN, managed security, cloud connectivity, and voice, often with different vendor stacks even in their own environments. Rationalization is inevitable – it’s the whole point of the scale efficiencies being promised. Some products will be designated “strategic”. Others will quietly stop getting investment long before any formal end-of-life notice reaches you.
- A vast web of third-party access. This is the detail I find most interesting. Neither parent is contributing subsea or terrestrial fiber to the venture. It’s a service-layer business, riding on the parents’ networks and hundreds of local access providers. That “180 countries” figure has always meant a patchwork of underlying carriers stitched together commercially. Those commercial arrangements now need to be renegotiated, novated, or replaced – and in the remote geographies where manufacturing plants, mine sites, and logistics hubs tend to live, there’s often only one or two viable access options anyway.
- Two account structures. Your account director, your service manager, the engineer who actually knows your network’s history. Integration creates uncertainty for these people, and the best of them are also the most employable elsewhere.
We've seen this movie before
The strategic logic of combining international enterprise units to achieve scale is not new. Concert (a BT joint venture, as it happens), Global One, Unisource – the industry has been through this several times, and the pattern was consistent: sound logic, difficult execution. Governance between parents was slow, portfolios overlapped, and customers were left unsure who owned what.
The IT services world offers a more recent parallel. When HP’s Enterprise Services business (itself the former EDS) merged with CSC to form DXC, the combined entity spent years rationalizing delivery centers, contracts, and platforms. Customers who were strategically important got attention. Many others experienced the integration as service degradation, account churn, and a roadmap that kept moving.
None of this means the BT/Verizon venture will fail. A 50:50 structure with a dedicated management team is a more serious partnership than the loose alliances of the 1990s, and the leadership appointments suggest they understand the execution challenge. But it does mean the next three to five years will be shaped by integration priorities, not just customer priorities. And with BT’s CEO already signaling this could be the first step in broader consolidation, possibly with additional partners, the ownership question may not be settled even after the deal closes.
What you gain, what you lose
It would be wrong to see this news as universally negative. There are some positives for enterprises.
You may gain scale, a more focused owner, and eventually a more modern platform – the venture is expected to be built around a genuinely cloud-native orchestration layer rather than legacy MPLS infrastructure. If you’re one of the flagship global Fortune 500 accounts, you’ll likely be well looked after, because the venture cannot afford visible failures early on.
What’s at risk is more subtle. Roadmap certainty, while portfolios are rationalized. Continuity of the people who know your environment. Negotiating leverage, if your renewal lands mid-integration when the provider’s attention is elsewhere. And if you’re a mid-sized multinational rather than a Fortune 100 behemoth, the risk of becoming the kind of account that integration programs like these deprioritize.
Advice to IT leaders
If I were running network strategy for a global enterprise with either provider today, I’d be doing four things:
- Map your actual dependencies. Not the cloud diagram – the real one. Which services, which underlying access circuits, which countries, which contracts, and when do they renew?
- Ask direct questions. Which products are strategic to the combined portfolio? What are the integration milestones? Who is my account team in twelve months? Vague answers are themselves an answer.
- Use the timing. A provider heading into a multi-year integration has strong incentives to lock in renewals early. That’s leverage, if you’re prepared to use it.
- Reduce the impact of provider change. This is the structural point. If your architecture is built on telco-independent SD-WAN and SASE, with your own choice of technology stack and diverse underlying internet access, then a change of ownership at any single provider is something you can plan for – a simple commercial change, rather than an architectural one. The enterprises I see navigate these transitions best are the ones for whom the answer to “what happens if our global provider changes hands?” is “not much.”
That last point is really the theme of most of what I’ve written about over the years. The traditional model required enterprises entrust their entire global network to a single carrier’s cloud diagram. Consolidation events like this one are a reminder of what that entrustment actually means. The alternative – owning your architecture and treating connectivity as a competitive, swappable input – has been proven at scale for a decade now.
The key takeaway is simple: build a network strategy that remains resilient, regardless of who owns the underlying provider.
