In Europe, Teams is no longer free: what that changes in the comparison
For years, the Microsoft Teams vs Slack debate was settled in one sentence: “Teams is already included in our Microsoft 365 subscription, so why pay for Slack on top?” It was an unbeatable argument, and it’s exactly the one that almost every comparison available online still repeats, as if Teams came free with the suite.
That’s no longer true in Europe — and even Microsoft’s US price list now offers the same suites without Teams (as of November 2026). Since the European Commission’s decision of September 12, 2025, Microsoft has been required to sell, in the European Economic Area and Switzerland, versions of its Microsoft 365 and Office 365 suites without Teams, at a lower price. In other words: on your invoice, Teams now has a line, a price, and therefore an opportunity cost. The question is no longer “should we pay for an extra tool” but “which of the two tools is worth the price gap.”
This shift completely changes the arithmetic of the decision, and it lands in the same year as a general Microsoft 365 price increase on the 1st of July 2026. A business leader renewing a contract in 2026 therefore faces, often without knowing it, a choice they never had to make: keep the full suite with Teams, or take the unbundled version and freely choose their team messaging tool.
This comparison tackles the problem from that end — real cost, real capabilities, real reversibility — rather than from the feature list, where the two products look more and more alike. It extends our head-to-head Google Workspace vs Microsoft 365, which covers the choice of collaboration suite as a whole; here, we zoom in on the team communication layer. To place that layer among the others, our overview of a small business’s digital stack in 2026 gives the big picture.
What exactly the European Commission imposed on Microsoft
The case stems from a complaint filed in 2020 by Slack Technologies — a Salesforce subsidiary since 2021 — accusing Microsoft of tying Teams to its office suites to squeeze out competition. A second complaint, from Germany’s alfaview, followed. The Commission opened a formal investigation, and Microsoft, rather than face a fine of up to 10% of its worldwide revenue, offered commitments.
On September 12, 2025, the Commission accepted those commitments and made them legally binding. The decision makes no finding of infringement — it’s a commitments procedure, not a sanction — but it binds Microsoft, with the same fine of up to 10% of worldwide revenue in case of breach. Three obligations follow, and for companies in Europe each has a direct effect on the buying decision.
1. Price unbundling. Microsoft must offer its suites without Teams at a lower price, and has committed to widen that gap — increasing the price difference by around 50% on some suites. The regulator’s aim is clear: make the saving visible enough that a customer can genuinely consider a competitor. Practical corollary: any sales communication presenting a bundle with Teams must also present its equivalent without Teams. If your reseller offered you only one price list, ask for the other.
2. Interoperability. Microsoft must guarantee competing services access to the interoperability features they need — directory, identity, integration with the rest of the suite. In practice, a Slack deployment alongside Microsoft 365 must not be a second-class citizen, technically hobbled to discourage its use.
3. Data portability. Microsoft must allow data produced in Teams to be extracted and taken elsewhere. These commitments run for up to ten years depending on the component. This is the most underestimated point: the main argument against leaving Teams — “we’ll never get our history back” — has been legally defused in Europe. It remains a project to carry out, but it’s no longer a contractual dead end.
The real price of Teams: price lists with and without Teams
Here’s the information you won’t find on the product page: exactly what Teams costs inside your suite. The table below shows the Microsoft list prices that took effect on the 1st of July 2026, in dollars per user per month with an annual commitment, as shown on Microsoft’s US pricing pages as of November 2026 (which list both versions) — the international reference grid; euro versions follow the same structure but vary by country, reseller and contract type.
| Plan | With Teams | Without Teams | Price of Teams |
|---|---|---|---|
| Business Basic | $7.00 | $5.40 | $1.60 |
| Business Standard | $14.00 | $10.79 | $3.21 |
| Business Premium | $22.00 | $18.79 | $3.21 |
| Office 365 E1 | $10.00 | $6.79 | $3.21 |
| Office 365 E3 | $26.00 | $17.45 | $8.55 |
| Microsoft 365 E3 | $39.00 | $30.45 | $8.55 |
| Microsoft 365 E5 | $60.00 | $51.45 | $8.55 |
Two takeaways stand out. First, the order of magnitude: on Business Standard and Business Premium, which cover the vast majority of small businesses, Teams is worth $3.21 per user per month ($1.60 on Business Basic). That’s not nothing, but it isn’t the price of a paid Slack plan either. Second, the step up on Enterprise plans: on the E3 and E5 suites, the gap climbs to $8.55, because the included version is Teams Enterprise, which is considerably richer. A mid-sized company considering unbundling therefore recovers a saving nearly three times larger than a small business does.
Note also that there are standalone Teams offers, for anyone wanting the reverse move — keeping Teams without the full office suite: on Microsoft’s US page as of November 2026, Teams Essentials is $4.00 per user per month, paid yearly, and Teams Enterprise is $8.55. This route mainly suits organizations where part of the workforce doesn’t need Office.
The trap to avoid: don’t compare the 2026 “without Teams” line with the price you pay today. Prices rose on the 1st of July 2026 — by up to 16% on Business Basic and 12% on Business Standard — and the increase applies on your contract’s anniversary date. Switching to the unbundled version may therefore narrow the gap with your current invoice without actually lowering it. To frame this kind of budget trade-off, our guide to the cost of a digital transformation for small businesses details the costing method.
Slack in 2026: the plans and what they really include
Slack has reworked its packaging since its acquisition by Salesforce, with an explicit logic: push artificial intelligence down into the paid plans rather than sell it as an add-on. US list prices in dollars per active user per month, annual commitment, as of November 2026; monthly billing adds about 20%.
| Plan | Annual price | What it brings |
|---|---|---|
| Free | $0 | 90 days of searchable history, 10 integrations, 5 GB of storage. Messages older than one year are permanently deleted. |
| Pro | $7.25 | Unlimited history and search, unlimited integrations, external channels (Slack Connect), conversation summaries and huddle notes. |
| Business+ | $15.00 | SSO / SAML, automatic account provisioning, compliance exports, AI enterprise search, translation, workflow generation, agentic Slackbot included. |
| Enterprise+ | Contact sales | Multiple workspaces, data residency, encryption key management, advanced compliance and governance. |
The free plan isn’t an option for a business. The 90-day history limit isn’t a cosmetic annoyance: it deprives you of the company’s memory. Every decision made in a channel, every trade-off, every technical explanation disappears from search after a quarter, then is permanently erased after a year. For professional use, the honest comparison point with Teams is therefore Slack Pro, at $7.25, not Slack Free.
The useful tipping point is between Pro and Business+, and it’s less about features than about compliance: SSO, automatic provisioning and compliance exports. A small business with fewer than 50 people does very well on Pro. As soon as there’s an IT department, a centralized identity policy or retention obligations, Business+ becomes hard to avoid — and the price gap with Teams widens sharply.
Real cost over 3 years: a simulation for a 30-person small business
Let’s move from list price to decision. Assumption: a 30-employee small business on Microsoft 365 Business Standard, annual commitment, three-year horizon. The starting point is the same in every scenario — the office suite is a given, not up for discussion. Only the team communication layer varies.
| Scenario | Suite | Team messaging | Extra cost over 3 years |
|---|---|---|---|
| A — Status quo | Standard with Teams $14.00 |
Teams (included) | Baseline |
| B — Unbundled + Slack Pro | Standard without Teams $10.79 |
Slack Pro $7.25 |
+ $4,363 (≈ $1,454/yr) |
| C — Unbundled + Slack Business+ | Standard without Teams $10.79 |
Slack Business+ $15.00 |
+ $12,733 (≈ $4,244/yr) |
| D — Both tools | Standard with Teams $14.00 |
Slack Pro $7.25 |
+ $7,830 (≈ $2,610/yr) |
What this calculation shows. The extra cost of Slack Pro compared with Teams isn’t $7.25 per user per month, but $4.04 — since dropping Teams lowers the Microsoft bill by $3.21. Over three years and thirty people, the trade-off therefore comes to about $4,400, or roughly $1,450 a year — about $120 a month for the whole team. For a small business, it’s a real decision but not a chasm, to be weighed against a daily productivity gain across the whole team.
Scenario D is the most common — and the worst managed. Many companies end up with both tools in parallel: Teams because it’s in the suite, Slack because a technical team or a partner agency imposed it. It’s the worst of both worlds: you pay for all of Slack without recovering the unbundling saving, and above all you split internal conversation across two platforms, which destroys exactly the value you were looking for. If you’re in this situation, the first gain to go after isn’t switching tools, but choosing between the two and moving the suite to the no-Teams version if Slack wins.
Finally, watch out for an item missing from the table: migration cost. Recovering history, recreating channels, reconnecting integrations and above all getting teams used to the new tool is a project of several weeks. When switching from one tool to the other, this human cost often exceeds the first year’s subscription gap.
Where Teams wins, where Slack wins
Teams is better at meetings and office integration. It’s first and foremost a video-conferencing and business telephony solution with messaging grafted on, whereas Slack is the reverse. Structured meetings — large groups, external guests, physical meeting rooms, recording, transcription, captions — are its natural ground, and the Teams Phone option can replace a traditional phone system, which Slack doesn’t claim to do. Co-editing a Word or Excel document directly in the conversation thread, without leaving the app, remains a real comfort for organizations that live in Office. Finally, administration happens in the same console as the rest of the suite, with the same identities and security policies: for a small business without a dedicated IT department, that’s a weighty argument.
Slack is better at asynchronous conversation and application integration. Its strength lies in three mechanisms Teams has never really matched: channels organized by topic rather than by team, threaded replies that isolate a conversation without cluttering the channel, and search that actually finds a decision made eighteen months ago. Together they produce what distributed organizations call a searchable company memory — an asset whose value you only measure when you lose it.
The second differentiator is the integration ecosystem. Slack was designed as a convergence point for application notifications: development tools, CRM, monitoring, automation platforms. A well-configured channel becomes the live dashboard of a business process, where the alert arrives with action buttons next to it. If you already orchestrate automations — a topic we cover in our comparison n8n vs Make vs Zapier — Slack is the most natural output point on the market.
Slack’s third asset is Slack Connect, which lets you open a shared channel with a customer, supplier or partner, each staying in their own workspace. For an agency, a consulting firm or a service business working closely with its clients, it’s often the deciding criterion: replacing dozens of email threads with a permanent channel transforms the client relationship.
| Criterion | Microsoft Teams | Slack |
|---|---|---|
| Nature of the product | Video conferencing and telephony with messaging | Channel-based messaging with video conferencing |
| Structured meetings | Excellent (large groups, rooms, telephony) | Adequate (huddles, informal format) |
| Asynchronous conversation | Adequate, organized by teams | Excellent, topic channels and threads |
| History search | Average | Historic strength of the product |
| Application integrations | Solid in the Microsoft world | Largest catalog on the market |
| External collaboration | Guests in the team | Slack Connect (cross-company channels) |
| Built-in office apps | Native (Word, Excel, PowerPoint) | Via connectors |
| Artificial intelligence | Copilot as a paid add-on | Included in paid plans |
| Net cost (small business on M365) | $3.21/user/month | $7.25 (Pro) to $15 (Business+), i.e. $4.04 to $11.79 net of the unbundling saving |
AI: two opposite business models
This is where the gap widened most in 2026, and it isn’t about model quality but about how AI is billed.
On the Slack side, AI is included in the subscription. Conversation and thread summaries, as well as automatic huddle notes, are available on all paid plans. The Business+ plan adds AI-assisted enterprise search, translation, recaps and natural-language workflow generation. Salesforce has also rebuilt Slackbot as an agentic assistant able to act on connected tools, included at no extra consumption cost in Business+ and Enterprise+, and rolled out in a more limited version on the Free and Pro plans since April 2026. Agentforce agents and partner AI apps can also be deployed on all paid plans.
On the Microsoft side, AI is a separate product. Copilot remains an option billed on top of the suite. Since the 1st of July 2026, Microsoft has made bundled plans permanent — Business Standard or Business Premium with Copilot — as well as a standalone Copilot Business offer at $21 per user per month, paid yearly, with a promotional price of $18 through the end of 2026 (US page, as of November 2026). In return, the scope is much broader: Copilot works in Word, Excel, Outlook and PowerPoint, not just in team messaging.
How to decide. If your AI need is about conversation — finding a decision, summarizing a channel after time off, translating an international team’s exchanges — Slack delivers that value with no extra line on the invoice, and the price gap with Teams justifies itself. If your need is about producing documents, spreadsheets and letters, Slack’s AI doesn’t answer the question and you should look at Copilot. The two aren’t mutually exclusive, by the way. To assess what these assistants are really worth day to day, our ChatGPT vs Copilot vs Claude comparison for business details the use cases and limits for small businesses.
GDPR and data sovereignty: what’s true on both sides
Let’s be frank: neither is a sovereign solution. Microsoft and Salesforce are both US companies, subject to the CLOUD Act, which allows US authorities to request data held by a company under their jurisdiction, including when that data is stored in Europe. For European customers, this tension with Article 48 of the GDPR isn’t resolved by any technical measure, and it should be treated as a documented risk rather than an eliminated problem.
That said, both vendors offer serious data residency options. Microsoft operates the EU Data Boundary, which processes and stores customer data for core services — Teams included — in the European Union and EFTA. Salesforce offers data residency through its Hyperforce infrastructure, with European regions including Germany and France, and a European operating zone; for Slack, this covers message storage, search indexes and encryption keys within the EU. Both rely on standard contractual clauses and the EU–US Data Privacy Framework for residual transfers.
What to do, whatever you choose (if you handle EU personal data): sign the data processing agreement, explicitly enable European residency — it isn’t always on by default and depends on the plan, notably at Slack where the most complete options belong to Enterprise+ —, list the processor and its sub-processors in your record of processing activities, and set a message retention period. That last point is the most often neglected: keeping every internal conversation indefinitely runs against the storage limitation principle and turns your messaging into an uncontrolled trove of personal data. Our GDPR compliance guide for small businesses walks through the full process, and our article on securing a hybrid cloud with a Zero Trust approach covers the technical side of data access.
Verdict: which tool for which kind of company
Choose Teams if your company is already fully equipped with Microsoft 365, your teams live in Word and Excel, your main use is meetings rather than written conversation, and you have no IT department to administer an extra tool. That’s the case for most small businesses in France, and it’s a rational choice: the $3.21 per user gap is only justified if you’re really going to use what Slack does best. If you’re also considering replacing your phone system, Teams Phone strengthens that reasoning further.
Choose Slack if your organization is distributed or significantly remote, if your work culture is asynchronous and written, if you have technical or product teams living in application notifications, or if you work in a permanent channel with external clients and partners. Agencies, software vendors, consulting firms and IT services companies get a clear return on investment from it. In that case, go all the way: switch your Microsoft suite to the no-Teams version to recover the saving, rather than paying for both.
Keep both only in one legitimate scenario: Teams as the meeting and business telephony platform, Slack as the written workspace and integration hub. This coexistence works on one non-negotiable condition — explicitly defining and enforcing the rule that says what happens where. Without that rule, you don’t have two complementary tools, you have two silos and information nobody can find.
And if you’re not on Microsoft? A small business on Google Workspace doesn’t have Teams included and chooses instead between Google Chat, included in its subscription, and Slack. The reasoning is the same, but the price gap is the full price: Slack then costs its $7.25 with no offsetting saving. Our comparison Google Workspace vs Microsoft 365 covers that upstream suite choice, which largely shapes this one.
Method: how to decide in 6 steps
1. Measure real usage before discussing price. Pull three months of usage statistics from your current tool: share of channel messages versus direct messages, number of meetings, volume of history searches. A company where 80% of traffic is direct messages doesn’t need a channel tool — it needs a change in practices, not in software.
2. Ask your reseller for both price lists. Demand the price of your suite with Teams and without Teams. In the EEA this is now an obligation stemming from the European decision; in the US, both versions appear on Microsoft’s public price list. Without those two figures, you can’t calculate Slack’s net cost.
3. Calculate the net extra cost, not the gross price. Subtract the unbundling saving from Slack’s price. On Business Standard, the real delta is $4.04 per user per month, not $7.25. Project it over three years and your actual headcount.
4. Check which plan level you really need. If you need SSO, automatic provisioning or compliance exports, your comparison point is Slack Business+ at $15 (US list price, annual billing, as of November 2026), not Pro. That nearly triples the net extra cost — $11.79 instead of $4.04 per user per month — and often changes the conclusion.
5. Handle compliance before signing. Enable data residency where you need it, sign the DPA, set a message retention period and document it all in your records. These settings are much easier to put in place at launch than to fix two years later on a history of several million messages.
6. Pilot with one team before rolling out. Deploy to a department of five to ten people for a month, with a written usage rule. You’ll measure real adoption and, above all, discover integration friction before it affects the whole company. This gradual rollout logic is developed in our complete guide to digital transformation for small businesses.
Frequently asked questions
Is Teams really free if I already have Microsoft 365?
Not anymore. Since the European Commission’s decision of September 12, 2025, Microsoft must sell versions of its suites without Teams, at a reduced price, in the EEA and Switzerland — and its US price list offers the same no-Teams versions (as of November 2026). On Business Standard and Business Premium, the gap is $3.21 per user per month on the July 2026 price list ($1.60 on Business Basic): that’s the real price of Teams. Teams remains included if you take the bundled version, but you now pay for it explicitly.
How much does Slack really cost on top of Microsoft 365?
Less than its sticker price, provided you unbundle. Slack Pro costs $7.25 per user per month with an annual commitment, but switching your suite to the no-Teams version saves you $3.21. The net extra cost is therefore $4.04 per user per month, or about $4,400 over three years for a team of thirty. If you need Slack Business+ ($15 per user per month, annual billing, as of November 2026) for SSO and compliance exports, that extra cost rises to about $12,700 over the same period.
Can you use Teams and Slack at the same time?
Technically yes, and it’s common, but it’s rarely a good idea without a clear rule. The legitimate case is an explicit split of roles — Teams for meetings and telephony, Slack for written work and integrations — formalized and enforced. Without that rule, you pay for two tools, you split internal conversation across two platforms and you make information impossible to find. And you lose the unbundling saving along the way, since you keep paying for Teams in your suite.
Is Slack’s free plan enough for a small business?
No, for a specific reason: history is limited to 90 days of viewing, and messages older than one year are permanently deleted. You therefore lose the memory of your decisions, which is precisely the main value of a channel-based tool. Add to that a limit of 10 integrations and 5 GB of storage. For professional use, the honest comparison point with Teams is Slack Pro, not Slack Free.
Are Slack and Teams GDPR compliant?
Both can be used in compliance, provided you sign the data processing agreement, enable European residency — the EU Data Boundary at Microsoft, the Hyperforce infrastructure with its German and French regions at Salesforce —, document the processor in your record of processing activities and set a message retention period. Be aware, however: both are US companies subject to the CLOUD Act, which creates an unresolved tension with Article 48 of the GDPR. Neither is a sovereign solution in the strict sense.
Need help deciding on your work environment?
Choosing between Teams and Slack isn’t a software choice: it’s a choice of working style, with a three-year cost and a switching cost. In 2026, it also comes with a contractual opportunity many companies overlook — the unbundling imposed on Microsoft in Europe, and the no-Teams versions now on its price list — which is negotiated at renewal time.
As a fractional CIO, I help leaders of small and mid-sized companies with this kind of decision: auditing real usage, costing the total, negotiating price lists with the reseller, and steering the rollout if a change is needed. If your Microsoft contract is up for renewal this year, now is the right time to ask the question. You can reach me at +33 6 18 85 20 10 to discuss it.