Skype Web SDK
Applies to: Skype for Business 2015, Skype for Business Online
The Skype Web SDK documentation consists of the following sections:
Skype for Business Online Retirement
Skype for Business (SfB) Online retired in July 2021. The retirement of SfB Online reduced the market of Skype tenants for the SfB Web SDK, and many SfB organizations are migrating to Teams.
Azure Communication Services (ACS) is a cloud-based communications service that lets you add voice, video, chat, and telephony to your apps. ACS applications today can interoperate with Teams on behalf of an anonymous user. The ability to interact with Teams on behalf of M365 users is in preview, and we encourage implementers of the SfB Web SDK to transition to Azure Communication Services and Microsoft Graph APIs. Microsoft Graph APIs control behavior specifically in the M365 ecosystems, such as presence. It also provides chat support.
The table below maps SfB Web SDK sub-systems to Graph and ACS capabilities.
|SfB SDK System||Description||Alternative|
|Presence||Use presence information to help users decide whether and how they should person other users.||Graph Presence APIs|
|Local user||Use the mePerson object to represent the currently signed-in user.||Graph User APIs|
|Conversations||Use conversation services to determine the ways for communication between persons.||ACS Calling SDK for voice/video and Graph for chat|
|Listening for and generating presence events||Use events to get a person's current presence.||Graph Presence APIs|
|Persons||Use person objects to represent individual users.||Graph User APIs|
|Devices||Select Cameras, Microphones, and Speakers to use for audio and video conversations.||ACS Calling SDK|
Azure Communication Service SDKs are designed with a substantially different API model than SfB Web, and we do not host the SDK on a content delivery network (CDN). Your web application hosts the SDK, and you have the choice of using one of several SDKs listed below. The core Calling and Chat SDKs have essentially no GUI and allow for robust customization of the end-user experience. But for most SfB Web SDK implementations, using the open-source composites is recommended to reduce the amount of UI development required by replacing SfB.
|SDK||Implementation Complexity||Customization Ability||Calling||Chat||Interact on behalf of a M365/Teams users|
|Base Components||Medium||Medium||✔||✔||In Preview|
|Open-Source Composite||Low||Low||✔||✔||In Preview|
To use Graph and ACS SDKs as an SfB Web SDK replacement, you will leverage these features:
|Graph||Log-in a user to M365||Available Today|
|Graph||Set presence||Available Today|
|Graph||Get Presence||Available Today|
|Graph||Send and receive chat messages||Available Today|
|Azure||Create an ACS token for an M365 user||In Preview|
|Azure||M365 user can call a user in Teams||In Preview|
|Azure||M365 user can join a Teams meeting, interface with the video, audio, and chat channels||In Preview|
|Azure||M365 user can initiate PSTN calls from Teams-allocated phone numbers||In Preview|
|Azure||M365 user can receive PSTN calls from Teams-allocated phone numbers||In Preview|