Unable to Create a "General" Channel from Scratch in Teams Desktop

Anonymous
2024-09-10T03:57:45+00:00

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.

Microsoft Teams | Microsoft Teams for business | Teams and channels | Manage a team or channel

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.

0 comments No comments

44 answers

Sort by: Oldest
  1. Anonymous
    2024-10-09T15:43:55+00:00

    This works!! Thank you so much

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2024-10-26T01:13:37+00:00

    Hello,

    Any updates on this issue? The other problem names "Teams has no General Channel" also has no additional replies from Microsoft. Please reply to your customers and fix your bug!

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2024-10-31T23:18:33+00:00

    Another workaround that I have found is to start in SharePoint and create a new Team Site.

    Once that is created you can use the "Teamify" option on the bottom left of the home page to generate the new Team from the group, and the General channel is set up automatically.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2024-11-01T20:27:02+00:00

    A super easy fix - add another word to the channel name

    General Talk

    General Chat

    General Conversation

    General whatever....

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2024-11-28T09:29:08+00:00

    Just had a call with MS support, they have confirmed it is a known bug related to roadmap ID 395931. They are expecting a fix in Q1 2025 ...

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments