More good news on this front! This week we shared our official roadmap for convergence: https://techcommunity.microsoft.com/t5/Microsoft-Teams-Blog/Roadmap-for-Skype-for-Business-capabilities-coming-to-Microsoft/ba-p/119636
And here’s the PPT deck of the roadmap in case the GIFY makes you dizzy:
Tweet me at @skprufo if you have any questions and I’ll see what I can dig up for you.
I'm concerned that this will be confusing regardless of the implementation. Notification sync'ing between the two has potential, but conversation history? S4B has no concept of a channel, so what channel in Teams is the S4B history going to sync with? A private Teams chat with all members of the S4B chat? And visa-versa?
Too many apps with overlap now...maybe S4B should be retired. :-)
Hi everyone, thanks for your comments in this thread, tweets, emails and calls. Please don’t hesitate to reach out to me with any questions at all; I’m here for YOU! I’ll continue to update this ticket as we make progress towards MSA.
Just in case you missed it, there is a FAQs in the Guest Access Help Article. Just click the “FAQs” tab here: https://aka.ms/GuestAccessHelp We’re updating them this week with new questions we’ve been getting, like “Is Guest Access available for Business Essentials licenses?” (The answer is yes.)
Lastly, the team is starting work on Federation so I’ve broken out Federation into its own UserVoice ticket. Please vote and subscribe to updates on its progress here: https://microsoftteams.uservoice.com/forums/555103/suggestions/20566714
This is a must have. Today's teams span across company borders. It needs to be easy and seamless, no requirement for a MS account. +10K
Slack has pretty much set the bar, so Teams needs to _at least_ meet it. The area where Teams has a chance to beat-up on Slack is for all Office 365 users/companies due to the seamless integration...BUT Teams _must have_ feature parity. :-)
Its been a while since my last update, so wanted to check in and let you know that this is well under way. We’re aiming for early next calendar year (2018) if development and testing go well. I’ll ping you again with a more exact ETA after the new year.
Meanwhile, feel free to ping me on Twitter at @skprufo if you have any questions!
Yes, private channels are important. One use case is specific team members may be assigned to a client's project. There would be a channel built for this project but only those assigned to the project should be in the channel.