How can we make Microsoft Teams better?

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.

2,517 votes
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Josh BlalockJosh Blalock shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    98 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...
      • Joey BowlesJoey Bowles commented  ·   ·  Flag as inappropriate

        Any new development in Teams Meetings / communication, needs a Skype Biz counterpart. This will be very confusing for users if they can only do certain items in certain locations. This is one of the huge reasons Yammer hasn't taken off at my company. The yammer presence is different than SfB. The Yammer chat is separate form the SfB chat. I know Yammer was an acquisition, but Teams is built form the ground up.

      • GertGert commented  ·   ·  Flag as inappropriate

        Yes Please. The faster you do the faster we can start making it happen in large scale internally. It is a hazzle to let user understand the differens between the two types of skype, or even 3 if the count also goes together with the Skype consumer.
        So yes please.

      • Anonymous commented  ·   ·  Flag as inappropriate

        This is a great idea. I'd like to be able to add a distribution list to the chat section so I can dynamically add new users and remove old ones from active directory.

      • Micah RairdonMicah Rairdon commented  ·   ·  Flag as inappropriate

        I've been explaining Teams as "Finally Microsoft's myriad of tools in one user friendly user interface." Making the Skype integration full would be one of the last pieces of the puzzle on this.

      • Anonymous commented  ·   ·  Flag as inappropriate

        I agree with Jamie O365 is beginning to get very complicated with multiple methods for doing the same function. Training is tough

      • Jamie ThomsonJamie Thomson commented  ·   ·  Flag as inappropriate

        I want to respectfully disagree with Eric who said: "There are many times when people will want Skype and not Teams and vice versa. Nothing wrong with options."

        My opinon is ... there *is* something wrong with having options. In fact this is the achilles heel of O365 today, there are too many ways of doing the same thing. Erik says "There are many times when people will want Skype and not Teams and vice versa", but doesn't offer any such example.

        Consolidation is what users want in my experience.

      • Jamie ThomsonJamie Thomson commented  ·   ·  Flag as inappropriate

        Seems like an obvious thing to do. At my place we use Cisco's telephony and UC solution (Jabber+Webex) but as we're already paying for O365 I suspect we'll consolidate at some point by getting rid of Cisco. Josh's most pertinent point is "Users want to consolidate the number of apps they use, not increase it", I couldn't agree more.
        I used Teams for the very first time today and my impression of it is that its more than just a Slack compete - its nothing short of a client for the whole of O365, so the telephony part needs to be in there too.

      • Seb HerrmannSeb Herrmann commented  ·   ·  Flag as inappropriate

        Completely agree with this point. Our current trial of Teams reveals just how frustrating this is. We have pilot users on SfB and Teams who report this as the only reason they don't want to jump onto teams permanently. The multiple status, assume they can see chat history from teams in Skype / Outlook. Many prefer the chat UI in Skype (small, compact) can chat to many people and not have a full window open, but when in teams, want to carry on those conversations. You can already join Skype meetings from within Teams - this is good. Wanting to roll this globally, but - this issue is a road block. Will kill adoption and send people back to other services again.

      • Reginald TreiderReginald Treider commented  ·   ·  Flag as inappropriate

        I could not agree more. As users are being asked to adopt and or have to decide which application to use for collaboration, it only generates frustration and confusion. Incorporating all SfB functionalities into MS Teams will only make things more simple for users to live and work within one application.

      • Arden ShackelfordArden Shackelford commented  ·   ·  Flag as inappropriate

        Josh said this very well. The point on inhibiting adoption is key. When you have companies working with 1 tool for 5+ years, getting them to move away from it is very difficult. You'll have those excited to move to a better tool and then you'll have others who ask "But I can chat and make calls with Skype for Business, so why move?".

        I know it was mentioned in a similar post that the intent is to keep SFB and Teams separate entities but... as someone who supports my immediate department group, the end users need 1 thing, not multiple.

      • Andy SaleenAndy Saleen commented  ·   ·  Flag as inappropriate

        This would finally give a single interface to do work in. This is in everyone's best interest and will maximize the usefulness of the Teams product.

      • SethSeth commented  ·   ·  Flag as inappropriate

        The desktop screenshare is an important feature of skype that my users utilized often.
        Forcing users to do a video conference first before being able to share their screen is a huge inconvenience. Either allow users to set a preference so that their webcam is not defaulted on during a video call or provide a way to share a screen outside of a video call.

      • Alok SanyalAlok Sanyal commented  ·   ·  Flag as inappropriate

        "Share Your Desktop / Screen" like Skype for Business is one Vital feature where i still prefer TeamViewer over Skype for Business as Teamviewer is a much better with one big feature "If the shared screen requires admin credentials skype for business hides that while Teamviewer allows me to enter my credentials" Please provide this for remote management

      • ANdReANdRe commented  ·   ·  Flag as inappropriate

        A status list would be great for each channel to see, who is online at the moment. Could be a small frame on the right side to slide in and out.

      • Allan RodolfoAllan Rodolfo commented  ·   ·  Flag as inappropriate

        This would be useful. I too like the idea of having the contact list of everyone in our company instead of just typing to search. Or some type of address book.

      • Pete BostromPete Bostrom commented  ·   ·  Flag as inappropriate

        The Teams client could potentially be a replacement for the SfB client if this was in place. No need for users then to have the confusion of which application to use.

      Feedback and Knowledge Base