May 05 2020 05:28 AM
May 05 2020 05:28 AM
this is a weird thing... my company has it's teams setup "open" for all companies, and this other company I'm trying to contact with is as well open.
Before the upgrade, we were able to chat on skype for business.
Now, both our companies got upgraded to "teams only", so skype for business is no longer an option.
On the desktop and on the web, when I receive a message from this company, I cannot reply, because I get this message
"Due to org policy changes, some chat and calling features are no longer available. Continue your conversation here."
If I press the link on "here", it opens a new teams chat window, this time with the skype for business logo. If I send a message on that chat window, the other person gets the message but cannot reply (same message as I have). So, effectively, in order to communicate, we need to use 2 chat windows...
The strangest part is that on my iPad this works perfectly. I can reply on the correct chat window. It's just on desktop and the web that this does not work.
Has anybody faced this issue?
May 05 2020 06:18 AM
May 05 2020 07:01 AM
Thanks for your reply.
As I mentioned in the original post:
1) Upgrade to teams has been performed on both organizations, so "Teams only" mode is mandatory, right? In any case, please see attached print screens from the external access setting and the upgrade setting
2) On an iPad, it works fine... it's just on desktop and web that it doesn't
It must be something else
May 05 2020 07:10 AM - edited Jul 01 2021 03:54 PMSolution
Sure, I was focusing on this part
If I press the link on "here", it opens a new teams chat window, this time with the skype for business logo
I would do the following to make sure it works
1.) Ensure, through Powershell that both of your users are 100% Teams only on the back end
You would use something like this
PS C:\> Grant-CsTeamsUpgradePolicy -PolicyName UpgradeToTeams -Identity email@example.com
2.) Check it and make sure you are both on your respective lists in your tenant
Get-CSOnlineUser | select UserPrincipalName, teamsupgrade*
3.) Start a completely new chat with the other person
That 'ought' to fix it, may take a few hours to propagation and you may have to check back a few times in a 24 hour period, but from my experience of this issue, it should help to fix it. If it doesn't you can go down the routes of clearing the cache or re-installing the client
It is well known doing the upgrade in the TAC doesn't always have the desired effect and so falling back on the shell to re-propagate fixes a lot of it
Let me know how you get on
May 05 2020 07:34 AM
May 05 2020 07:37 AM
Apr 14 2021 08:30 AM
Apr 14 2021 09:42 AM