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 encountered an issue when trying to create a new team from scratch in the desktop version of Teams. It seems that naming the first channel has become a mandatory step. However, I am unable to name the channel "General" as it shows the message: "The name General is reserved. Try another name."
Could anyone please advise on how to create a "General" channel from scratch in the desktop version of Teams? Is there a workaround for this restriction?
Thank you in advance for your help.
Controlling settings, permissions, and membership within Teams and channels
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.
Thanks Jennifer. Will remember that for the future. We solved by starting at Sharepoint and Adding to Teams from 365 admin. Also creates a General channel.
Josu - obviously I wouldn't be wasting time on this topic or searching the interweb for a solution IF THE BUG WASN'T AFFECTING US.
We have many existing Teams, yes, that are proper with a General folder - I created a NEW team on Teams desktop and tried to mirror our naming conventions and could not.
Trying to make the new Team match the existing Teams led me to this thread.
As noted in my second post, to fix I had to blast the Team and create a new one using one of the other functional methods (in my case starting at Sharepoint). I had to use a slightly different name, but alas, all is now well.
Sorry to waste your time Myles. Won't do it again.
I also agree. I'm also having the same issue weather creating from scratch or from another team
Whoever is in charge of New Teams and New Outlook should really spend some time out in the real work before suggesting some of these strange features. It's great that we can now define the name of it, but what if we want to be the name General. It's like they obviously put some thought into it because the added the safety check to not allow the word General. But it never cross their mind that someone would like to call it General when they first create it?
This is a major issue. We have clients that have exhaustive training and strict processes around new Teams creation. The "General" channel has always been a default, and thus vast documentation exists to accommodate for that. And, the clients use the General channel. So, not only do they need it, but asking them to use the Admin center (most users don't have access to this) or mobile teams (many users do not use mobile teams) is not an acceptable workaround. Even it it was, it would still require significant change management to update all processes and documentation, and train relevant staff.