Please check “Teams/Skype Consumer chat and calling interop” on the public roadmap at microsoft.com/microsoft-365/roadmap?filters.. for updates.
@Alex, so glad to so MS working on this!!!! THANK YOU!!!!!
Not able to federate with Skype consumer was a no-go for moving to Teams and just made NO sense.
BUT, a big potential issue that I see when looking at the M365 roadmap for this. The roadmap item says that it will "Enable Teams and Skype for Consumers users to chat and make VoIP calls to each other". It says nothing about video (HUGE!!!!) or screen sharing (big, but secondary to no video). Is this intentional or is MS starting with chat/VoIP calls and then adding video (and screen sharing) later?
A couple of other questions:
1. Will this consumer federation include group (more than two Teams, Skype (consumer), S4B users) capability?
2. Will you please remember to allow the federation with Skype (consumer) users who's email address is NOT a Microsoft domain. An example of this is a Skype user with the Microsoft Account of email@example.com or firstname.lastname@example.org.
Featured ID: 53935
Microsoft Teams - Teams/Skype Consumer chat and calling interop
Enable Teams and Skype for Consumers users to chat and make VoIP calls to each other
They had better add consumer Skype federation and better external party (SfB/teams) federation if they want to get people off of SfB. (another topic altogether but they also need a simple/streamlined IM/AV Teams client version as well as going from SfB client too Teams client is way to complicated bloated/complicated for users needed simple IM/AV capabilities)
I do hope that the feature team will reconsider this! How are we supposed to migrate from Skype for Business to Teams when we loose a major feature like this? Not all business/people have Skype for Business (or Office 365/Teams) but many that don't still have consumer Skype accounts. Not gaining Skype (consumer) federation means losing contact with those business contacts (or having to resort to us using Skype for Business/Teams AND a consumer Skype account to communicate.
As stated by the original poster, having Chat as a separate area in the Teams client is not productive for certain use cases. It can be a step backwards from the separate (and simple) Skype for Business interface.
I too understand Microsoft wanting to bring everything under one interface and am not advocating that Microsoft does a way with the current all-encompassing Teams apps. Sometimes you need a separate interface, or at least the ability to bring it out into a separate interface. I'd love to see MS do this and using Teams client for IM/Audio-Video chat makes me want to go back to Skype for Business or some other application every time I use it.
I also created a separate UserVoice request that is similar to this request but might go a step further than what your request is asking for. https://microsoftteams.uservoice.com/forums/555103-public/suggestions/38860165-streamlined-im-audio-video-chat-interface
We’re pleased to announce the Teams client for Linux is now available for preview. Please see details at https://techcommunity.microsoft.com/t5/Microsoft-Teams-Blog/Microsoft-Teams-is-now-available-on-Linux/ba-p/1056267.
Please check out the Q&A forum here – https://docs.microsoft.com/answers/topics/teams.html.
This would be great! Another use-case is in a classroom setting. A teacher can queue up one or more messages to be sent to their class ahead of time.
This is in internal testing. I don’t have exact timing for you, but wanted to let you know it is coming!
Due to a priority shift this request has slipped to the backlog. I hate to bring bad news. I will continue to provide the feature team your feedback and votes.
Hopefully this will move back up in the queue soon.
As stated in the last update, the ability to use multiple Teams accounts at the same time is being implemented in stages for Desktop. Faster tenant switching functionality on the Windows client has been rolled out to the public ring fully, and Mac will begin rolling out soon. Work is in progress on cross-tenant notification improvements, and support for multiple accounts on desktop will follow. We’ll keep you posted!
Note: The ability to use multiple Teams accounts at the same time is supported on iOS & Android today.
Alex & the Teams team
Item 1 and 2 are Under Review.
Item 3 has been Completed.
I’ll keep you posted as I hear more on this request.
This work is officially in the plans now. We will update as we have more information for you.
Thanks for following our suggestion to vote this up on SharePoint. It worked! SharePoint has confirmed that they have already started working on this and I’ll be getting an ETA from them after the holidays. -Suphatra
I’m excited to share that I got to use this in our experimental settings the other day. We’ve built it and are testing it internally. I’ll let you know once it moves up in the validation rings!
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.
Due to prioritization of other work-items this has been moved to the backlog. We will update when it is being actively worked on again.
Thank you so much for your support of the product. This request was particularly helpful and we appreciate your engagement in the surveys, comments and forum to help us design this feature. Please continue to submit ideas!
For this item, we’re making great progress. It has now entered TAP validation with a small group of tenants. Will let you know how that goes!