Forum Discussion
Teams Internal user getting "Due to org policy changes this chat is no longer available."
I have an internal user attempting to message another internal user but they are getting the message "Due to org policy changes this chat is no longer available. Continue with Skype for Business". Th...
Hello,
Have you had any news on that one? Me and another org are in teams only mode but used to be on skype for business before due to our VOID provider using it. Now we are both migrated to Teams. Everything is carried out properly, checked to see via powershell (all users in both orgs are teams only), no issues connecting to other external users, no issues with the telephony. However, chatting between us is problematic. They can message me on teams (they see no skype icon), i see the messages but i get this error so i can't really interact with them. However, it appears like teams wants to redirect me to the previous skype for business thread to continue the conversation. On my mobile teams app, everything is fine so I am pretty sure it is not an issue with the tenancies.
Have you had any news on that one? Me and another org are in teams only mode but used to be on skype for business before due to our VOID provider using it. Now we are both migrated to Teams. Everything is carried out properly, checked to see via powershell (all users in both orgs are teams only), no issues connecting to other external users, no issues with the telephony. However, chatting between us is problematic. They can message me on teams (they see no skype icon), i see the messages but i get this error so i can't really interact with them. However, it appears like teams wants to redirect me to the previous skype for business thread to continue the conversation. On my mobile teams app, everything is fine so I am pretty sure it is not an issue with the tenancies.
My problem has to do with licensing. I was using the trial license for the some of my users and an Office365 basic license for others. The ones using the trial had to be assigned a 365 basic for their Teams to function. antonispgs
- For posterity, all my team members were on the trial license, so it could have played a role in the problem. But now the problem is solved.
