TL;DR: The EU has formally accepted Microsoft’s commitments to sell Office/Microsoft 365 without Teams and improve interoperability. Global unbundling began in 2024; the 2025 settlement cements rules for the next decade. Net effect: more purchasing “choice,” but higher complexity—and most organizations will only unlock value if they use this moment to simplify the stack, harden governance, and align Copilot to where work actually happens.

---

What just happened (and why it matters)

• Global unbundling: Microsoft began offering Office/Microsoft 365 without Teams worldwide on April 1, 2024, after first doing so in the EEA/Switzerland.
• EU settlement (Sept 12, 2025): The European Commission accepted legally binding commitments from Microsoft—no fine, but clear obligations on pricing options, switching flexibility, and interoperability/data portability with rivals. Commitments last up to 10 years for certain elements.
• Pricing signals: Microsoft has historically quoted €5/user/month for standalone Teams in the EU context and continues to adjust “with-Teams vs. without-Teams” price deltas across suites; Microsoft also signaled further frontline-suite adjustments effective Nov 1, 2025. Details vary by SKU and region.

Why this is a watershed: Unbundling curbs default lock-in, but it doesn’t make strategy for you. The value (or waste) comes from how you redesign collaboration, AI, and compliance around the new menu.

---

The upside (if you architect it)

1. License flexibility: You can standardize on Teams or decouple specific groups (e.g., engineering on Slack, Zoom Rooms for spaces) without paying for unused entitlements.
2. Sharper AI focus: Copilot value compounds where meetings, chat, files, and knowledge intersect; for many, that remains Teams—so the question becomes how to engineer that value, not whether it exists.
3. Negotiation leverage: Clear deltas between “with” and “without” SKUs create room to rationalize spend by persona.

The hidden downsides (if you don’t)

• Total cost can rise if you re-add Teams à la carte while also keeping incumbents.
• Governance sprawl: Multi-vendor chat/meet/telephony complicates retention, eDiscovery, legal hold, DLP, call recording, and quality-of-experience monitoring.
• Interoperability ≠ simplicity: Even with better APIs and data portability, identity, compliance boundaries, and meeting interop add operational overhead.

CIO decision framework (15-minute exercise)

1) Workflow gravity
Where does “work” actually happen today—chat, meetings, files, apps, and AI recaps? Map by persona (frontline, Sales, Support, Eng, Exec/Admin). If Teams is the center of gravity for most personas, dual-stacking may introduce more friction than value.

2) AI ROI path
List your top Copilot use cases (meeting notes → tasks, email draft, knowledge surfacing). If you want fast ROI, leaning into Teams’ native surface can reduce change management and context-switching.

3) Compliance surface area
Inventory retention/eDiscovery/call-recording needs by jurisdiction (e.g., E911 policy in North America, call recording for regulated teams). Multi-tool estates require policy parity.

4) Telephony & contact center
Reassess Teams Phone vs incumbent UCaaS, and how Contact Center (CCaaS) integrates—routing, analytics, transcripts, and recordings—without multiplying vendors.

Three viable strategies (pick one and commit)

1) Standardize on Teams

• Consolidate chat/meet/telephony into Teams; deprecate duplicative tools.
• Double-down on Copilot inside Teams (recaps, tasks, knowledge).
• When it wins: You prioritize speed, governance cohesion, and Copilot ROI.

2) Selective dual-stack

• Keep Slack for Eng and/or Zoom Rooms for spaces; Teams for everyone else.
• Enforce clear rules: identity, interop, retention, and eDiscovery mappings.
• When it wins: You have entrenched power users who’d lose velocity if migrated.

3) De-bundle by design

• If your org is deeply invested elsewhere, adopt without-Teams suites + standalone Teams only where required (external collaboration, certain meetings).
• When it wins: You can operationalize multi-vendor governance without sapping IT capacity.

---

30–60–90 Day Action Plan

Days 1–30 — Model & guardrails

• Persona-based TCO: Compare “with vs without Teams” across suites; include support, training, compliance, and meeting hardware.
• Data & AI guardrails: Confirm Copilot permissions, sensitivity labels, and conditional access.
• Records & eDiscovery: Align retention labels and legal-hold workflows across platforms.

Days 31–60 — Pilot & interop

• Stand up two pilots: (A) Teams-first cohort; (B) dual-stack cohort.
• Validate SSO, cross-tenant federation, calendar interop, guest controls, and meeting interop with key partners.
• Test call recording/E911 for regulated personas.

Days 61–90 — Decide & deploy

• Land license changes at renewal/true-up, not just EoQ.
• Pick a single operating model; deprecate shadow tools.
• Roll out a Copilot adoption sprint (executive admins, sales managers, project leads first).

Procurement & licensing checklist

• Lock a taxonomy for SKUs (with/without Teams) per persona.
• Check the standalone Teams price points in your region and agreement (EA/CSP); confirm the deltas versus bundles you actually hold.
• Validate Microsoft’s latest communications on frontline suite deltas and timing (e.g., Nov 1, 2025 adjustments).
• Ensure switching flexibility clauses align with the EU commitments timeline.

SOFTEL’s point of view

Unbundling is a regulatory milestone, not a collaboration strategy. The leaders we work with use this moment to simplify the stack, operationalize AI, and tighten governance—not to accumulate tools.

---