How can we make Microsoft Teams better?

← Public

Webhook needs to support forced notification a la "@channel", "@team", "@person"

Webhooks should have a property to force notification a la "@channel", "@team", "@person". I have been using Slack webhooks for notifications out of our monitoring platform and can use "@" tags to make sure that the correct channels get the data and if the condition is severe, notify "@channel".

1,250 votes
Sign in
(thinking…)
Sign in with: Facebook Google
Forgot password?
Create a password
Signed in as (Sign out)
Close
Close

We’ll send you updates on this idea

Paul Davis shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

187 comments

Sign in
(thinking…)
Sign in with: Facebook Google
Forgot password?
Create a password
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • Callum. commented  ·   ·  Flag as inappropriate

    If it helps anybody, after looking in to this and seeing it couldn't be done (still!?), a workaround for me was to change the channel notification settings to banner + feed for all new posts for relevant users in the channel. This eliminates the need to use the tag (if tagging the team).

  • Brian Seekford commented  ·   ·  Flag as inappropriate

    Welcome to 2020. Well over a year since last update. Is Teams managed and developed by like 2 guys in a basement in Siberia who are only allowed to surface every once in a while to check on features? It seems like all the features I need for integration have these we will update when we know statuses that are so outdated it makes it look like the company is out of business. Insane. Idea shared, 2016. Updated 2018. Here it is starting out 2020. Let the folks out of the basement. Maybe hire some people.

  • Marc commented  ·   ·  Flag as inappropriate

    The status of this request needs updating from "Under Review". Even if it is to "Rejected" then people can make more strategic decisions about whether to stick with Teams or not for automated targeted messaging.

  • Dave H commented  ·   ·  Flag as inappropriate

    I'm baffled that this is not yet available. I integrated some DevOps pipelines with Teams two years ago and found this feature missing. Circled back because of some new integrations to find it is still not available. If people aren't aware that there is something they need to look at it's almost pointless to put the message there.

  • Rob commented  ·   ·  Flag as inappropriate

    Under Review for over a year to implement this. It's a pretty essential portion of what many of us in a corporate setting would like to use for a chat tool.

  • Josh Wingstrom commented  ·   ·  Flag as inappropriate

    What more needs reviewed!?! My understanding is this is available via flows with <at>name@domain</at>. If y'all can't get this together, reach out and we'll implement it for you.

  • Rich Mawdsley commented  ·   ·  Flag as inappropriate

    Started building a webhook for Teams.. 10 minutes later find it didnt have this basic functionalitly. Off to Slack I go.

  • Aliaksei commented  ·   ·  Flag as inappropriate

    It is under review for a year, but it seems really small in comparison with other suggestions.

1 3 5 … 9 10

Forum Home

Reference Information for Teams

Public: Developer Platform

Categories

Feedback and Knowledge Base

(thinking…)

More Teams Information