Aug 26 2020 10:59 PM
Hi,
I have been chatting with external users (clients) of different domains from my organizational account. Suddenly, this has stopped working. Instead of an 'External' tag next to their name, Now I see the user as 'Unknown'. The more worrying this, I still get the messages from them, but I'm not able to reply to them.
Can someone help me with this. Thanks in advance!
Aug 26 2020 11:17 PM
Hi,
Are you the only one in your organisation with this problem or are there more users with the same problem? If there is changes made by your administrator for Teams I suggest that you report this to Microsoft Support via the Office 365 admin portal.
Aug 26 2020 11:24 PM
It's actually everyone in my org; not able to chat with external users @Linus Cansby.
Aug 27 2020 02:03 PM
@nitishkanann23 Make sure that nothing been changed with the settings for external communications by admins:
https://docs.microsoft.com/en-us/microsoftteams/manage-external-access
Test in the web client https://teams.microsoft.com
And if that doesn't work contact Microsoft Support.
Feb 16 2021 04:37 AM - edited Feb 16 2021 04:41 AM
We have a similar problem. We have this workaround for the problem :
Click on the name above in the chat, write a message in that chat window. This should work.
We have a MS case open for this problem but this workaround makes it less of a problem for us.
Do you have exchange on premise or/and used skype on premise?
Is teams only set to "teams only" ?
Apr 23 2021 07:22 AM
@MastBob did you found a solution? Same problem here...
Apr 25 2021 11:16 PM
Hello Jef,
I did solve it. It has been a wile so I don't know exacly how I did it but here are some left over notes. I would create a MS case if you are not sure about the following commands.
This commands to connect to PS :
Import-Module SkypeOnlineConnector
$session = New-CsOnlineSession -Verbose -OverrideAdminDomain ******.onmicrosoft.com
Import-PSSession $session –AllowClobber
Command to disable lync on premise shared sip space
Set-CsTenantFederationConfiguration -SharedSipAddressSpace $false
also changed the following DNS
lyncdiscover.yourdomain.com to webdir.online.lync.com
I do remember setting some user settings from hybrid to online online but not sure if this command did anything :
Get-ADUser -Filter {msRTCSIP-DeploymentLocator -like "SRV*"} |
Set-ADUser -Clear msRTCSIP-DeploymentLocator
Jun 28 2021 12:30 PM
Jun 29 2021 04:50 AM
@Lucas_Reis can you elaborate a little further? S4B? Hybrid? Teams migration?
Jun 29 2021 01:02 PM
Inside my tenant, there are 100 users, these 100 users, 30 users are not able to answer the external Teams chat, the other 70 users are responding to normal external team chat. For those users who are having problems answering the Teams external chat, the following error is appearing: "due to the change in the organization's policy, this chat is no longer available to use Skype For Business". Checks I've already done. My tenant and the tenant who is making an external communication are without teams only
Jun 30 2021 01:34 AM - edited Jun 30 2021 01:35 AM
Check teams admin center and go to users. Check if there is a difference on the following options:
ofcourse all users need a valid license.
Also check if your SIP/skype/teams Dns records are pointing to office 365 and not something onpremise like Skype.
DNS requirements for Skype for Business Server - Skype for Business Server 2015 | Microsoft Docs
Jun 30 2021 06:41 AM
the interesting thing is with some users that this happens, so if it were DNS it would be a problem for all users
In the picture below there is a difference in the powershell window on the left, the user who works, on the right side of the user who doesn't.
Jun 30 2021 06:47 AM - edited Jun 30 2021 06:51 AM
Solutionyes in my post above I posted a command to clear all those locators. I think it was this one :
Get-ADUser -Filter {msRTCSIP-DeploymentLocator -like "SRV*"} |
Set-ADUser -Clear msRTCSIP-DeploymentLocator
http://terenceluk.blogspot.com/2020/11/powershell-script-for-clearing-msrtcsip.html
you can always try 1 account with the AD attribute editor and see if it works before dooing the command on all users. ( don't forget to sync to the cloud)
Dooing a logout + login cycle for teams on the users computer might be required.
If not you can make a case with O365 support but I solved it myself before they had any decent info
no idea why this happens but in my case the Skype on prem server crashed before we could decommission properly.
Jun 30 2021 07:00 AM
Jun 30 2021 07:04 AM
Jun 30 2021 07:25 AM
Jun 30 2021 10:33 AM
Jul 04 2021 11:22 PM
Jun 30 2021 06:47 AM - edited Jun 30 2021 06:51 AM
Solutionyes in my post above I posted a command to clear all those locators. I think it was this one :
Get-ADUser -Filter {msRTCSIP-DeploymentLocator -like "SRV*"} |
Set-ADUser -Clear msRTCSIP-DeploymentLocator
http://terenceluk.blogspot.com/2020/11/powershell-script-for-clearing-msrtcsip.html
you can always try 1 account with the AD attribute editor and see if it works before dooing the command on all users. ( don't forget to sync to the cloud)
Dooing a logout + login cycle for teams on the users computer might be required.
If not you can make a case with O365 support but I solved it myself before they had any decent info
no idea why this happens but in my case the Skype on prem server crashed before we could decommission properly.