Microsoft will sell Teams as a $5-per-user standalone app and offer Office suites without the collaboration tool to customers worldwide, capitulating to a European antitrust probe that began after a 2020 complaint from Slack. The move, paired with binding interoperability promises, marks one of the most significant antitrust remedies in enterprise software since the browser wars—and it hands IT buyers new leverage to trim costs and mix vendors.

On Tuesday, Microsoft formalized a package of commitments before the European Commission that includes unbundling Teams from Microsoft 365 and Office 365 globally, publishing clear price differentials, and opening APIs so rivals like Zoom and Slack can integrate as deeply as Teams does with Word, Excel, and Outlook. The Commission will now market-test the proposal, and a negotiated settlement—without fines—could land before year-end.

How a Slack Complaint Turned into a Global Antitrust Reckoning

The story traces back to July 2020, when Slack filed a formal complaint in Brussels alleging Microsoft illegally tied Teams to its dominant Office suite. Slack argued that forcing customers to accept Teams as part of a bundle distorted competition in the then-booming collaboration market. As the pandemic supercharged remote work, Teams’ monthly active users ballooned to over 320 million, embedding the app inside countless organizations that might have otherwise chosen a rival.

European regulators opened a preliminary investigation, and by 2023 Microsoft began offering no-Teams SKUs in the European Economic Area and Switzerland. But the Commission’s concerns ran deeper than simple unbundling: rivals complained they couldn’t match Teams’ integration with Office apps, and that moving data out of Teams was too hard. In April 2024, Microsoft extended the unbundled options to new customers globally, signaling a broader retreat. The formal commitments submitted in May 2025 aim to lock in those changes and add technical firepower behind the promises.

What Microsoft Has Pledged: Price Deltas, APIs, and a Seven-Year Agreement

The remedy package rests on three pillars:

  • Unbundled SKUs: For the first time, enterprises everywhere can buy Microsoft 365 or Office 365 plans without Teams. A standalone Teams SKU lets organizations license only the collaboration platform.
  • Pricing transparency: Teams standalone costs roughly $5 to $5.25 per user per month. The no-Teams Office suites start near $7.75 per user per month, depending on tier—roughly $2 cheaper than bundles that include Teams. Exact pricing varies by region and plan, but the gap aims to show customers they aren’t paying a hidden Teams tax.
  • Interoperability and data portability: Microsoft commits to documented APIs that let third-party apps embed Office Web Apps, exchange data with Outlook, and access Teams-level services. It must provide data-export tools so organizations can extract chat, file, and meeting metadata in standard formats and move them to competitors. Reference implementations and SDKs should help rivals build integrations, and service-level agreements promise API stability and backward compatibility.

The company says these commitments will last seven years for product availability and price deltas, with interoperability terms extending even longer. If the Commission accepts them, the binding decision would settle the case without finding Microsoft liable or imposing a fine—but any breach could trigger fresh penalties.

What the EU Actually Wants to Fix

The Commission’s worry is threefold. First, bundling gave Teams a distribution advantage that no competitor could replicate, unfairly tilting the market. Second, integration barriers kept rivals from matching the seamless experience users got with Teams and Office—undermining competition on quality. Third, data lock-in made it costly for customers to switch, entrenching Microsoft’s position even after unbundling.

The remedy targets each problem directly. By unbundling and assigning a visible price, Microsoft must now compete on merit. Interoperability guarantees aim to level the technical playing field. And portable data lowers exit barriers. Together, they create what EU competition chief was quoted as calling “a meaningful space for rival innovators.”

Industry Reacts: Cheers, Caution, and Realpolitik

Salesforce, Slack’s parent, called the commitments “a vindication of the market’s concerns” but said it would scrutinize the fine print. Other competitors like Zoom and Cisco Webex see an opening to pitch best-of-breed stacks. Enterprise customers, especially multinationals, welcome the chance to standardize procurement globally and trim spending on unused Teams licenses.

But many analysts warn that the impact could be muted. “Microsoft’s gravitational pull isn’t just about SKUs—it’s about Entra ID identity, Azure cloud, and Copilot AI,” said one Gartner analyst. Switching collaboration tools means reworking authentication, conditional access, and user habits. Even with open APIs, rivals must invest heavily to match the polish of native Office integration. For most shops, the bundle will remain the path of least resistance.

Winners, Losers, and the Muddy Middle

The obvious winners are standalone collaboration vendors that can now compete on price and, eventually, on a more equal technical footing. Companies like Zoom and Slack can pitch feature-by-feature comparisons without an artificial price handicap. Enterprises that prefer a multi-vendor approach get clearer choices and lower friction.

