12-02-2016 11:18 AM
12-02-2016 11:18 AM
We have now fully migrated our company over to Microsoft Teams for inter-office chat. Skype for Business has btea, Microsoft Teams, Chat, Administratoreen completely uninstalled from everyone's machine, yet some of use are still seeing this message when searching for users. Does anyone happen to have a fix for this or know what is causing it?
12-02-2016 12:08 PM
Kevin - we are experiencing the same issue. We were just about to switch from Slack to Teams, but this issue is a pretty big deal considering chat threads are lost. Am very interested to see if there's a fix.
12-05-2016 08:14 AM
Any assistance from Microsoft on this? This is causing a real issue in our organization right now.
12-13-2016 01:50 PM
We currently have this issue as well. We switched from Skype for Business (in Office 365) to HipChat over a year ago, and are now switching to Teams...but we get this message when trying to send individual chats to a few users (but not all). Haven't been able to find any settings on Office 365 to "turn off" Skype for Business so that Teams knows that everyone is native. We need a fix for this as soon as possible.
12-16-2016 01:56 PM
I saw this on one of our early test users. He didn't have Skype for Business installed. Once I installed the Teams application on his Windows desktop the situation was corrected and we could use Teams chat as usual with other Team users.
12-18-2016 03:59 AM
We had the same issue in our company. I discussed with Microsoft Support and they told me a workaround until its fied in an update. Just let all your users sign in and sign out of their "Skype for Business" accounts using the app. The teams app works fine afterwards.
12-18-2016 09:58 AM
Thank you all for the feedback. We have identified this issue and are working to mitigate and fix this.
12-19-2016 07:32 AM
Thanks for the response Julie. Do you happen to have any type of timeframe for a fix? This has really been a problem within our organization.
12-19-2016 11:33 AM
We are currently experiencing this as well. The biggest issue is lack of chat transcripts being kept for these users.
Is there an update on the fix?
01-03-2017 04:48 PM
I am experiencing this issue as well and until it is resolved, I can't see us transitioning to teams.
01-03-2017 11:05 PM
We had the same issue in our company. I discussed with Microsoft Support and they told me a workaround until its fied in an update. Just let all your users sign in and sign out of their "Skype for Business" accounts once using the app. The teams app works fine afterwards.
01-31-2017 08:23 AM
01-31-2017 10:05 PM
As per Microsoft they had noticed the issue a month ago and were working to fix it. If it still occurs for you, then this is the only solution they had for it.. And yes, you'll have to install the client (desktop or mobile) just to log in and out once.
02-01-2017 04:50 AM
What was odd was that on my boss's Mac client for Teams, he had no problem starting a chat with the rest of us in the group. It's just those of us on Windows who can't start chats with each other.
Hopefully they sort it out soon, it's more of an irritance than anything for us.
02-15-2017 07:31 AM
I actually don't know now. We only have four of us using Teams at the moment and I was able to work around this issue for them all by initiating the chats from the mobile app or from the OSX client rather than the Windows client.
I opened a service request with Microsoft and eventually got them to understand the issue and that it seems to be on their end and I've left it with them to come back to me later. I'm just assuming this will get sorted out once they release Teams fully.
02-22-2017 08:08 AM
So what we were able to do to finally get everyone in my organization communicating properly was to repeatedly attempt to start a conversation from both sides. The one thing that helped was that if you are chatting using Skype for Business (whether you actually are or Teams just thinks that you are) is that if you close the application and re-open, that chat dissapears. So we just kept starting conversations back and forth, getting rid of the SfB chats whenever needed until finally they all started to show as Teams chats. It seems as once it finally makes the initial connection it sticks.
Real pain in the rear but at least we are all up and running now.
04-05-2017 10:57 AM
Sorry for the late reply, in the end this seemed to just sort itself out for us.
There's still only a handful of us using Teams right now but we'll be pushing it out to a few others soon so will see if we get the same issues then.
04-20-2017 12:59 PM
We recently started using Teams for internal office communications, and discovered the following fix for this issue:
Every person has to do this. That solved it for us.
12-12-2017 09:56 PM
Any news on that fix yet? Do you think it will be ready in time for your big update that is about to roll out next week?
We just rolled Teams out to one office, and found this issue the hard way and lost 75% of chat history after finding which Teams installs were actually sending via skype (despite nobody in this country having ever used SFB at our company).
We're not pushing, if it's already taken 12 months to fix then it is clearly part of the big web of integrations that your team is flat-out working through... But it would be good to know how long we need to postpone further rollouts for.
02-09-2018 10:32 AM
We had this issue and this fixed it for us:
Does anyone know of a powershell to disable this setting for everyone? We only use Teams not SfB
03-09-2018 09:24 AM
we found a way to apply this change for everyone:
To disable the Tenant-wide Microsoft Teams setting for Skype integration in the Office 365 Services & add-ins portal:
Settings -> Services & Add-ins -> Microsoft Teams
Microsoft Teams settings -> Tenant-wide settings -> General ->
"Use Skype for Business for recipients who don't have Microsoft Teams"
(set this to disabled)
09-13-2018 11:27 AM
09-13-2018 11:27 AM
This worked for us but we had to go to the new teams admin page to disable the setting. If you follow the path above it will provide a link to the new admin page.
10-05-2018 12:23 PM
10-05-2018 12:23 PM