This feature request is working its way through the backlog queue. No new details are available yet.
Please check “Teams/Skype Consumer chat and calling interop” on the public roadmap at microsoft.com/microsoft-365/roadmap?filters.. for updates.Anonymous commented
unbeliavable, forced to upgrade from S4B to Teams and we are not allowed to use it to contact normal skype users when we were able to do that with S4B?
Discarded so we must use two clients? Set an option to allow\block connection to Skype as we were able to on O365.
GG, this plus the costant heavy memory usage of Teams = moving to slack
This feature is still on the backlog.
As part of our commitment to being customer driven, we’d love your input on top features that will improve your satisfaction with teams and channels navigation, and help you be more productive in Teams. Please access the survey here: https://forms.office.com/Pages/ResponsePage.aspx?id=v4j5cvGGr0GRqy180BHbR7hW7rKdVrVInUSM809cvrtUNFhLRVNJVVhaUFI0WEJHVTA4MlpGWVZUSS4u
Thanks for your feedback!
This is still being worked upon. I hope to have more details in the next couple months.
Please know the team is actively working on this feature.
Great performance and user experience remain a topmost priority for us. Application launch time has seen improvements in the recent build. We will continue making improvements across the product including channel to chat switching and overall resource consumption.
This feature item is still in the works. We will keep you posted as we have new info from the feature team.
We are working on a design with more density in mind. Until this design is solidified we are putting this item back to Under Review.