July 31, 2021 is no longer a planning horizon — it is about ninety days away. Skype for Business Online retires. If you still have users, meetings, or voice dependencies on SfB Online, this is the final checklist: stragglers, rooms, contact centers, assisted upgrade paths, and what happens if you do nothing.
Inventory that must be true this week
- Users not yet Teams Only (or equivalent destination)
- Meetings still scheduled as Skype
- Response groups / call queues still on Skype paths
- Room systems on Skype Room Systems without Teams upgrade plan
- Contact center integrations and SBCs still pointing at Skype Online
- Hybrid on-prem SfB Server dependencies that assumed Online forever
If any row is “unknown,” that is the first work item.
Meeting and chat
Move organizers and defaults to Teams. Clean residual Skype meeting links. Train the last Islands holdouts. Dual clients increase confusion — pick a date and communicate hard.
Voice is still the long pole
Number porting, Direct Routing, Calling Plans, analog devices, common area phones — none of these shrink because the calendar is short. Escalate carrier timelines now. Parallel-run where possible; do not invent a weekend port of the entire DID range without a backout.
Rooms and devices
Boardrooms that still only understand Skype meetings will become executive incidents in August. Firmware, accounts, and meeting modes need owners. A single “Teams Rooms” pilot in 2020 that never expanded is now a crisis project.
Contact centers
If your CCaaS or on-prem ACD still integrates to Skype Online, engage the vendor this week. These are multi-party projects. “IT will switch a DNS record” is not a plan.
Assisted upgrade and Microsoft tools
Use whatever tenant admin tools and upgrade advisories Microsoft provides for your mode as of today — but tools do not replace voice architecture. Track Microsoft 365 admin center recommendations as a punch list, not a complete program.
If you do nothing
Users lose SfB Online service capability after retirement. Meetings break. Some hybrid scenarios degrade. You will migrate under incident conditions with worse options. Doing nothing is a decision — write it for leadership if they choose it.
Minimum 90-day plan
Days 1–14: freeze inventory, executive decision on Teams Only date, voice critical path chart
Days 15–45: move remaining users/meetings; room upgrades; carrier orders
Days 46–75: contact center and analog edge cases; load test
Days 76–90: freeze changes, war room ready, residual exception list signed
Extended practice notes (2021)
The remaining gap between a short checklist and a usable field note is usually scenario detail. In practice, the same engagement type described above still requires explicit answers to: what is in scope this quarter, what is deferred with a date, who can halt a wave, and how success is measured in production — not in a lab.
We document those answers before the first production change. When stakeholders disagree, the disagreement is resolved in writing, not on the bridge at cutover. That habit is independent of whether the workload is mail, identity, virtualization, desktop delivery, or security hardening.
Repeatable detail also includes communication: who tells users what changes, when the freeze starts, where status is posted, and how exceptions are requested. Technical excellence without communication still produces an outage from the user's point of view.
If you're facing this
If Skype for Business Online still appears in your tenant reports with ninety days left, escalate to a dedicated program now. We help close SfB Online residual risk and Teams voice/rooms cutovers — bring user mode reports and SBC/room inventories.