Skype integration (Consumer Federation)
It would be nice to integrate public Skype (not Skype for Business) into Teams. I am able to chat with Skype for business users within my organization but when working with external clients I still have to go back to public Skype. If I could even just simply chat and call with Skype users as well that would allow me to use Teams as my sole communication platform.
Admins can now enable their tenant to allow Teams users to chat with and call Skype users by using their email address and vice versa.
More details here: https://docs.microsoft.com/microsoftteams/teams-skype-interop for more details
641 commentsComments are closed
Ioannis Gerokostas commented
Please allow team to communicate with public skype
Frank Schumacher commented
BAD News, It makes no sense.
We have to communicate with Skype/Skype for Business/MS Teams as well. Please support Federation over all MS Technologies.
Omer Khalil commented
Back to S4B for me. I'd expect a replacement to be better than the product it's replacing. I haven't seen evidence of that with Teams... Not Impressed.
Completely crazy... I work part of my time for a company that switched to Office365. We used to do all our calls over Skype as they're about a 1000 Km away from me... Now they can't use Skype anymore, and Teams only offers a very, very limited set of features. Basically they can call between themselves and no-one else. No Skype users no nothing. Seems they can't even get back on Skype. I have teams and Skype, but my Skype calls don't get through to them neither. Microsoft, time to wake up guys ! This is completely non-functional, frustrating and does not make in sense in 2019 !
James O'Neill commented
It's been said already but you're pushing people off Skype for business and into teams; SfB had good connectivity to other organizations which has become quite ugly in Team for example in SFB I had external contacts in my IM client; now teams is the client no external contacts. I could see presence for people in federated (or federate-able) organizations so I knew if it was a good time to call them. Gone. And there was a gateway to consumer skype
"Public IM Connectivity" went back to OCS, was in Lync, and SFB and then … Gone. PIC was a server side thing and skype users could contact you and at one time looked like they were fellow lync/sfb users from an org with a funny naming convention.
This is strange, you can add someone with consumer Skype but cannot chat with that person. Why is this even possible when you don't even provide the functionality.
We where happy to start using Teams but this limitation bring alot of hassle, very much disappointed in Teams devs.
I understand you want to push everybody to O365 but from a customer perspective (we, the O365 paying customers) this is quite unacceptable. And seeing below we are not the only one. Why is it that Microsoft never listens to what we -actually- need. A LOT of my business contacts use Skype only, we cannot force my customers to start paying for O365! Do you really want us to switch to appear (or even whatsapp web / discord)? Only good service will make users switch, this is only killing your business!
This is an utterly bad joke. How do you even consider Teams has the same features as Skype for Business???? Well you might decline that feature as well as we might decline to use this garbage.
The Teams client is absolutely horrible and buggy and is absolutely NOT ready for general use. We were forced to switch from SFB to Teams and every user is complaining loudly and asking that we switch to free Skype immediately.
I will join all the others in saying that this limitation is the one thing preventing our organization from making a full transition from Skype for Business to Teams. We have a large team of salespeople that use Skype for Business to contact customers/clients that use consumer Skype since they do not belong to an organization with Skype for Business or Teams, and as long as this limitation continues to exist, we simply cannot make the transition to Teams that Microsoft is so aggressively trying to push. It also makes Microsoft's statement that Teams is 'feature-parity' with Skype for Business a bold-faced lie.
Josh Blalock commented
Difficult to explain feature parity to a customer when this obvious feature has flat out been declined by the Feature Team. Should be standard, as it was present in SfB.
Agreed with all (!) the other comments. How can you seriously not port this required feature from SfB to Teams? Our initial plan was moving from SfB to Teams, but now we will instead stay and look at implementing Slack for all business units.
We are currently using slack (and skype - but we hate skype) and evaluating other solutions. Teams is one of the top possible options for us because we already have Office365 licenses.
But after reading that this feature is declined without telling any reason, I would like to cancel the licenses, work with Libre Office and Thunderbird and keep using slack and hating skype...
Ilya I. commented
@microsoft, hey, what the **** is going on?
Reopen this issue and add possibility to at least chat/add Skype contacts to MS Teams.
You've bought Skype long time ago and now all connectivity goes thru YOUR servers.
Skype for business WAS ABLE to chat/call to regular Skype.
Cherry-picking some commits should NOT be a problem, yeah?
Am I right thinking this was possible with Skype for Business, and now the Teams, which replaces it, does not support calls to regular Skype anymore? That's one way to shoot yourself in the foot.
This is a must-have feature. If SfB has this ability, so should Teams which is its replacement.
Haha, they just don't care and your needs are not important to them. That's the strategy and look how much money they make, that's why they don't think they need you. Yes, it's stupid and yes, they will pay the price. But not today, even the drain has begun and will be unstoppable at a certain point. Not too far from today and maybe not in big business, that takes more time as they loose their user base now. I'm a IT-Pro with 20y of MS experience and for the first time I'm thinking to change my focus. All this stupid decisions without any reasonable argument makes tired. I've always hated Apple exactly for that and now MS is going the same way. Ridiculous but sad.
Craig Tate commented
So, if we are supporting a customer that is a Skype4Biz shop, and we move to the MS Kool-Aid called "Teams", we can no longer chat with our customers who are still on Skype? If so, this needs to be re-instated, as you *know* that there are many many monolithic institutions that have significant investments in Skype Telco infrastructure. "Slow to adopt and roll out" is not a reason to cause them more pain. We need to be able to interoperably chat between the two clients while the transition period is live. To not do so is business hindering of a critical nature.
please reinstate this feature. We are communicating a lot with homed skype users, this is not available anymore since were updated to teams
a great app but this downgrade of interoperatbility is just sad. Please reconsider and let us decide the security implications and benefits for the organisation