Just last Friday Microsoft announced in their blog page https://techcommunity.microsoft.com/t5/Microsoft-Teams-Blog/Microsoft-Teams-is-now-a-complete-meeting-and-calling-solution/ba-p/236042 that MS Teams now has all the meetings and calling functionality of Skype for Business Online. The article describes how MSTeams is now a complete meeting and calling solution and a Teams Conferencing Gateway, which allows you to use existing Skype for Business certified SIP-based phones with Teams; and USB HID Support for Teams, enabling customers to answer, end calls and control mute and volume using USB peripherals. In addition, cloud video interop services to support Teams meetings with existing VTC systems are underway with offerings from Pexip, Polycom, and Blue Jeans to be generally available later this calendar year. Of course this does not mean that the roadmap has been competed as there are additional features coming in Q4 of this year as can be seen in the MS Roadmap available here: http://aka.ms/skype2teamsroadmap. The purpose of this blog post is to serve as an add-on to go into detail the configuration of the O365 tenant to allow for calls to work between MSTeams and Skype for Business users.
In a previous blog post I wrote about provisioning Exchange mailbox accounts and Skype for Business meeting rooms accounts for Skype Room Devices such as the SurfaceHub and the Skype Room Systems V2 that is already available today. During my initial setup of a Polycom MSR Skype Room System V2 device, even after following the steps in the previous blog post, the device can register and sign-in successfully to a Skype meeting room account that is homed online on Office365. However, using an account that is homed on-premise, I could not get the device to sign in successfully. This blog posts walks through the error encountered and how I managed to resolve the issue