Forum Discussion
Teams open and close itself when you change Team scope. Ubuntu; userStorageMisMatch
Hello We have a problem with Microsoft Teams breaking down. After logging in to the client's scope (switching the team from main 'company' scope to client Team), the application turns off and th...
- This workaround worked for me: https://www.reddit.com/r/MicrosoftTeams/comments/mktdgu/anyone_with_the_teams_for_linux_desktop_client/gtoiodd?utm_source=share&utm_medium=web2x&context=3
1. sign out of teams
1. open teams, get to the sign in page
1. click "Sign-in options" on the O365 login screen and choose "Sign in to an organization"
1. type in the domain name of the organization to sign in to - you can see what these are in the azure portal's "switch directory" option, for me it was "$COMPANY.onmicrosoft.com"
1. enter user/pass as normal
There are a few related issues on uservoice, consider upvoting those to raise the profile of this issue:
* https://microsoftteams.uservoice.com/forums/908686-bug-reports/suggestions/43208844-cannot-login-to-organization-as-guest-anymore
* https://microsoftteams.uservoice.com/forums/908686-bug-reports/suggestions/43068624-unable-to-switch-organizations-after-1-4-00-7556-u
* https://microsoftteams.uservoice.com/forums/908686-bug-reports/suggestions/43090383-switching-tenants-no-longer-works-on-linux
Hello,
I got the same issue, and it was resolved.
Seems, this issue only happened on Linux version, it works fine on Mac, Browser and iOS app.
I'm not sure if it can work on your side, but let try some below steps:
- Logout your account from Teams
- Open an invitation link to this scope (the link that you have received when you were added to this scope) like: https://login.microsoftonline.com/redeem?rd=https%3a%2f%2finvitations.microsoft.com%2fredeem%2f%.....
- Login screen will appear, try to log in to your account and see the result.
Thank you.
I got the same issue, and it was resolved.
Seems, this issue only happened on Linux version, it works fine on Mac, Browser and iOS app.
I'm not sure if it can work on your side, but let try some below steps:
- Logout your account from Teams
- Open an invitation link to this scope (the link that you have received when you were added to this scope) like: https://login.microsoftonline.com/redeem?rd=https%3a%2f%2finvitations.microsoft.com%2fredeem%2f%.....
- Login screen will appear, try to log in to your account and see the result.
Thank you.
- huh, not sure if I still have that link, I'd try and let you know
My friend have a similar case to your solution - he says, teams are crushing after changing the scope, but luckily they open after crash into recent scope, so he can work. In my case I'm reverted to main TeamScope.
I've heard that updated linux version was released
I did not see it yet neither in snap nor in apt
but I look forward to test it
I hope that Linux version of the Teams would incorporate the Windows/Mac version of the app - that would be only 2-3 month release delay... maybe Teams Developers could be more aware of app and API lifecycle, because I really suspect that the problems are caused by Microsoft changing server-side API that is not reflected in Teams linux desktop app, as it is not yet released...
If only someone could confirm that... and fix internal Microsoft procedures...
I still see:
```
latest/stable: 1.4.00.7556 2021-03-29 (4) 127MB
``` - I'm having the same problem as sirkubax and this procedure did not change anything for me.
What I did:
* sign out from teams in the desktop app
* sign out from teams in any browser tabs
* sign back into login.ms to access my email
* find my "your request to join $ORG has been approved" email
* click the "Join teams", which is a urlshortener.teams.microsoft.com link
* this opened a new tab, some redirects, then prompted me to get the linux app. The "Get linux app" button leads to the normal download page. The "Linux DEB (64-bit)" button downloads `teams_1.4.00.7556_amd64.deb`, which is what I have installed already
* I opened desktop teams
* it prompts me to sign in, I do so
* it opens with my default organization, not the $ORG related to the email link
* the "crash and switch back" behavior described here still occurs
