Microsoft unbundled Teams from its Microsoft 365 suite in 2025 after the European Commission accepted binding commitments to resolve a competition probe. The move was supposed to loosen the grip of ecosystem lock-in for enterprise customers. Yet for many organizations, one deeply embedded application, email through Outlook and Exchange Online, continues to function as the strongest anchor keeping them inside Microsoft’s product orbit, even as regulators chip away at the formal ties between other services.
What is verified so far
The European Commission’s antitrust case, designated AT.40873, targeted the bundling of Teams with Microsoft 365 and Office subscriptions. The Official Journal notice lays out proposed commitments and invites market feedback. Those commitments include interoperability requirements that would enable competitors to embed Office web apps within their own platforms, along with other technical and commercial terms designed to reduce tying between Microsoft products.
Microsoft confirmed that it entered into commitments with the European Commission in 2025. The terms address both the unbundling of Teams from Microsoft 365 and Office and broader interoperability obligations. Separately, the Associated Press reported that the Commission formally accepted these commitments, effectively closing the EU probe into Teams.
On the corporate side, Microsoft’s FY2025 Annual Report describes Microsoft 365 as a platform that bundles Office, Windows, security and compliance tools, and services including Teams. The company frames this integrated suite as an enterprise productivity platform, language that signals a continued strategic bet on keeping customers inside a tightly connected product family. Even with Teams sold separately, the rest of the bundle remains intact.
That framing matters because the regulatory fix targets one visible seam, the Teams-Office bundle, while leaving the deeper connective tissue largely untouched. Email is the clearest example. Exchange Online powers Outlook calendaring, contact management, and mail across desktop, web, and mobile clients. It feeds into Microsoft’s security and compliance stack, its identity layer through Azure Active Directory, and its collaboration tools. Removing Teams from the subscription box does not sever those connections.
What remains uncertain
Several questions remain open after the Commission’s acceptance of Microsoft’s commitments. The Official Journal notice invited market feedback, but no public summary of that feedback or any follow-up compliance report has been published in the sources reviewed here. Whether competitors have actually embedded Office web apps under the new interoperability terms, and how smoothly that process works in practice, is not yet documented in any primary record available in this reporting.
On the data portability front, Microsoft’s Graph API documentation shows that mailbox import and export APIs are available in preview for Exchange Online. These tools are designed to standardize high-fidelity mailbox export and import. The documentation covers what users can export, in what fidelity, and under what constraints. But the key word is “preview.” No independent benchmarks or third-party audits cited in the record have measured how well these APIs perform at scale, what format limitations persist, or how much manual work a migration still requires. The gap between a documented API and a painless switch can be enormous, and right now that gap is unquantified.
There are also no primary user testimonials or enterprise case studies in the public record that describe real-world switching barriers after the unbundling. The regulatory record addresses the structural problem of bundling, but it does not capture the daily friction that keeps an IT department from moving thousands of mailboxes to a competitor. No direct statements from Microsoft executives about email-specific retention strategies appear in the available institutional documents. The technical details exist, but the strategic intent behind them is left to inference.
The competition policy framework of the European Commission provides oversight context, yet the case-specific enforcement timeline beyond the initial acceptance is not detailed in any source reviewed here. Whether the Commission will audit interoperability compliance, seek further information from market participants, or revisit the commitments if market conditions do not change is an open question. The legal architecture for oversight exists, but the practical enforcement path is not spelled out in the documents cited.
How to read the evidence
The strongest evidence in this story comes from primary institutional documents: the Official Journal notice for Case AT.40873, Microsoft’s own legal commitments page, and the FY2025 Annual Report. These sources confirm the regulatory action, the binding nature of the commitments, and Microsoft’s own characterization of its product strategy. They are the load-bearing pillars of the factual record, establishing what was agreed, when, and at a high level, why.
The Associated Press report adds a useful chronological anchor, confirming the Commission’s acceptance and summarizing the regulatory rationale in accessible terms. It functions as corroboration rather than as the original source of any claim about the commitments themselves. The Microsoft Graph API documentation is technical rather than strategic; it tells readers what tools exist for mailbox migration but says nothing about adoption rates, vendor support, or success metrics.
What the evidence does not contain is equally telling. There are no independent studies measuring how many enterprises have actually switched away from Exchange Online or Outlook since the unbundling. There are no competitor statements in the cited record describing whether the interoperability provisions have opened meaningful market access. And there are no user surveys or IT administrator interviews in the primary documents that would quantify the practical switching costs that email imposes, from retraining staff to retooling security policies.
This absence creates a significant analytical gap. The regulatory documents prove that the EU identified a problem and extracted a remedy. Microsoft’s own filings prove that the company still views its integrated platform as a competitive advantage. But the middle ground, the lived experience of organizations trying to leave or stay, is populated only by inference. Readers should treat claims about retention rates or switching difficulty as plausible hypotheses rather than established facts until independent measurement catches up with the regulatory action.
One common assumption in coverage of the Teams unbundling deserves scrutiny: the idea that separating one product from a bundle meaningfully reduces lock-in. The evidence suggests a more complicated picture. Microsoft’s commitments address the formal act of bundling and the interoperability of specific components, but they do not dismantle the underlying architecture that makes Exchange Online central to identity, security, and collaboration inside Microsoft 365. As long as email, calendars, and directory services remain tightly coupled to the rest of the suite, the gravitational pull of Outlook and Exchange is likely to persist, even in a world where Teams can be purchased, and, in theory, replaced, on its own.
More from Morning Overview
*This article was researched with the help of AI, with human editors creating the final content.
