Dan M
My feedback
-
1 vote
Dan M shared this idea ·
-
1 vote
Dan M shared this idea ·
-
5 votes
Dan M shared 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
44,472 votesThank you for your continued feedback. As many people have pointed out, this is available on mobile today. Support for replying to a specific message is on the backlog for desktop. I’ll let you know when we have progress to share. Thanks.
Dan M supported this idea ·
-
-
2 votes
Dan M shared this idea ·
-
292 votes
Dan M supported this idea ·
An error occurred while saving the comment -
1 vote
Dan M shared this idea ·
-
23 votes
Dan M supported this idea ·
-
505 votes
Dan M supported this idea ·
-
428 votes
Dan M supported this idea ·
-
2,569 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,706 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 ·
-
14 votes
Dan M shared this idea ·
-
6 votes
Dan 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.
-
19 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 votes
Dan M shared this idea ·
-
16 votes
Dan M supported this idea ·
-
14,572 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!
Dan M supported this idea ·
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.