Microsoft's move to fold Lync into the Skype brand and then roll that product into an enterprise-ready client called
Skype for Business was never just cosmetic — it was a strategic effort to marry Skype's broad consumer familiarity with Lync's enterprise controls — and the company's early rollout tactics, including a mix of in-person workshops, live webcasts, and Office 365 Readiness resources, made clear that this was a migration that would require real-world training and operational planning across IT teams worldwide. ([blogs.microsoft.coosoft.com/blog/2014/11/11/skype-business-brings-best-skype-lync-due-2015/)
Background
Microsoft announced the plan to rename and re-skin Lync as
Skype for Business in November 2014, pitching it as “bringing the best of Skype and the best of Lync” together into a single communications platform for enterprises. That message emphasized user familiarity (consumer Skype) plus enterprise-grade security, compliance, and manageability (Lync).
The client and platform transition rolled into product updates in early 2015: an April 14, 2015 update for Lync 2013 delivered the Skype for Business client to Office customers, and Microsoft documented how the update changed the client experience and interoperability considerations. Administrators were told there was no new hardware requirement for customers updating Lync Server 2013 to Skype for Business Server; Office 365 customers received the client automatically as part of the service updates.
At the same time, Microsoft signaled the longer arc of its communications strategy: over the next few years,
Teams would emerge as the long-term strategic client for workplace collaboration, eventually superseding Skype for Business Online in the Office 365 cloud. That transition created an extra planning consideration for organizations adopting Skype for Business in 2015–2018: was this a one-off UI change, or a step on a migration path toward a different platform?
What Microsoft announced — and what it meant for IT
The announcement in plain terms
Microsoft’s public messaging framed Skype for Business as a consolidation: the familiar Skype consumer interface and reach combined with Lync’s enterprise controls. The technical reality was more conservatively described — in many ways,
Skype for Business was Lync rebranded with UI and service-layer enhancements rather than a full architectural reinvention. For operations teams, that meant the
concepts they already knew (servers, policies, mediation, federation, client versions, and PowerShell management) remained relevant even as the client experience changed.
Release mechanics and upgrade path
Microsoft distributed the new client through an update channel: Lync 2013 installs were updated to the Skype for Business client via the April 2015 update (KB2889923), and Office 365 tenants received the new experience through the cloud update pipeline. Microsoft’s guidance noted that administrators could retain the Lync UI if required, but cloud tenants would be automatically offered the Skype for Business client during the rollout window. That meant admins needed to plan user communications, pilot groups, and rollback options ahead of broad rollouts.
Training, readiness, and the delivery model Microsoft used
Microsoft’s rollout included a deliberate learning and readiness program: instructor-led in-person events in selected global cities, live webcasts for remote attendees, and Office 365 readiness pages and calendars where on-demand content and training schedules were published. Tnized two realities — first, that effective UC (unified communications) adoption depends on both technical configuration and end-user behavior; second, that enterprises span time zones and locations, so a hybrid delivery model (in-person + online) was necessary.
- In-person workshops gave administrators and power users hands-on time with Skype for Business features like conferencing, PSTN integration, and security/policy controls.
- Live webcasts expanded reach and provided immediate, accessible context for teams that could not attend Readiness and partner readiness calendars aggregated schedules, on-demand sessions, and implementation labs to help partners and IT departments plan deployments.
Note: reporting at the time highlighted specific in-person event listings in a handful of cities. Those regional details were useful for planners but, unless confirmed by official Microsoft event pages, should be treated as paint-on-the-wall scheduling details rather than hard contractual commitments from Microsoft. When planning, IT teams should always verify local event availability against official readiness calendars.
The readiness calendar and event-driven model, however, were very real and active resources for administrators.
Technical implications for enterprises
Core capabilities carried forward from Lync
Skype for Business retained the Lync architecture foundations: presence and IM, enterprise-grade conferencing, PSTN integration options (via Cloud PBX or on-premises SIP/PBX integrations), federation capabilities with consumer Skype, and the familiar server and client management model that used PowerShell and administrative consoles. The rebrand focused on the user experience (icons, presence indicators, and contact discovery) but left back-end capabilities largely consistent with Lync Server and Lync Online.
Federation and interoperability with consumer Skype
One of Microsoft’s strategic selling points was reach: enterprises could connect more easily to the hundreds of millions of Skype consumer accounts. That interoperability required careful policy design — admins had to define federation rules, guest access policies, and contact-level controls — because opening IM or federation pathways without governance can create compliance, audit, and data-loss exposure.
Hybrid deployments and on-premises considerations
Microsoft continued to support on-premises deployments (Skype for Business Server), and also documented hybrid guidance for organizations that wanted a mix of cloud and on-premises users. Hybrid deployments introduced additional operational complexity: directory synchronization, hybrid voice routing, meeting migration strategies, and split policy management across on-premises and cloud. Microsoft’s guidance emphasized planning steps and warned that some content (for example, scheduled meetings) may require rework when accounts are migrated.
Management, client UI, and admin tooling changes
Although admins could allow users to retain the Lync UI temporarily, Microsoft exposed a path for admins to switch between the Lync and Skype for Business interfaces (scripts and guidance were circulated to help with the switch). That support highlighted the practical need for reversible change controls in enterprise rollouts: pilot, measure, revert if needed, and then proceed. Forum threads and readiness notes from partners confirmed admins were acripts and tools to manage the conversion at scale.
Why Microsoft invested in training — benefits and the business case
- Improved user adoption: UC tool rollouts frequently fail because users aren’t confident; instructor-led sessions reduce friction and accelerate adoption.
- Reduced helpdesk load: hands-on workshops for power users and admins preemptively address common misconfigurations and usability questions.
- Faster, safer migrations: readiness training includes migration tools, checklists, and hands-on labs that reduce post-deployment outages and meeting disruptions.
- Standardized governance: workshops help embed compliance and policy best practices into deployment plans, reducing risk from poor federation or external sharing settings.
These are not abstract benefits: partners and enterprise IT teams that participated in Microsoft readiness programs consistently reported faster onboarding and fewer surprise support calls. The readiness calendar and on-demand labs were explicitly designed to make the learning process repeatable and auditable.
Critical analysis — strengths and strategic value
Strength: Brand recognition and user familiarity
Rebranding Lync into Skype for Business leveraged the strong consumer familiarity of
Skype. That lowered the perceived learning curve for end users and encouraged faster adoption among organizations that already saw Skype as the default for video calls. Microsoft’s messaging here was savvy: use the consumer brand to make the enterpriachable without sacrificing enterprise controls.
Strength: Enterprise feature parity and security posture
Because Skype for Business preserved Lync’s administrative and compliance features, organizations didn’t have to sacrifice legal hold, auditing, or management controls in exchange for a friendlier UI. For enterprises with regulatory constraints, that continuity was essential. The product provided a path to modernize user experience while keeping the security and policy foundations intact.
Strength: Training + hybrid delivery model
Microsoft’s mix of
in-person workshops,
live webcasts, and
on-demand readiness resources represented a pragmatic and modern training approach. The model acknowledged that technology change is both technical and behavioral, and it offered multiple learning modalities to reach different audiences. The presence of instructor-led labs and readiness calendars materially helped partner ecosystems and large IT teams manage complex migrations.
Risks, weaknesses, and things that went wrong or needed extra attention
Risk: Messaging and product-line confusion
Although the rebrand made UX sense, it created an immediate naming confusion: consumer Skype, Skype for Business (formerly Lync), Skype for Business Server (on-premises), and later Microsoft Teams. For IT planners, that multiplicity required extra diligence when mapping features to licensing and long-term strategy. The confusion was not merely cosmetic; it complicated procurement, training curricula, and migration timelines.
Risk: Midstream strategic shift (Teams)
Microsoft’s later decision to position
Teams as the primary Office 365 communications client (announced publicly in 2017) meant organizations had to account for an evolving roadmap. Teams absorbed many of Skype for Business’s capabilities and became the strategic dist collaboration. That pivot created a planning challenge: invest in training and rollouts for Skype for Business now, knowing Teams was the future, or accelerate Teams migration planning immediately. For many, the practical solution was hybrid: use Skype for Business where on-premises or specific voice integrations demanded it, and plan Teams migration on a measured timeline.
Risk: Migration complexity and user disruption
Even minor client UI changes can cause disproportionate helpdesk demand. Calendar invites, scheduled meetings, PSTN conferencing dial-in numbers, and third-party integrations require testing. Microsoft documented thaexample, scheduled meetings) might not migrate cleanly between on-premises and cloud contexts, meaning organizations needed to build testing and re-scheduling into their cutover plans.
Risk: Federated reach vs. security and compliance
Federation with consumer Skype provided reach but also created potential compliance exposures. Organizations operating in regulated industries had to explicitly evaluate whether external federation aligned with their data retention, eDiscovery, and audit requirements. The readiness workshops addressed policy design — but the onus remained with the enterprise to define acceptable federation surfaces and logging requirements.
Practical checklist and recommended steps for IT teams planning a Skype for Business rollout (or similar migration)
- Inventory and mapping
- Map existing Lync/UC configurations, voice routing, PSTN integrations, and third-party connectors.
- Identify admin roles and owner contacts for each integration.
- Pilot and compatibility testing
- Select representative pilot groups (different geographies, job functions, and voice usage patterns).
- Validate client behavior, meeting migration, calendar integrity, and federation scenarios.
- Training and readiness
- Book instructor-led sessions for administrators and power users; schedule webcasts for general users.
- Use Office 365 Readiness and partner readiness calendars to access labs and on-demand recordings.
- Policy and governance alignment
- Define federation rules, guest access policies, retention and eDiscovery settings, and meeting lobby controls.
- Enforce policy via PowerShell scripts and group policy where applicable.
- Communication and support
- Prepare user-facing documentation, quick-start guides, and short video walkthroughs that show new UI changes and meeting join flows.
- Staff the helpdesk for the first 2–4 weeks of broader rollouts with additional resources.
- Rollout, observation, and rollback plan
- Stagger rollouts by region or business unit.
- Maintain ability to revert UI changes for a cohort if critical issues arise.
- Future-proofing
- Keep an eye on Microsoft’s roadmap (Teams migration guidance and hybrid support lifecycles) and maintain contingency plans for moving to Teams if your organization decides to consolidate to the Microsoft Teams platform.
Real-world lessons from partner and community feedback
Community threads and partner discussions from the rollout era repeatedly emphasize two themes: (1) the need for hands-on, instructor-led sessions for administrators and support staff; and (2) the practical value of scripts and tooling to flip between UI experiences or update meeting invitations after service changes. Forums recorded IT pros sharing migration tools (for meeting updates and PSTN configuration), and readiness calendars helped partners coordinate instructor-led labs. These were not theoretical advantages—administrators used these resources to prevent thousands of avoidable helpdesk tickets during broad rollouts.
Long view: lifecycle, deprecation, and what happened next
Microsoft’s longer-term strategy shifted: Teams became the company’s centerpiece for cloud collaboration and communications. The company signaled in 2017 that Teams would evolve as the primary Office 365 communications client and, over the following years, Teams gained calling, meeting, and federation capabilities that overlapped with Skype for Business. For organizations planning in the 2015–2018 window, this created a necessary second layer of planning: short-term adoption of Skype for Business to modernize the UC experience, and a medium-term roadmap to evaluate Teams as the organizational collaboration platform.
Microsoft later announced migration and retirement timelines for Skype for Business Online, and partners documented operational guidance for moving tenants to Teams. These downstream decisions underscore a core lesson: enterprise communi connect short-term operational readiness with multi-year platform roadmaps so that training investments map to long-term platform strategy.
Final assessment — should organizations have invested in Skype for Business training in 2015?
From a pragmatic perspective, the answer is
yes, with conditions.
- Yes, because the UI updates and interoperability features reduced friction and delivered immediate productivity gains for users who were previously on legacy Lync clients. Training reduced support costs and helped admins enforce consistent policies across a distributed user base. Microsoft’s readiness resources and partner-led instructor sessions were designed to make these gains achievable at scale.
- With conditions: organizations needed to pair tactical training with strategic planning. Because Microsoft’s product direction later prioritized Teams for cloud-first customers, organizations should not have treated Skype for Business training as a permanent end-state without a Teams migration plan. Instead, training should have emphasized transferable collaboration concepts (meeting hygiene, federation governance, PSTN integration patterns) that carry forward to Teams and other UC platforms.
Recommendations for IT leaders designing a UC readiness program today
- Design training for transferability: teach concepts, not only UI flows. Cover meeting security, compliance, and PSTN integration patterns that apply beyond any single client.
- Use blended delivery: combine instructor-led, hands-on labs with recorded webcasts so geographically distributed teams can access the same material on demand. Microsoft’s readiness calendar model remains a good template for modern programs.
- Pilot aggressively: start with pilot groups that mirror the complexity of your environment (on-prem voice, hybrid mailboxes, cross-company meeting loads) and validate end-to-end flows.
- Maintain governance disciplines: federation, archiving, and eDiscovery require explicit configuration when you open IM and calling surfaces to external networks.
- Prepare for platform evolution: keep lifecycle and roadmap planning as part of your training budget — expect vendor roadmaps to shift and ensure your training investment is resilient to those changes.
Conclusion
Microsoft’s Skype for Business era delivered a pragmatic combination: a friendlier, Skype-styled user experience while preserving Lync’s enterprise controls. The company’s rollout strategy — mixing in-person workshops, live webcasts, and Office 365 readiness tooling — was a recognition that unified communications are as much about people and process as they are about protocol stacks and servers. For IT teams, the core takeaway is simple: invest in training that reduces operational risk today, but design that training so the knowledge remains useful even as platforms evolve. Ready organizations treated Microsoft’s readiness programs as tactical accelerators and paired them with strategic roadmaps — and those were the teams that minimized disruption and came out ahead when the next platform wave arrived.
Source: onmsft.com
Skype for business training will be available in person and online – OnMSFT