Skype for Business Online’s retirement date has passed. Some tenants are quiet. Others are living the week-after: residual meetings, confused devices, hybrid edges that still assume Online, and executives who “only now” found a boardroom that never moved. This post is field notes from closing the program properly — not celebrating a calendar checkbox.
What still breaks after the date
- Calendar items with Skype join links that never converted
- Room systems on abandoned account modes
- Contact center or SBC configs half-cut
- Clients reinstalled from old packages
- Hybrid on-prem SfB expecting Online peers that no longer behave
Inventory admin center recommendations and call detail for failures. Treat residuals as Sev-2 until empty.
Hybrid on-prem is not a time machine
Skype for Business Server on-premises can still exist. It does not restore Online. If your long-term plan is Teams-only with on-prem voice edges, document that architecture. If on-prem SfB is a comfort blanket with no funding, schedule its end too.
Rooms and devices punch list
Every room that hosted a failed meeting in the last two weeks gets an owner and a fix date. “We’ll get to rooms in Q4” is how Q4 becomes another incident cluster.
Soft skills
Send a short company note: SfB Online is retired, Teams is the path, here’s the help link, here’s how to fix a stuck meeting. Silence reads as incompetence even when engineers are fixing SBCs overnight.
Metrics for “closed”
- Zero user-facing SfB Online dependency in monitoring
- Room fleet on supported Teams modes
- Voice critical path green for two weeks
- Exception list signed by business for any remaining on-prem-only scenarios
Triage board we run for two weeks post-retirement
Columns: meetings, rooms, voice, hybrid, clients, “unknown.” Every ticket lands in a column with an owner and age. Anything older than three days escalates to the business sponsor. Without a board, residuals hide in personal inboxes of senior engineers.
Hybrid configuration review
Re-read hybrid DNS, sharing, and federation settings after Online retirement. Remove dead dependencies. Confirm on-prem SfB Server (if any) has a funded roadmap rather than accidental permanence.
Contact center and analog
These are where “we migrated” claims go to die. Joint war rooms with telephony vendors beat email threads. Capture call failure traces; do not argue from opinions.
Executive briefing template
One page: residual risk count, rooms fixed vs remaining, voice open items, decision needed. Executives can unblock vendors and budget; they cannot debug SIP trunks personally — give them decisions, not packet captures.
Closing criteria revisited
“Date passed” is not closed. Closed means two quiet weeks on residual metrics and a signed exception list for anything still non-Teams by design.
Scenario walkthrough
Consider a mid-size organization with hybrid identity, mixed desktop delivery, and a mandate to reduce risk without stopping the business. Week one is inventory and sponsor alignment. Week two is a written target state with two options and explicit out-of-scope items. Weeks three and four are pilot build and measurement. Only then does broad change begin. Compressing that sequence into a single weekend is how outages are born.
Along the way, three conversations dominate: who owns identity decisions, who pays for platform capacity, and what residual risk leadership accepts in writing. When those conversations are avoided, engineers improvise under pressure and the organization inherits accidental architecture.
We keep a living risk register with severity, mitigation, residual risk, and owner. The register is reviewed in the same meeting as the delivery burn-down. Risks that never move owners are the ones that become incidents.
If you're facing this
If retirement week left you with a trail of broken rooms and meetings, run a residual burn-down with executive visibility. We help close SfB Online leftovers and stabilize Teams voice/rooms — bring ticket themes from the last fourteen days.