11-04-2018 10:05 PM
Hi,
I have created a Team under my personal Office365 account (a gmail account). I have added multiple users to this team and it has been working fine until now. Today I could not login using my account (owner of Team), I am getting this error:
Other users can still access this team without issues. And I can login to the team with my work email account (for which I added a user previously). However, this is now a major issue as I cannot 'manage' the team with the 'owner' account.
The main problem appears to be that I cannot login with my personal Office365 account (gmail account).
Any ideas how to fix this issue?
11-04-2018 10:20 PM
11-04-2018 10:51 PM
Thanks much @Juan Carlos González Martín. I have posted a comment on that other thread, sounds like an identical problem.
11-04-2018 11:42 PM - edited 11-04-2018 11:43 PM
I had this problem a few weeks ago. I don't even have Office 365 personal subscription, so can't get any support. They either don't want to support me or forward to regular Office support where they don't even know what Teams is.
I was able to fix this. You need to know your tenant's GUID. You can find it in the registration confirmation email. You can probably also see it in the URL when you login with work account or like myself i was able to find it by logging into free Teams SharePoint site and seeing it in the URL. When you have your GUID, then go to https://teams.microsoft.com/_?tenantId=GUID
https://techcommunity.microsoft.com/t5/Microsoft-Teams/Can-t-access-my-Free-Teams/m-p/270176#M18772
11-05-2018 01:30 AM - edited 11-05-2018 01:31 AM
Hi @Oleg K,
I followed your advice. The GUID link approach does not work for me, not sure why, just takes me to the /#guestaccount page. However, I found an old email with a link that allows me to sign in to my account. I have not yet decoded which properties in that long email URL does the trick though ... This means I can only sign in to Teams using this link, and cannot use Teams on mobile devices ...
Overall, this is very odd ... Definitely sounds like a backend bug at Microsoft.
11-05-2018 03:10 AM