Microsoft Teams reached 200,000 organisations across 181 markets within roughly a year of general availability — a figure Microsoft announced in early 2018, describing four-fold growth over the period and crediting the Office team under Kirk Koenigsbauer. Teams had been unveiled in November 2016 and became generally available in March 2017. By the anniversary it was the fastest-growing business application in the company's history. The number is real and it is also the least interesting part of the story, because it measures tenants with Teams enabled rather than organisations that had decided to use it. Teams grew the way Microsoft products have always grown: it was included in a subscription that a very large number of businesses already paid for, and it was switched on by default. That is not a criticism — it is the most important fact about enterprise collaboration economics, and misreading it led a lot of buyers to the wrong conclusions. Because for the IT director who arrived on Monday to find a new chat platform live in a tenant already running a different one, the question was never whether Teams was better. It was what to do about a product that had appeared without a procurement decision.
Why bundling won, and what it actually beat
The competitive case in 2017 favoured the specialists on product quality. Teams was noticeably rougher in its first year — slower client, weaker search, fewer integrations, an information architecture that confused users who had learned channel-based chat elsewhere. Slack's "Dear Microsoft" newspaper advertisement the previous year had been confident for good reason. Bundling beat it anyway, and the mechanism deserves precision because it generalises. Teams removed three separate procurement decisions at once: the licence purchase, the security and compliance review, and the identity integration. An organisation already on Microsoft cloud subscriptions had budget approved, a data processing agreement in place, single sign-on configured, retention and legal hold already covered by existing tooling, and administrators who understood the console. A competing platform, however superior, had to win a budget request, clear a security review, be added to the compliance estate, and be integrated with identity. The specialist had to be better by enough to justify all four. For most mid-market organisations it never was. The secondary effect mattered as much. Teams bundled chat with meetings and voice, which turned the comparison from a chat decision into a collaboration-and-telephony decision — and once conferencing consolidation entered the frame, the specialists were competing against a suite rather than against a feature. The organisations that stayed with a specialist platform generally had a specific reason: deep integration dependency, a developer culture built around it, or a genuine workflow requirement the bundled product did not meet.
| Layer | Decision to document | Evidence to check |
|---|---|---|
| Conversation | Name the primary place for team discussion. | Find a recent working decision and its owner. |
| Meetings | Choose where scheduled and external meetings run. | Test actual participant access and working devices. |
| Exceptions | Define where a specialist tool remains justified. | Record its scope, owner and review date. |
| Records | Set responsibility for retention and access. | Test retrieval after an owner leaves. |
Qualitative summary of this article's source text, not a measured outcome or performance estimate.
What buyers should have done — and mostly did not
The worst outcome was the most common: run both. Teams enabled by default, the incumbent platform still in use, teams splitting along lines nobody chose, and decisions living in two systems with no search across either. That is the sprawl problem in its purest form, and it persisted for years in a great many organisations. The decision that needed making was narrow. Pick a primary platform for durable team conversation and be explicit about it. Where a specialist tool stays, define what it is for and what belongs in the bundled platform — by team, by function or by data type, but written down. Turn off what you are not using, because an enabled platform accumulates channels, files, guests and compliance obligations whether or not anyone decided to adopt it. And critically: separate the meetings decision from the chat decision. A large share of the value organisations got from Teams in this period came from consolidating conferencing and eventually voice, not from chat. Several companies ran Teams for meetings and kept a specialist platform for team conversation for years, and that was a defensible answer rather than an indecisive one.
Practical Guidance for Enterprise Collaboration Strategy
- Decide the primary platform explicitly, even when one arrived for free. A product enabled by default is not a decision, and running two chat platforms is the most expensive outcome available.
- Separate the chat decision from the meetings and voice decision. Most of the bundled value is in conferencing consolidation; treating them as one question distorts both.
- Price the switching cost, not the licence. Migration of history, integrations and habits dwarfs subscription differences, and it grows with every month of dual running.
- Disable what you are not adopting. An unused but enabled platform still accumulates channels, files, external guests and retention obligations.
- Name the exceptions with owners and a review date. Specialist tools that stay should have a stated scope; undocumented exceptions become permanent sprawl.
- Check what the bundle does not cover before assuming compliance is handled. Retention, legal hold, external sharing and residency for the new workload need configuring, not inheriting.
- Decide where the record of a decision lives. Chat is not a record; without a documentation answer the platform choice solves nothing.
- Revisit vendor leverage at renewal, honestly. Consolidating chat, meetings, voice, identity and documents with one vendor is a defensible trade — made once, deliberately, with the concentration risk written down.
The Regional Angle
Teams' growth curve in the Gulf was steeper than the global figure suggests, and the reasons are specific to how the regional market buys software. Microsoft's enterprise position here is unusually strong. Government, semi-government, large family groups and the banking sector run predominantly on Microsoft stacks, and the enterprise agreement is frequently the single largest software relationship in the organisation, negotiated at group level and renewed as a package. When collaboration arrives inside that agreement, it does not compete — it is already bought. Regional IT functions are also typically leaner and more integrator-dependent than Western equivalents, which raises the value of a platform the incumbent partner already knows how to deploy and support. A specialist platform in this market has to win a budget line, an integrator skill set and a security review that the bundled option skips entirely. The conferencing and voice angle carried more weight here than elsewhere, for a specific historical reason. Consumer voice and video calling over the internet was restricted in the UAE for years, with enterprise collaboration platforms progressively permitted for licensed business use. That created a genuine functional gap and a strong preference for platforms whose enterprise voice and meeting capability was explicitly sanctioned — which shaped adoption patterns in ways that had nothing to do with product comparison. Organisations that had built around workarounds found a bundled, permitted enterprise platform unusually attractive. WhatsApp remains the incumbent for actual business communication, and this is where regional Teams deployments most often stall. A rollout here is not a migration from another sanctioned platform; it is an attempt to move client conversations, supplier coordination and internal approvals off personal messaging. Feature comparisons are irrelevant to that contest. The argument that works with finance and legal is governance — an approval given in WhatsApp leaves the company when the employee does, and given employment-linked residency, departures can be abrupt. The argument that works with users is a mobile experience good enough for the work, in the language they use. That last point is the most underestimated. A large share of the regional workforce is frontline rather than desk-based — retail, logistics, hospitality, construction, facilities — multilingual across Arabic, English, Hindi, Urdu, Malayalam, Tagalog, Bengali and Nepali, and frequently without a corporate email address. Licensing models built around knowledge workers do not fit that population, and a 200,000-organisation adoption statistic says nothing about whether the platform reached the majority of a regional company's employees. Most regional deployments in this period covered the office and left the operation on WhatsApp. One compliance note that grew in importance. Tenant location, archive residency and where search indexes live are now live questions under Saudi PDPL, the UAE federal framework and the separate DIFC and ADGM regimes. Regional cloud availability for collaboration workloads arrived later than for core infrastructure, so organisations with in-country hosting obligations spent several years with a residency gap in exactly the platform holding their day-to-day business communication.
The objection worth taking seriously
The strongest criticism is that bundling of this kind is a competition problem dressed as customer convenience, and that buyers who accepted it made a concentration decision without noticing. The substance of the concern is straightforward: a product included at no marginal cost inside a dominant productivity suite does not have to be as good as its competitors, and over time it does not have to be good at all. Competitors lose not on merit but on distribution, investment in the category declines, and the buyer ends up with identity, email, documents, chat, meetings, voice and compliance tooling all supplied by one vendor with full visibility of their switching cost at renewal. European and other regulators have examined the bundling of communication tools with productivity suites for exactly this reason, and the argument is not frivolous. The counter-argument is also real, and buyers should weigh it rather than adopt a position. Integration genuinely delivers value: one identity, one compliance boundary, one administration surface and one support relationship is materially cheaper and more secure to operate than five, particularly for organisations with small IT functions. The honest framing is that this is a trade — lower operating cost and better integration in exchange for higher concentration and weaker negotiating position later. Made deliberately, with the concentration written into the risk register and an occasional honest look at what exit would cost, it is a reasonable trade. Made by default, because a product appeared in a tenant, it is not a decision at all. And a narrower point about the number itself. Two hundred thousand organisations with Teams enabled was never two hundred thousand organisations using Teams, and the industry's habit of treating enablement metrics as adoption metrics distorted a lot of buying decisions in this period. The useful internal metric is not how many people have a licence but how many teams have moved their working conversation, and whether anyone can find a decision made six months ago. Most organisations could not answer either question then, and a surprising number still cannot.
Common Questions
Did Teams win on product quality?
Not in its first year. It won on distribution — bundled licensing, an existing compliance and identity footprint, and administrators who already knew the console. Product quality improved substantially afterwards, which consolidated the position rather than created it.
Should an organisation run two chat platforms?
Only with a written boundary — by team, function or data type — and an owner. Undeclared dual running fragments decisions across two searchable estates and is the most expensive outcome of the entire decision.
What is the most common rollout mistake?
Treating it as a technology deployment. Without decisions about channel structure, what belongs in chat versus documentation, and where the record of a decision lives, the platform reproduces the fragmentation it was meant to solve.
How does AI change the platform decision now?
It has raised the stakes on consolidation and made the concentration question sharper at the same time. Assistants answer from what they can reach, so an organisation whose conversations, documents and decisions sit in one governed estate gets materially better results than one split across platforms — which strengthens the bundled option considerably, since the suite vendor can index everything. Three cautions follow. AI capability now differs by tenant region, and in-country or sovereign hosting arrangements have historically lagged on feature availability, so organisations with residency obligations should ask for current availability rather than roadmap language. Unmanaged archives become newly consequential, because a channel nobody has read since 2018 can surface a stale decision with full confidence once something indexes it. And the concentration trade tightens: an assistant trained on and embedded in one vendor's estate, with embeddings and retrieval indexes that are not portable, raises switching cost in a way chat history never did. Whatever platform you choose, ask what leaves with you if you go.
Enterprise Collaboration Strategy — decide the primary platform deliberately, split the chat and meetings questions, and write the concentration trade down.