11-20-2017 08:25 AM
11-20-2017 08:25 AM
We have had an ongoing issue that appears intermittent and random for users - starting a direct chat in Teams with a user who is in Teams, shows up in the drop down, but then the chat box displays 'This user is currently using Skype for Business. Some Microsoft Teams features won't be available. Invite to Microsoft Teams.' Message user on Skype for Business. Some users can see that same user as a Teams user with no issues. Has anyone seen this?
11-20-2017 08:49 AM
11-20-2017 09:50 AM
That was my first thought as well, however the user I was attempting to message was in the room with me and logged into Teams.
12-12-2017 07:28 AM
I see this issue almost every time I try to on-board someone new to Teams. It is really annoying, although it does seem to go away eventually on it's own. I've read somewhere else that a restart or log out / log in might help, but haven't yet been able to confirm it.
03-09-2018 09:27 AM
we found a way to fix this 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)
05-28-2018 06:44 PM
Awesome that was really annoying, we didn't use the "Skype for Business" with our Office365, and while migrating from standard Skype to Teams we had this message all the time even though we didn't use it.
05-29-2018 12:48 AM
Just to flag you might want to change this once Microsoft deliver 1:1 federation to other businesses as this will use that Skype service to do that federation in the first instance. By then however you'll also be bale to select a mode in https://admin.teams.microsoft.com that will switch people entirely into Teams client.
08-19-2018 06:56 PM
I'm an innovation lab type working to introduce Teams and more collaborative ways of working to the wider company, it's a bit of a skunkworks thing as per, so I don't have full IT access. I'm seeing this problem all the time, but it's intermittent - sometimes I can communicate with users just fine, other times I get the 'using Skype for business' error mentioned here. What does it actually mean? It's not a great message. Does it mean that the user will not get that message ever? Why does it only happen sometimes? How are we supposed to resolve it without master Admin access?
Thanks for your help
08-20-2018 06:57 AM
Hi Jasmine, it means that user will receive your message in Skype for Business rather than Teams. This will also mean that some features of a Teams conversation are missing, e.g. send pictures, files, gifs etc as they aren't supported when it's talking to Skype.
How it decides will tend to depend on the settings your admin has set, and you can't change them without being an admin. For example they can define that all users will only use Teams, only use Skype or, and as default, that you are in Islands mode.
In this islands mode your messages in Teams will go to Teams and Skype will go to Skype, keeping the two separated. The exception being that if Teams sees you are messaging a users that has never used Teams it will be send to them via Skype and that message is displayed. If they log in to Teams, even just once, then their messages will be sent there instead.
08-20-2018 10:13 AM
10-19-2018 11:27 AM
How long did it take for this to take affect? I've made the changes and given it a couple hours but it still hasn't corrected itself.
10-19-2018 02:31 PM
Answer what ?
your admins can set the mode that you are in to one of
Teams Only - All your messages from Skype or Teams will come to you in Teams
SfB Only - All your messages from Skype or Teams will come to you in Skype for Business
Islands - Teams messages to Teams, SfB to SfB, no interop at all
12-21-2018 10:23 PM
Only have the modes:
Skype for Business only
The mode "Team only" is missing. How can I activate it?
12-22-2018 12:01 AM
12-23-2018 03:15 AM
I tried the PowerShell command in Admin mode but get the error:
The term 'Grant-CsTeamsUpgradePolicy' is not recognized as the name of a cmdlet, function, script file, or operable program.
I`m connected to AzureAD.
12-23-2018 09:52 AM - edited 12-23-2018 09:53 AM
Installed Skype for business online module and somehow managed to go through the whole process without too many error messages, but alas the option "Team only" is still missing!
I googled for a novice guide for PowerShell for Office 365 but couldn't find any simple step-by-step guideline, so the whole process for me was more a trial and error approach with the accompanying frustrations.
However, I found one simple solution for the SfB problem posted by Justus Stewart on
1) Click on your profile picture
2) Select Notifications
3) At the very bottom is an option 'Chat with Skype for Business' - Disable it
Every person has to do this. --> We only had to do it on two computers and the problem was solved. Carefully read the later posts in that thread regarding possible problems like losing chat history.
02-07-2019 12:38 PM
We had encountered exactly the same situation. To send message to users who appears as "This person is currently using Skype for Business. Some Microsoft Teams features won't be available." we do so:
place mouse pointer on the user's icon and when user's card will appear you have to press "Chat" button. After that new chat window with Teams user will be opened. If it will not work, press "Organization" button on user's card (instead "Chat") - will appear organization structure consist of user's cards, place mouse pointer on needed user card and press "Chat", so chat window will be opened.
04-23-2019 06:33 AM
If you have an older version of Teams installed on the computer, we have found uninstalling and reinstalling with the latest setup.exe fixes this issue. There must be a registry key that locks the mode. This is similar to the old Skype/Lync/OCS profile folder occasionally that would need to be deleted to fix sign in issues.
If you have been using Teams for a LONG time and just upgraded the client overtime, uninstall and reinstall. This is assuming all settings are correct in the O365 Tenant.
We see this a lot for CIE(customer immersion experience) tenants and the content package. The content package installed on the machines uses a very old Teams install file. This must have a setting to force Skype interop. After uninstalling and reinstalling the Teams client with the latest version fixes this issue.
04-23-2019 06:37 AM
@jeff whealenI did each of those steps and it did not resolve the issue the issue automatically for me. I have to do the work around to resolve the issue. MS support was unable to resolve the problem despite months of working on it.
05-15-2019 01:46 AM
How are you able to change this setting when all your settings are managed in the teams portal. I have found the setting you have described however it is all blanked out and is now managed in the Team Admin portal and I cant find a setting that references it.
Unless there is a PowerShell command that can allow us to do this. We have upgraded the org wide settings to only use Team so we can move away from S4B and now use Teams only as our new VOIP system but this is holding us back a little. Let me know if I'm missing something any help is better than no help.
05-28-2019 11:52 AM
@jsummers1994 I'm guessing this is where you need to go:
And probably set Coexistence mode to "Teams Only".
We actually have it set to "Islands", and it doesn't seem to be hurting us, meaning users could optionally also use SFB if they wanted.