

Thanks to the ubiquity of smartphones, teams of employees can more easily communicate with each other, thanks to modern messaging apps like Skype and Slack.Moving conferencing and meetings back to the cloud, via Teams, may have licensing, networking, and calling/DID/toll-free cost implications. Costs - Many organizations saved hundreds of thousands or even millions of dollars by moving from a hosted conferencing provider to on-premises conferencing with Skype for Business.Evaluate and understand the implications of any network changes required to optimize Teams voice and meetings. This makes sense for new deployments but is likely different than the “hub and spoke” network model large organizations use for on-premises Skype for Business deployments. Network - Microsoft recommends local office breakouts for Internet connections to optimize Teams real-time communications.Note that you currently cannot use existing conference dial-in numbers via Direct Routing with Teams conferencing. Direct Routing enables you to use existing SIP trunks or T1/E1 connections with Teams.
#TEAMS VS SKYPE FOR BUSINESS SOFTWARE#
Some existing session border controllers/gateways may not be supported or may require software upgrades. On-premises PSTN connectivity - Teams introduces a new model called Direct Routing.Depending on how the interoperability scenarios work within your organization, you may choose to limit the “in between” period in your transition to Teams. If you’re going to have large groups of users on each platform for a long period of time, you should pilot the interoperability capabilities and mitigate any issues through strong communications, change management, and training. Interoperability with Skype for Business - Teams and Skype for Business work together but not seamlessly and not perfectly.While an over-simplification, presently call queue and attendant capabilities in Teams lack some of the features available in Skype for Business (which also leveraged some capabilities of Exchange Unified Messaging). Similarly, automated attendant/IVR capabilities in Teams are based on new code. Call queues and automated attendants - Microsoft has rebuilt the call queue service for Teams, which in Skype for Business is called response groups.Phone device support - Microsoft has introduced a new line of certified Teams IP phones, but it also has said that basic functionalities will continue to work on Skype for Business Online-certified devices when a user switches to Teams.Teams also can provide a transcription for meeting audio and can blur a presenter’s video background. On the positive side, Teams records meetings and stores these recordings in the cloud, unlike Skype for Business, which stores meeting recordings on local PCs. In another difference, while Teams does allow you to share your desktop, a specific application window, or PowerPoint slides during a meeting, you can’t annotate shared PowerPoint slides in Teams like you can in Skype for Business. These, however, are one-to-many rather than interactive meetings, and only allow attendees to join via Web browsers. This is not to be confused with broadcast meetings, now called Live Events in Teams, which enables the hosting of meetings for up to 10,000 attendees. While you could set up a dedicated Skype for Business pool to host interactive meetings with up 1,000 users, meeting size in Teams is currently limited to 250 users. Meetings - While Teams and Skype for Business meetings are similar, they have important differences.(There is some indication that this will improve with future updates.) Teams guest access at present is cumbersome to manage and creates a disjointed user experience. In several cases, federation between customers and suppliers was specifically noted as significantly improving the business relationship and overall customer service. Federation with external organizations - the OCS/Lync/Skype for Business federation model was very easy to implement and manage, and provided a tremendous improvement in the ability to communicate and hold meetings with users from organizations also using Skype for Business.Contact center and other third-party integration - organizations that have deployed contact center applications integrated with Skype for Business or have invested in third-party reporting or management tools should be aware that few if any of the existing tools work with Teams.Teams multi-geo capabilities don’t currently provide the same level of control. Data residency - larger organizations may have created multiple Skype for Business pools located in different countries to address regulatory requirements related to where call detail records, IM conversations, uploaded content, and meeting recordings are stored.
