This request is for the ability to completely delete a private chat thread. (Not hide/archive.)

Again, this was pulled out into its own topic because it is still under review and no decision has been made.

To recap what has already been completed from the other topic:

1. Delete your own messages anywhere in Teams.


2. Team Owners can choose if users can edit/delete in their tenant as well as choose if admins have the power to delete any message posted in public channels.


3. The ability to hide your private chat threads (these are not the chat threads in channels, but the private chat threads that appear when you click the Chat icon on the left-side app bar).


4. The ability to mute your private chat threads. (these are not the chat threads in channels, but the private chat threads that appear when you click the Chat icon on the left-side app bar).

This topic deserves consideration and separating out hot items is something we have often done. Please don't think of this as an attempt to diminish the ask, we know that many people want this.

Thank you for your understanding and feedback.
-Warren

MORE STATUS
I like the status options in S4B, and so does my boss. It will be important to my boss before accepting the use of MS Teams widely to have a broader range of statuses. Missing statuses are:
* In a meeting
* In a conference call
* In a call
* Presenting
* Be right back
* Off Work

Particularly of importance are "Be right back" and "off work". "Do not disturb" is probably sufficient for "in a meeting", "in a call" and "presenting". But, it sure is nice that S4B auto-detects those three statuses (for the most part).

CUSTOM STATUS
Would like to create a custom status option, such as an out-of-office message.

1 User Request on SharePoint:

Enable integration of Microsoft Teams to an existing SharePoint site rather than to always create a new site collection

There have been a few ideas raised on integrating lists, OneNote, document libraries, etc. from an existing SharePoint site with Microsoft Teams, but in summary, it will be best if we could create a team upon on existing site, so that the "Files" and "Notes" tabs would directly reference the existing document library and OneNote in SharePoint. It does not make sense to have two separate sites: one for all the usual SharePoint stuff, and another just for Microsoft Teams.

2: Link to Existing SharePoint Sites

Trying to link my Team up to an existing SharePoint site - only seem to be able to link to individual folders rather than the whole document library, meaning that if i want all folders on the Team i need to create multiple tabs to get this. Would be good to link to a whole document library rather than one folder.

3: Other Asks

Post Team chat to SP microfeed
Connect team sites onenote if available (replace default notes)
Add links to existing document libraries (replace default files)
Add links to existing lists
Add support for SharePoint taxonomy and managed metadata, SharePoint views etc :D

Right now the conversation tab is the default landing page for a Team and/or Channel.
I want to be able to have a SharePoint site landing page in a tab and that tab be the default tab open when you navigate to a team or channel.

Think of it like a landing page for that team. You may not want it to drop right into Conversations. If you can have a SharePoint page with a Microsoft Teams conversations web part, you get the best of both worlds.
I can see a lot of scenarios where you'd want the chat window open and another tab at the same time. Rather than having to context switch. Imagine the SharePoint page tab being the way to do that by using Web Parts on a dashboard. A web part for the Microsoft Team and another web part for whatever was in another tab.