Dan M
My feedback
-
1 voteDan M
shared this idea
·
-
1 voteDan M
shared this idea
·
-
1 voteDan M
shared this idea
·
-
571 votes115 comments · Public » Accessibility (keyboard navigation, reader, colors etc.) · Flag idea as inappropriate… · Admin →
An error occurred while saving the comment Dan M
supported this idea
·
-
1 vote0 comments · Public » Apps, Connectors, Messaging Extensions · Flag idea as inappropriate… · Admin →Dan M
shared this idea
·
-
Reply to specific message in chat on desktop app
-
reply.png 26 KB -
reply.png 26 KB -
Respond_to_specific_Chat.PNG 53 KB -
Teams_message_idea.docx 174 KB -
Teams_2020-05-30_01-13-29.jpg 182 KB -
Whatsapp Screenshot.jpg 255 KB -
Teams_Reply_To_Message.png 3 KB -
whatsApp.jpg 31 KB -
CHAT.jpg 192 KB -
Team Chat.JPG 80 KB -
Capture.PNG 35 KB -
pandraus06-11-004.jpg 118 KB -
reply.PNG 82 KB
47,483 votesThank you for your feedback! The team is hard at work on this highly requested feature. We will share an update as soon as one is available.
Dan M
supported this idea
·
-
-
2 votesDan M
shared this idea
·
-
359 votesDan M
supported this idea
·
An error occurred while saving the comment Dan M
commented
Disabling this in Teams with large number of members / org-wide Teams would be a great add. This would avoid people accidentally starting ad-hoc meetings in large Teams. Common examples of this would be company communities, ARGs, org-wide Teams, etc.
This setting should be at the Team or even the channel level.
-
1 voteDan M
shared this idea
·
-
24 votesDan M
supported this idea
·
-
529 votesDan M
supported this idea
·
-
447 votesDan M
supported this idea
·
-
2,605 votes
This is currently in internal testing rings at Microsoft, and the feature team is targeting a release to the public in early Q2.
Stay tuned!
~Alex & the Teams team
Dan M
supported this idea
·
-
4,994 votes
We are currently testing this feature internally, and will share an update as soon as it’s available. To learn more, please visit https://docs.microsoft.com/MicrosoftTeams/sharing-files-in-teams.
Dan M
supported this idea
·
-
17 votesDan M
shared this idea
·
-
6 votesDan M
supported this idea
·
An error occurred while saving the comment Dan M
commented
This is also needed because in highly managed environments with audit and regulatory concerns, we need to centrally manage and approve all access change requests. This means the process is handled outside of Teams (because there are many systems that require access management) and it handled in tools such as ServiceNow with pre-defined processes and workflows. End users are NOT owners of teams. So this feature essentially just creates a black hole for requests to fall into which is outside of the enterprise process.
-
20 votes
An error occurred while saving the comment Dan M
commented
You can disable the option for end users to create m365 groups (which is the foundation of a Team). You would then have to centrally manage Team creation in IT or by another group of users that has been delegated the privs to do it.
-
8 votes
An error occurred while saving the comment Dan M
commented
It is likely a configuration issue, either in your tenant or theirs.
- Validate all DNS records are properly configured
- Ensure both organizations are on Teams and validate which upgrade mode the users are in.
- Ensure that external access is enabled in both tenants and that there are not any domain restrictions. -
5 votesDan M
shared this idea
·
-
17 votesDan M
supported this idea
·
Need to add a global windows shortcut, that is easy to use and will allow you to toggle your mute status in Teams even when the Teams app does not have focus. This is very common when people are on calls and have multiple monitors.