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

Anonymous

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.

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

44 answers

Anonymous

2024-12-04T19:26:34+00:00
It was mentioned earlier in this thread that a fix is expected by Q1 2025. The original intended feature, to my understanding, is this one ( https://www.microsoft.com/en-us/microsoft-365/roadmap?filters=&searchterms=395931 ). I have a few questions regarding the behaviors that will result from this fix:
- On Teams UI, will it create a default General and a named channel OR a default General channel only and then we can rename it?
- On the Graph API, will the call to retrieve the primary channel( https://learn.microsoft.com/en-us/graph/api/team-get-primarychannel?view=graph-rest-1.0&tabs=http ) correctly return the General channel, even if it was renamed?
- When renaming the General channel in the UI, does it rename the General channel folder in SharePoint?
Was this answer helpful?

1 person found this answer helpful.

0 comments No comments
Anonymous

2024-11-28T09:47:09+00:00

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

General Talk

General Chat

General Conversation

General whatever....

This is a rubbish fix as it misses the whole point.
Was this answer helpful?

4 people found this answer helpful.

0 comments No comments
Anonymous

2024-11-28T09:46:11+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 ...

Q1 2025 seems like a long wait since september 24 when it all started...

Thanks for the update
Was this answer helpful?

0 comments No comments
Deleted

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
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