Anonymous
My feedback
-
2,544 votes
This feature request is now actively being worked upon. As we move through the development process, I will post an new updates to this topic.
Please keep the votes and feedback coming in. Your feedback is shared with the feature team every month.
-Warren
Anonymous
supported this idea
·
-
2,978 votes
Please check “Teams/Skype Consumer chat and calling interop” on the public roadmap at microsoft.com/microsoft-365/roadmap?filters.. for updates.
Anonymous
supported this idea
·
-
3,589 votes
Due to prioritization of other work-items this has been moved to the backlog. We will update when it is being actively worked on again.
Thanks.
Anonymous
supported this idea
·
-
5,294 votes
Thanks for following our suggestion to vote this up on SharePoint. It worked! SharePoint has confirmed that they have already started working on this and I’ll be getting an ETA from them after the holidays. -Suphatra
Anonymous
supported this idea
·
-
1,241 votes
We are working on a better experience in Teams when a user is not connected to the internet. No timeline to share at this point, but we will keep you posted.
Anonymous
supported this idea
·
-
78 votesAnonymous
supported this idea
·
-
319 votesAnonymous
supported this idea
·
-
276 votes
I hate to bear bad news but this feature request has been declined by the feature team.
-Warren
Anonymous
supported this idea
·
-
8 votesAnonymous
supported this idea
·
-
297 votes
Updating the status to “Try this instead” and have added the clarification that after 30 days the name is once again available.
The reason for this decision was that Channels can be restored 30 days after being deleted. During this time, we intentionally don’t support creating a channel with the same name. After the 30 days, the name is available.
You can workaround this by restoring a deleted channel, renaming it, and then deleting the channel again. The previous name is then available for use.
This workaround has already been mentioned in the comments and if an immediate reuse of a Channel Name is required, this is the recommended solution.
-WarrenAnonymous
supported this idea
·
-
10 votesAnonymous
supported this idea
·
-
4,772 votes
Sorry for the delay on an update on this one! I’m hunting down the status for you and will update once I have it.
Also, if you are interested in participating in testing or surveys for this, just tweet me at @skprufo.
Suphatra
Anonymous
supported this idea
·
-
6,892 votesAnonymous
supported this idea
·
-
101 votesAnonymous
supported this idea
·
-
18 votesAnonymous
supported this idea
·
-
46 votesAnonymous
supported this idea
·
-
76 votesAnonymous
supported this idea
·
-
74 votesAnonymous
supported this idea
·
-
452 votes
As mentioned in the prior status, the channel limit was raised from 100 to 200.
In the near future a retention limit will be set so you can still go back and reinstate a channel you had deleted. Once the retention period has expired then the channel will get a hard delete which will free up the space and no longer count toward the 200 channel limit.
This will help with some of the issues you have voiced in the comments below.
But I understand many of you wish the limit to be further increased. I will continue to provide your votes and comments to the feature team.-Warren
Anonymous
supported this idea
·
Anonymous
commented
The 200 channel limit is way too low for us. We want to create a channel for each client so all their conversations, files etc... are in one place. However we have around 300-350 client's per support team.
-
1,028 votes
This request is now being reviewed by the feature team! I’ll keep you posted as to the future decision.
-Warren
Anonymous
supported this idea
·
Suphatra is on a long holiday. She left Microsoft earlier this year for another company.