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 is under review! If you have more ideas/feedback specifically on this item, please sign up for user testing here: https://1drv.ms/xs/s!AryUNzh1ogZzif8pDcOcx2pW45I87w
You can also tweet me at @skprufo if you have any questions.
My top requests for Skype for Business being integrated more thoroughly with Teams are:
1. Contact List + Grouping features
2. Conversation History saved into the same folder in Outlook
3. Add Present option to the bottom of personal chat conversations, as it appears in Skype for Business
Get the top 10 requested changes done and get rid of Skype for Biz altogether. How about that?
Connor Slack commented
I prefer having them separate. I find the Teams UI and functionality to be much better & easier to use than the interface for skype & our users feel similarly. We've actively avoided using skype for team chat thus far because it's so messy.
How I break this down is:
If you want a more video-conferencing centric chat application, use skype
If you want an O365 integrated and managed alternative to Slack or Hipchat, use Teams.
Please do not merge the two.
Joseph Thornley commented
When should I turn first to Skype for Business? When should I use Teams? The overlap between the functionality is confusing and causes my team members to use both less than they would if they were better integrated.
Same for Outlook and Outlook groups, one app for collaboration, why having different apps, it's a confusion not a différenciation, at the end the user will decide whether to use the extra feature or not.
Matthew Holt commented
If this comes in phases, presence in teams would be at the top of my list.
Skype for Business is the worst application Microsoft has even made... As soon as Skype calls works in iOS Teams then i'd just delete SFB..
Vlad Yushvah commented
I am forcing everyone in my org to switch to Teams. Skype for Biz is a disaster.
Would love to see these two platforms completely merge and get rid of any separation through some sort of rebranding.
Brian Harris commented
I want skype for business in Teams, but I want persistent voice more than any other feature. Discord is marketed as a gaming social platform but the persistent voice chats there allow the casual collaborative environment that could make Microsoft Teams THE killer app.
I've moved our entire org over to Teams and disable Skype across the board.
There is no reason I can find for our environment (or any other environment) to need both if Teams can provide some of the core features provided by S4B.
-Screensharing needs to not require a video/phone call
-Presence integration into outlook is a MUST
-Presence system based on device usage NOT app usage is a must
If we can get those things in place - 95% of my user complaints will be solved and our environment will no longer have a use for S4B
Stefan Tsalapatis commented
Such integration is not the appropriate for contact centers, service, agents. What we need is a headless unified (S4B, Teams) Client SDK.
Replacement of S4B client in favor of MS Teams, is not a viable solution in corporate environments for various reasons.
We, when installing Teams, simply disable Skype for business and all
Top comments from internal testers at work.
Why do I need to install another app, I already have Skype for business installed? Or Why do I need Skype anymore?
Just a person commented
I agree with making Teams able to be a direct replacement to S4B. Those who don't need the Teams functions can use S4B and others like me can use Teams. I hate having to juggle the two
Share presence and chat between Teams and Skype for Business on-prem.
Skype for business needs to be put to sleep as a sick dog and actively develops the Teams :) We could not accustom users to Skype for business for several years, the users took the Teams immediately within a couple of weeks
I agree with the comments. There seem to be many entry points to do things and having one entry point, which to me would be Teams would be a Hugh advantage. In essence, Teams would become my second desktop. I would start my day there and try to stay there.
Sean O'Quin commented
If the t thread gets too complex or you want to remote view a desktop, it would be ideal to have a "start a meeting" function firing up Skype! Bonus being able to define which users in the chat should be in the Skype meeting
Yes, please implement this. We would love to tie these features into our existing conferencing system. The collaboration in Teams is way above what S4B does, but for A/V, room systems and desktop phones its S4B.
The fact that this wasn't implemented from day one makes me wonder how MS operates internally, do all employees run two clients? Are operations that silo'd that this is not an issue?