Microsoft emerges with its business intact but not unscathed. Revenue may dip if some customers drop Teams, and the compliance and engineering costs of maintaining open APIs and data portability will be non-trivial. Yet the settlement avoids a larger structural remedy—like a forced sale of Teams—and Microsoft retains its broader ecosystem lock-in. Small vendors reliant on proprietary integrations or network effects may not feel much relief if customers stay put.

The EU’s commitment procedure is a well-worn path. After publishing Microsoft’s proposal, the Commission opens a market test—typically 4–8 weeks—where rivals, customers, and experts file feedback. If the feedback is generally positive, the Commission makes the commitments legally binding. That decision closes the antitrust case without an infringement finding, but it includes monitoring and reporting obligations.

If Microsoft fails to uphold the commitments, the Commission can impose fines up to 10% of worldwide turnover. The seven-year duration is designed to let competitors gain durable footholds; after that, the market may be restructured enough that the remedies become unnecessary.

The Technical Backbone: APIs That Actually Work

The loftiest promises mean nothing if the APIs are throttled, poorly documented, or changed without notice. IT leaders should push for:

  • Public, versioned APIs for embedding Office documents, accessing chat histories, and syncing calendars—not hidden endpoints.
  • Data export in open standards like JSON or CSV, not proprietary blobs that require manual transformation.
  • SDKs and reference apps in major languages so vendors can build, test, and certify integrations.
  • Contractual SLAs on API uptime, rate limits, and deprecation notice periods.

Third-party validation will be crucial. Independent audits, perhaps commissioned by the Commission or industry groups, could confirm whether the APIs deliver on their promise. If they don’t, the remedies could become a paper tiger.

What Procurement and IT Teams Should Do Now

For organizations with upcoming renewals, the new landscape demands action:

  • Audit your licenses: Map every user seat to a bundle. Identify pockets where Teams goes unused—frontline workers, contractors, or departments loyal to Slack or Zoom.
  • Model total cost of ownership: Compare the bundled cost versus a la carte pricing (Office without Teams + standalone competitor). Factor in migration, training, and administrative overhead.
  • Segment your users: Power users may keep the bundle; task workers might get a stripped-down suite and a different collaboration tool.
  • Negotiate hard: Use the EU’s commitment as leverage for global pricing consistency, multi-year caps, and contractual guarantees around interoperability.
  • Pilot before migrating: Run dual-vendor environments in a small cohort to validate that API integrations, sign-on flows, and data portability actually work at scale.

Risks and Reasons for Skepticism

Several uncertainties could dim the remedies’ impact:

  • Rollout timing: Although Microsoft says it will align global offerings if the EU accepts the commitments, exact local availability dates and prices may vary. Procurement teams must confirm SKUs with their Microsoft representative.
  • API depth: Until independent developers build real integrations, the interoperability pledges remain theoretical. Microsoft could comply with the letter—exposing rudimentary endpoints—while keeping the most valuable deep integrations exclusive.
  • Enforcement muscle: The Commission’s ability to monitor and enforce such complex technical commitments is untested. A light-touch approach could let compliance atrophy.
  • Market inertia: Even with free rein, persuading an enterprise to migrate away from Teams is a multi-year, multi-million-dollar decision. Bundled pricing and ecosystem stickiness may blunt any competitive rush.

Beyond Teams: The Precedent for Platform Competition

This case will echo far beyond the collaboration market. It establishes a regulatory template: rather than demanding breakups, the EU extracted targeted behavioral remedies—unbundling, pricing transparency, and open APIs—and left the core product intact. That model could apply to other bundled ecosystems, from cloud marketplaces to AI assistants.

It also reinforces the EU’s de facto role as the world’s tech regulator. Microsoft’s decision to globalize the remedies rather than maintain a two-tier system shows that a single jurisdiction can drive worldwide product design. Other vendors facing antitrust scrutiny will watch whether the commitments actually restore competition or merely soothe regulators while the dominant player profits on.

The Bottom Line

Microsoft’s unbundling of Teams is not a revolution. The company’s identity management, cloud platform, and AI integrations still bind users tightly to its stack. But it is a meaningful regulatory victory—one that gives buyers a visible price, a contractual path to multi-vendor environments, and a playbook for demanding technical transparency.

The real test is in the implementation. If the APIs are robust and the price deltas are sustained, competitors will finally get a shot at a fair fight. If not, this will be remembered as a well-publicized settlement that changed little. For Windows administrators and CIOs, the time to start testing is now.