Forum Discussion
Wish To Remove guest account from MS teams desktop App
- Go to https://myapps.microsoft.com/
- Click on the Name icon on Top-right, then click on the 3 dots and click on Leave new experience.
- On the reloaded to page, click on the Picture or icon and then click the Cog.
- Click on Leave Organization next to the one that's listed as Guest in Teams.
myspacebarisbroken
In order to do so, you have to be able to sign in at the tenant you joined as a guest.
If the tenant admin removes you as a guest before you thought about leaving the tenant, you no longer can click the "Leave Organization" option.
Any other option?
- to - matthew_linx
I have seen the difference when following the steps I had mentioned above earlier and the one I am mentioning below:
1. Go to https://myaccount.microsoft.com/organizations
2. Sign in with your account that have Guest account added (If not already signed in)
3. You should see the option to Leave Organization instead of Sign in to leave organization.
Try this and let me know if this helps.That didn't help. It's not clear. I only log into Microsoft with 1 account, and that account is signed in through SSO. The organisations to which I had guest membership added me with that same account.
Your directions:
1. Go to https://myaccount.microsoft.com/organizations -> Defaults to my 1 account username
2. Sign in with your account that have Guest account added (If not already signed in) -> brings me to my SSO sign in and my own tenant.
3. You should see the option to Leave Organization instead of Sign in to leave organization. -> Nope.- I have this same problem. The Guest account shows in the Desktop app but not in myaccount page. I want to remove it from my account when I no longer have the ability to login to it.
As noted above, one cannot 'leave' an organization that has already removed one's Guest Access as Microsoft require a sign-in to effect the 'leave'. This is a failure of development, so the external organisations continue to show at present. I will open a case for this to see if they can remove it from the backend, but this is a clear deficiency.
