/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

← → days · ↑ ↓ browse · Enter similar · o open

Microsoft says Skype for Business Online will be “retired” on July 31, 2021; Skype consumer users will be able to communicate with Teams users starting Q1 2020

Mary Jo Foley / ZDNet :

ZDNet Mary Jo Foley

Context & Ripple Effects

This is the execution step for a decision Microsoft telegraphed in September 2017, when it announced Teams would replace Skype for Business and put more pressure on Slack. The retirement date turns that strategic statement into a hard deadline, while the Q1 2020 interoperability window shows Microsoft bridging — not merging — its consumer Skype base with Teams ahead of any fuller consolidation.

It also fits an established pruning pattern: Microsoft had already retired Skype Qik in 2016 and folded Skype's Windows touch app into a single desktop client in 2015. Each move trims a peripheral surface so engineering and messaging concentrate on fewer properties.

First-order effects

  • Enterprise customers running Skype for Business Online get a fixed July 31, 2021 cutoff, forcing them onto Teams migration paths rather than leaving them on a maintained legacy service.
  • From Q1 2020, Skype consumers can reach Teams users directly, which removes the interoperability barrier that previously made switching off Skype costly for mixed consumer-business contact lists.

Second-order effects

  • Slack faces a competitor whose business-messaging product now inherits an entrenched enterprise installed base by default, sharpening the pressure Microsoft set up when it positioned Teams against Slack in 2017.
  • Partners and ISVs built around Skype for Business Online APIs must rework integrations toward Teams, shifting the third-party ecosystem's development effort to Microsoft's chosen platform.

Third-order effects

  • The pattern points to full brand consolidation: once the enterprise product is retired and interop normalizes Teams for consumers, the remaining consumer Skype property becomes redundant — the endpoint Microsoft later reached by [[a:882963|shutting down Skype entirely and directing users to migrate contacts and chat data to Teams]].
  • For buyers, communications purchasing shifts from picking among discrete chat, voice, and meeting tools to adopting a single bundled platform, raising switching costs and concentrating vendor power in suites like Teams.

The trend: Microsoft is methodically collapsing its fragmented Skype properties into Teams, using deadlines and interoperability rather than a single cutover to migrate both enterprise and consumer users.