We have all had the Teams We’ve Run into an Issue Error. Something worked one day and then the next…it doesn’t. How frustrating! Most times, it happens with something as simple as logging in but there are other cases where you might get this error.
I will give you an example…
Accessing an External Team You Have Been Invited To
You may get the Teams We’ve Run into an Issue. In this case, the user was receiving errors trying to get into an external team he had been part of for a while. It showed the error message from the picture above. At first only the Teams web app worked, then nothing worked.
What Teams We’ve Run into an Issue Might have been…
First, I thought it was a mismatch between Teams policy settings between the user’s company and the external company. The policy to allow only Teams 2.0 clients was enabled on the user’s side in the Teams admin portal. We had moved to the new team’s client permanently as MS stopped supporting Teams Classic on July 1st.
If the external companies MS Teams policy was set to “Microsoft-controlled”, which allows the use of Teams Classic until next year, it could cause a conflict.
It was verified that the external organization was using the New Teams Policy, so it wasn’t that…
What it was and What fixed It
It turns out it was 2 things. One, the user had recently got a new mobile device and the external organization needed to reset his MFA. And two, his Teams Cache needed to be reset.
I have written a great post on how to delete Teams Cache (Classic and New) Here.
Dan
I am an IT professional with over twenty years experience in the field. I have supported thousands of users over the years. The organizations I have worked for range in size from one person to hundreds of people. I have performed support from Help Desk, Network / Cloud Administration, Network Support, Application Support, Implementation and Security.