Considering that teams channel are sometime used for discussing projects, problems, long term plans, etc. in business regardless of the size. Having the possibility to archive an entire post (and its replies) either in an dedicated archive feature added to teams or give the option to send the post to a different teams / channel ( that would be used for various backup decisions or archiving data) would be a great addition to MS Teams.

This would go hand in hand with the search feature in Teams to easily find old post that would be relevant reference to a new discussion that your user would need to start.

I think this would also go along the many ideas about archiving feature for other aspect of MS Teams (like archiving entire teams / chat)

*English follows Japanese

■Title(件名)：
Microsoft Teams において所有者でないメンバーに [メンバーを追加] が表示されないような設定が可能となるよう機能の拡充を希望します。
Allow us to see the feature to hide “Add members” button from users who are not the owner of the team

***************
■Description(内容):
現在、Microsoft Teams のチームに所有者でない "メンバー" がメンバーを追加する場合、チームにメンバーを追加することを要求するメールが所有者宛に送信される動作かと存じます。この動作により、所有者から要求を承認されない限り、メンバーの追加が不可能な動作となっております。しかしながら、不要に要求をされることで不要なメールを受信し、承認または拒否をする工数が発生する為、所有者でないメンバーには、[メンバーを追加] の表示がされないよう設定が可能となるよう機能の拡充を希望します。

In current design, team owner will receive an email and need to accept or deny when team “members” who are not owner add another user as member, and general users are not able to add new members unless the owner accept the request. This design increases team owner’s unnecessary emails or workload for accepting or denying those requests.
Therefore, I would like to see the feature to hide “Add members” button from users who are not the owner of the team.

A 200-channel limit seems irrisory nowadays.
I am working hard to convince the directors of the company to move all operations to Teams, but the 200-channels limit is a dealbreaker. I implemented Teams quite successfully in my area of operations, and opened up 1 channel per client (the structure is: one Team per company area, that is, one for Operations, one channel per client and one thread in the conversation per project).
In my area of operations, I currently have 79 clients, and more than 400 projects. I have been fine with this but once I bring this up company-wide, we will hit the 200-channel limits pretty soon.
Please provide an option to increase the number of channels within the Team. We need at least 1000.

Our office is in the process of moving form HipChat to Team. We all agreed that Slack had a better interface but Teams was included with O365 and did not feel Slack was worth the price. Our user base is made up primarily of Developers and Linux Engineers that use chat way more than average users. Our experience has been frustrating due to the amount of clicking between teams channels and chats, Clicking to see who is present in the Team/Channel, the active feed uses first names rather than user names or full names and requiring a click to upload code. Maybe I am missing something but it seems to take much more time than other chat platforms I have used in the past. Also, I'd recommend adding a thumbs down emoji or really allowing the upload of custom emojis would be preferred. I would like to see a /command for code blocks, showing Team/Channel users and status, and a keyboard shortcut allowing us to quickly search contacts and direct message. /chat does allow direct messaging is much to slow looking up users and does not drop you into the direct chat under the Chat tab. I do like a lot of the Teams features but it's outweighed due to normal functions requiring mouse click or not being as quick as I expect.

Currently our initial circle color is random, but we should have the ability to pick our own color so that everyone on the team is different and there are no duplicates.

Additionally, if you download the Planner app in Teams, having different colors is essential, especially when you are using the schedule view. Everything being white does not help anyone and it is one of the reasons people will look elsewhere for other apps outside of Microsoft.

Colors would be VERY beneficial and should be easy on your end to implement. Please consider in order to make this a better product. Thanks!