Complete Skype for Business Integration into Teams
Honestly, this is a tall order due to the fact that Teams was not launched this way in the first place, but my real world experience, and feedback from the field, is that having Skype-for-Business-like functions in Teams (chat/Presence/etc) be separate from Skype for Business itself is not only confusing for many users, but inhibits adoption. Users want to consolidate the number of apps they use, not increase it. I personally find this to be true.
Teams is an incredible tool with so much potential, but living and breathing in Skype for Business, like so many of us do, Teams isn't a completely organic feel due to the disparity of chat identities. If I could go into Teams, manage my projects/files/OneNote, engage in Chats, see and join my meetings, engage in Audio/Video calls (I can do all this now), AND THEN also place and receive all my PSTN calls, Teams would be my new permanent application for doing all this, and email would start to fade into the background.
This is the direction I truly hope to see things go. Teams' potential is incredible, but realizing its full potential, in my humble opinion, relies on complete Skype for Business integration.
This topic will be closed out as completed since the vast majority of the S4B convergence has already released to the public.
If you have any specific requests, please open a new topic or vote for an existing topic that more specifically targets your wish.
The team is aware of the issue of using Teams will force you from using S4B.
I’ve opened a topic specifically for that based on the feedback below – vote for support of this request at https://microsoftteams.uservoice.com/forums/555103/suggestions/35124451
As for notification issues and being able to view multiple conversations, there are topics for allowing different types of notifications – http://microsoftteams.uservoice.com/forums/555103/suggestions/16925461 and a topic for multi-window for chats and more – https://microsoftteams.uservoice.com/forums/555103/suggestions/16926739
The ability to send audio or video messages can be voted for at – https://microsoftteams.uservoice.com/forums/555103/suggestions/32372014
Thank you for all the feedback and suggestions.
127 commentsComments are closed
The roadmap doesn't include all Skype for Business functionality. The notifications, status options and visibility into multiple conversations at once are completely omitted, and those are features we relied on daily.
Stephen Bacchus commented
I'm hoping a Microsoft rep sees this and takes it seriously.
Dear Admins, please get on the same page as your design teams and support staff, they're giving users contradicting information.
I just had a conversation with Microsoft Support about the ability for a Skype user to talk to a Teams user...basically at this time there is no such thing as interoperability despite their documentation regarding coexistence modes.
The very minute a user even tries Teams just once...they break the ability to use Skype to talk to you if you're using Teams. Apparently it's been in this broken state for months and is "by design."
Here's the quote from the rep, "Teams is designed to only send messages to Skype for Business if the recipient has NEVER used Teams. Once the recipient like USER B has signed into Teams (even just once), all messages from other Teams user like USER A, would ONLY be sent to Teams."
The support rep even admitted Microsoft's documentation does not match this current broken system. There is no actual migration path from Skype to Teams, there is no actual interoperability. If you have a 1,000 users and just one tried out Teams then you have to decide either everyone uses Skype or everyone uses Teams, nothing in between.
It's crazy but the truth is you can safely disregard everything in this article: https://docs.microsoft.com/en-us/microsoftteams/teams-and-skypeforbusiness-coexistence-and-interoperability
I'm desperately trying to keep Slack at bay in my organization, but this just gives Slack users more ammunition.
Microsoft, please get it together and provide us true interoperability that matches up with your documentation.
One step forward two steps back? The contact list feature (and import of contacts from S4B) is now here, that's good even if it is a bit lacking:
However when I now try to turn of S4B I no longer receive messages at all (previously I received them but history was not saved). We have tried both modes available in the new admin center (and waited 24h after changing the mode).
I was also saddened to hear that Teams will not be able to do everything S4B is able to do (communicate with normal Skype) https://microsoftteams.uservoice.com/forums/555103-public/suggestions/16958347-skype-integration-consumer-federation
Mike Turner commented
Does this particular UserVoice item include the ability to leave voice clip messages for others in Chat, like how Skype works? My userbase has some heavy users of Voxer, and would LOVE to get them to start doing the same within Teams (if Teams would include the already-existing feature from Skype).
Jenn Carr commented
its middle of second quarter and we have had no updates on this. Can you give us anything?
Currently, the "availability" check circle next to the person's picture/icon is not synchronized with SFB. So if I'm talking to someone in Teams, but they're sharing their screen with some in SFB, it still shows that person as green/available in Teams, and I would only know not to message that person by first checking their availability in SFB.
Derp - why do you want SFB killed? We use it for all our internal and external voice communication and online meetings. We don't want or need all the Facebook like stuff that comes with Teams. SFB does exactly what we want. Please keep the products separate or at least provide skins that can expose just the functionality required and make it look and feel like products that our 5,000 users are already familiar with (moving from Lync to SFB was hard enough).
I'd rather see SfB totally killed, actually... but people want what they want :)
SfB contacts and interop between Teams and SfB is suppose to have been released a week ago
Giovannie Hernandez commented
Q1 CY2018 ended and I haven't seen any new releases since the 21st of March. Is the next release delayed? When is it scheduled for? Will it include this feature?
The roadmap states end of Q1 CY2018 - i.e. 9 days away. Is this still the plan?
Liana Johnson commented
Is there a timeline for this? I am not seeing it on the roadmap.
I think you should rather concentrate on destroying Skype for Business (alias Lync) totally from this planet, and focus on improving Teams instead.
I totally agree. Currently my company uses: Email, Skype For Business, Yammer and now Teams. Two tools, Email and Skype are plenty for me - this makes no sense. We need convergence of info/activity, not divergence.
[Deleted User] commented
Hopefully this won't mean the end of skype for business as the power consumption of teams makes it not suitable for use on portable devices.
Jamie Dewoody commented
Will the remote desktop functionality of SfB be integrated fully into Teams? Right now, desktop sharing in Teams is view only whereas we were looking to replace slow, free desktop sharing utilities like join.me with SfB but would be fine with Teams if that is the direction it is heading.
When will we get a product that we can use with PTSN calling so we can replace Skype For Business. This tool cannot exist side by side with Skype For Business...it either has to get robust enough to replace for Skype For Business...or its just the latest and greatest gee whiz shelfware we cannot use.
To provide support to my userbase (a mix of windows and Mac), realtime chat with project planning and interact with externals I now need to maintain *3* different apps. Please provide convergence. What we need is one chat application not loads of different ones.
Thomas S commented
For me its not clear enough. Does this mean, Skype for Business will dying slowly? Do we have 2 Clients with the same basic functionality over time?
Torsten Werchmeister Hansen commented
Great news, that we will end up with one communication solution.
A couple of concerns:
1. I am experiencing many problems with both Teams and Skype for Business audio and video. How are you going to make the combined solution reliable? How long are we going to have to struggle with the current unpredictable communication issues costing a lot of time and lost focus.
2. The linked article promiss many electronic tools for supporting meetings. How are you going to make the experience flexible, robust and supporting, so that the solution lives up to the Manifesto of Agile Software Development, particularly "individuals and interactions over processes and tools"?