It has been a while, how is everything going?
If you have any update about this issue, please feel free to post back.
Hi @66304432
In order to narrow down this question, I have some questions to confirm with you:
1)What is your Teams coexistence mode?
2)Do you have any operations before this issue occurred?
3)Could you make a new conversation for the external users?
3)Does this user use Skype for Business before?
Meanwhile, please contact with your Teams admin to check if you and the external people have added each others domains in external access.
Does anyone else have the same problem in your organization?
To exclude the client issue, we firstly recommend you login to Teams web client to see if this issue can be reproduced.
If there is no issue in Teams web client, then you could try to clear Teams client cache file by following these steps:
1)Fully close Microsoft Teams
2)While holding the Windows key, press R to open Windows Run, then copy and paste the following into the box and click OK:
%appdata%\Microsoft
3)Find the Teams folder, then right click it and select Delete
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
It has been a while, how is everything going?
If you have any update about this issue, please feel free to post back.
It has been a while, how is everything going?
If you have any update about this issue, please feel free to post back.
Hi @LouD-5806
For org-wide wide Teams, the global admin and Teams service administrator will become Teams owner automatically. These Team service admin could be set in Office 365 admin. For more details about how to set it, you could refer to:

So we recommend you check if those owners are Teams service administrator or global admin.
Does anyone else have the same issue in your organization?
Could you provide the screenshot of error message when Teams client crashes?
To exclude the client issue, it firstly recommend you try to clear the client cache file to see if it can be fixed by running this command:
rm -r ~/.config/Microsoft/Microsoft\ Teams\ -\ Insiders
Hi @MaheshKumarGunasekaran-3965
Office-teams-windows-itpro is mainly focused on the general issue of Microsoft Teams troubleshooting. According to your description, your question is more related to Teams development. So I will add teams-app-dev tag to your thread. Someone who care about this tag will give insights for you.
Thanks for your understanding and patience!
Hi @MRAKESH-5751MRAKESH-5751
Our forum is mainly focused on the general issue of Microsoft Teams for Linux troubleshooting. According to your description, your question is not in our support scope. I will remove teams-linux tag from your thread. Thanks for your understanding and patience!
At present, we did not find too many valuable information about it.
Then I found a similar case in the Microsoft dev team is working on fixing. you could refer to the following message thread.
Meanwhile, to solve your issue more quickly, it recommends you to open a ticket in Office 365 admin center here.
Does anyone else have the same problem in your organization?
Is this your custom connector in Microsoft Teams?
What is the phenomenon in Teams web client?
Could you try to follow these steps to configure the connectors?
On the left bar, press the ellipsis under call (...)
In 'Find an App' select RSS and select it. This should bring up the RSS app
Select 'Add to a Team'
Search for the channel name - in this case general by just typing in 'G', select set up a connector
It will go to a screen which tries to set up the connector. Don't put anything in, just select cancel at the bottom, this should fall back to the connector screen
Select 'configured' under Manage
Select '1 configured' under RSS, then Manage
Select Remove
Haven't received your message for a long time.
Do you have any further issue on this topic?
@TeeChinYi-4226
Thanks for your feedback. I will test these two scenarios in our environment and feedback to you if there is any update.