Anonymous
My feedback
-
316 votes
An error occurred while saving the comment Anonymous
supported this idea
·
-
12 votesAnonymous
supported this idea
·
-
757 votes
This item is planned. We will update you as we have more details.
Thanks.
Anonymous
supported this idea
·
-
1,012 votesAnonymous
supported this idea
·
-
1,832 votes
Thank you for your feedback. The team has this ask under review, and are considering options for implementing this feature. We will share an update as soon as one is available.
Anonymous
supported this idea
·
-
2,421 votesAnonymous
supported this idea
·
-
4,479 votes
Due to a priority shift this request has slipped to the backlog. I hate to bring bad news. I will continue to provide the feature team your feedback and votes.
Hopefully this will move back up in the queue soon.-Warren
Anonymous
supported this idea
·
-
7,158 votes
Thank you for your feedback! The team has reviewed this request and has added it to our backlog for both Standard (Public) to Private and Private to Standard (Public) channel conversion. We will share an update as soon as it’s available.
Anonymous
supported this idea
·
-
6,538 votes
The team is looking into this feature and considering solutions. We will update when there is more information to share.
Anonymous
supported this idea
·
-
1,943 votes
This feature request is still working its way through the backlog queue.
-Warren
An error occurred while saving the comment Anonymous
commented
Is there an update?
Anonymous
supported this idea
·
-
4,826 votes
I apologize for not having updated this. Changing the landing page for a Team and/or Channel remains on the backlog at this time.
Anonymous
supported this idea
·
-
14,097 votes
We have raised the priority of this work item, and it is currently being worked on. We don’t have any dates to share at this point, but will update when we have new status. Thank you!
Anonymous
supported this idea
·
-
243 votesAnonymous
supported this idea
·
-
166 votes
To help customers meet rapidly changing communication needs, Microsoft Teams has temporarily raised default limits thru July 1, 2020 for Live Events hosted in Teams. Similar increases are coming for Yammer and Stream.
- Attendee limit: events can support up to 20,000 attendees
- Concurrent events: 50 events can be hosted simultaneously across a tenant
- Event duration has been increased to 16 hours per broadcastFor reference, see https://docs.microsoft.com/microsoftteams/limits-specifications-teams#teams-live-events
https://docs.microsoft.com/microsoftteams/limits-specifications-teams#teams-live-events
Anonymous
supported this idea
·
-
1,078 votes
This ask is under review by the team, taking into account your votes and comments.
Anonymous
supported this idea
·
-
2,448 votes
Thanks for the comments and votes. This item remains on the team backlog and we will watch your votes and comments on this feature.
Anonymous
supported this idea
·
-
3,738 votes
Thanks for your comments and votes. The team is working on this and we will update as soon as there are more details to share.
Anonymous
supported this idea
·
-
147 votesAnonymous
supported this idea
·
-
317 votesAnonymous
supported this idea
·
-
8,490 votes
Removing the Conversation Tab is being reviewed by the feature team.
For deleting chat messages, please following progress here: https://microsoftteams.uservoice.com/forums/555103/suggestions/33535006.
Thanks.
Anonymous
supported this idea
·
One of the biggest challenges today is keeping the team memberships in order.
Teams change and we want to give the user one list to keep in order. All the rest should follow automatic.
We use already a long security/Distribution groups for controlling authorisation in different 3th party applications, file server permission, etc.
This makes it so bizar that today you can only add members based on a distribution list, but afterwarths there is nog link anymoren :(