Dan M
My feedback
-
2 votesDan M
shared this idea
·
-
1 vote0 comments · Public » Apps, Connectors, Messaging Extensions · Flag idea as inappropriate… · Admin →Dan M
shared this idea
·
-
39,351 votes
Thank 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 votesDan M
shared this idea
·
-
181 votesDan M
supported this idea
·
An error occurred while saving the comment -
1 voteDan M
shared this idea
·
-
17 votesDan M
supported this idea
·
-
466 votesDan M
supported this idea
·
-
396 votesDan M
supported this idea
·
-
2,502 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,281 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
·
-
8 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.
-
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. -
4 votesDan M
shared this idea
·
-
16 votesDan M
supported this idea
·
-
13,635 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
·
-
2 votesDan M
shared this idea
·
-
5,059 votes
As part of our commitment to being customer driven, we’d love your input on top features that will improve your satisfaction with teams and channels navigation, and help you be more productive in Teams. Please access the survey here: https://forms.office.com/Pages/ResponsePage.aspx?id=v4j5cvGGr0GRqy180BHbR7hW7rKdVrVInUSM809cvrtUNFhLRVNJVVhaUFI0WEJHVTA4MlpGWVZUSS4u
Thanks for your feedback!
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.