This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
I have a user that is getting this error when trying to create a new Team in the Teams beta version. I was having it as well until I cleared my cache. Unfortunately, the same fix did not work for them. Any ideas?
Setting up a new workspace or conversation thread for collaboration in Microsoft Teams
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
We are having the same issue. It looks like this has been going on for a while with no fix.
I couldn't even try with the web app because I was forced to switch to the new Teams.
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more
My issue is we are assuming this is related to TM801268 yes? Even though it doesn't explicitly say 'create a team from the client' in the list of scenarios. and that advisory has been around for a month.
And then i see TM807389 today which does specifically mention creating a team from the client but only affecting admins.
My concern is Microsoft are not taking the concerns of people in this thread seriously and realising that this is all users in our environment and its a serious issue.
Same issue!!!! Any update, these work arounds did not work for me.
I just signed off my account en closed teams, sign in again en it was working again.. You can give that a try?