Conversation
…mitation Add a note clarifying that notification rule @-mentions target the Microsoft Teams channel named in the handle, not an incident's automatically created channel, since Teams has no equivalent of @incident-slack-channel.
Contributor
buraizu
reviewed
Sep 15, 2026
buraizu
left a comment
buraizu
left a comment
Collaborator
There was a problem hiding this comment.
Looks good overall, just left a couple of minor suggestions
|
|
||
| To customize this behavior, deactivate this setting and [define a notification rule][4] instead. | ||
|
|
||
| ## Notification targets |
Collaborator
There was a problem hiding this comment.
Suggested change
| ## Notification targets | |
| ## Microsoft Teams notification targets |
The new heading ## Notification targets doesn't name Microsoft Teams, although the cross-link added in notification_rules.md refers to it as "Microsoft Teams notification targets." Suggesting to add it here for better human/AI parsing and retrieval.
|
|
||
| [Notification rules][4] target a Microsoft Teams channel with a `@teams-<channel>` handle, which notifies the specific channel named in the handle. Use this to notify a standing channel, such as the global incident updates channel. | ||
|
|
||
| Incident Management does not provide a handle that resolves to an incident's automatically created channel. Slack notification rules can use `@incident-slack-channel` to notify the incident's Slack channel, but Microsoft Teams has no equivalent handle. As a result, a notification rule that includes `@` mentions delivers them to the channel named in the `@teams-` handle, not to the per-incident channel. |
Collaborator
There was a problem hiding this comment.
Minor suggestion for clarification — looks like this is the form used in this PR's description, as well.
Suggested change
| Incident Management does not provide a handle that resolves to an incident's automatically created channel. Slack notification rules can use `@incident-slack-channel` to notify the incident's Slack channel, but Microsoft Teams has no equivalent handle. As a result, a notification rule that includes `@` mentions delivers them to the channel named in the `@teams-` handle, not to the per-incident channel. | |
| Incident Management does not provide a handle that resolves to an incident's automatically created channel. Slack notification rules can use `@incident-slack-channel` to notify the incident's Slack channel, but Microsoft Teams has no equivalent handle. As a result, a notification rule that includes `@-mentions` delivers them to the channel named in the `@teams-` handle, not to the per-incident channel. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add a note clarifying that notification rule @-mentions target the Microsoft Teams channel named in the handle, not an incident's automatically created channel, since Teams has no equivalent of @incident-slack-channel.
https://datadoghq.atlassian.net/browse/DOCS-15281
What does this PR do? What is the motivation?
Merge readiness