Microsoft has set the clock: Skype for Business Online retires July 31, 2021. If you still treat Teams as the chat side project and Skype as "real meetings," that clock is now a program, not a preference. Two years sounds long. For enterprises with voice, contact centers, room systems, and regulated recording, it is barely enough.
We have lived through multi-tenant Skype for Business 2015, hybrid voice conversations, and Teams rollouts that went from pilot to default in uncomfortable bursts. This post is the runway plan we recommend starting in summer 2019 — coexistence modes decoded, meeting-first tactics, and why voice will dominate the critical path.
What "retirement" means operationally
Skype for Business Online as a service ends. Users need a landing: Teams Only (or a documented exception path). On-premises Skype for Business Server can still exist in hybrid stories, but the Online service sunset forces the identity and client default questions even for hybrid shops.
If your tenant is already Teams-first, congratulations — you still need to clear residual Skype Online meetings, client defaults, and edge cases. If your tenant is Islands mode with no plan, start now.
Coexistence modes without the hand-waving
Microsoft's modes (Islands, Skype Meeting with Teams Collaboration, Teams Only, etc.) are not branding; they change who schedules which meeting type and how clients behave.
Practical guidance we give:
- Islands is fine for early collaboration pilots. It is a terrible forever state — split meetings, user confusion, double presence.
- Meeting-first migration — move meetings to Teams while chat/call habits catch up — often reduces political heat versus flipping calling first.
- Teams Only is the destination for Online retirement. Plan the date; do not hope for another extension as strategy.
Pilot with a business unit that lives in meetings more than in phone queues. Contact centers and analog devices are last for a reason.
The long pole: voice and rooms
Chat migration is change management. Voice is architecture:
- Calling Plans vs Direct Routing vs existing SBC estates
- Number porting timelines (carriers do not care about your Teams project plan)
- Analog and common-area phones
- Call queues, auto attendants, contact center platforms that still point at Skype
- Room systems (Skype Room Systems vs Teams Rooms roadmaps)
- Recording and compliance for regulated industries
Start voice discovery this year even if user chat moves next year. Porting and SBC work will own the calendar.
Identity and network (again)
Teams is ruthless about network path quality. Split-tunnel or optimized paths for Office 365, DNS, and proxy bypass for media — revisit the same guidance you ignored when "Skype was fine on the VPN." It will not be fine at company-wide Teams meeting scale.
Identity: modern auth, Conditional Access that does not break meeting join for guests, and a clear external access story. Meeting explosion without guest governance is a security incident with a calendar invite.
Change management that is not a poster
- Default client and meeting links that do not require tribal knowledge
- Training for "where did my PSTN button go"
- Executive meetings move early so the rest of the firm follows power, not policy PDFs
- Helpdesk scripts for the first thirty days after each mode change
A simple two-year skeleton
2019 H2: inventory (Online vs on-prem, voice, rooms, recording); pick target mode path; network assessment.
2020: meeting-first broad move; pilot calling; room strategy; porting project kickoff.
2021 H1: Teams Only for remaining Online users; decommission Skype Online dependencies; load test.
2021-07-31: no heroics — only leftovers with executive-accepted risk.
Hybrid Skype Server estates
If you still run Skype for Business Server on-premises with Online hybrid, the Online retirement still forces Teams planning for cloud users and for the eventual on-prem endgame Microsoft has been signaling for years. Do not assume on-prem Skype Server is a forever escape hatch. Use the Online deadline to fund the discovery you postponed: dial plans, analog devices, response groups, and carrier contracts.
Governance before viral adoption
When meetings move to Teams, every user becomes a meeting organizer with external access questions. Define:
- Who can create teams and channels (or how you clean sprawl)
- External access and guest access defaults
- Naming standards
- Retention aligned with legal hold reality
We would rather ship slightly annoying guardrails in 2019 than spend 2021 deleting ten thousand abandoned teams after a security review.
Metrics that prove the runway is working
- Percent of meetings created as Teams vs Skype per week
- Helpdesk volume by category after each mode change
- Network quality scores for Teams media
- Voice pilot call success rate
- Room systems migrated vs remaining
Steering committees understand burn-down charts. Give them some.
Common coexistence mistakes
- Leaving Islands mode for a year because people seem fine
- Moving Teams Only without training organizers on lobby and recording defaults
- Ignoring room systems until executives cannot join from the boardroom
- Assuming Direct Routing is a two-week add-on
- No network remediation budget while promising company-wide video quality
Fix the mistakes in planning documents before they become 2021 fire drills.
Training that scales
One webinar is not adoption. We prefer short role-based guides: organizers, reception/lobby managers, executives, helpdesk. Pair with floor walkers for the first week after mode changes in large campuses. Measure meeting creation source weekly so you know if behavior changed.
If you're facing this
If your plan for Skype for Business Online retirement is "we'll switch everyone to Teams next summer," you are late in spirit even if the calendar says 2021. We plan Teams coexistence and voice migrations alongside Office 365 estates — bring your mode, your SBC inventory, and your room count.