From a4ee67139a8b8a67720df987ad5d701d5f8fc52f Mon Sep 17 00:00:00 2001 From: Esther Kim Date: Mon, 10 Nov 2025 14:49:01 -0500 Subject: [PATCH 1/9] Merge conflicts --- config/_default/menus/main.en.yaml | 12 ++ .../incident_settings/integrations.md | 49 +---- .../integrations/_index.md | 3 +- .../integrations/microsoft_teams/_index.md | 180 ++++++++++++++++++ 4 files changed, 196 insertions(+), 48 deletions(-) create mode 100644 content/en/service_management/incident_management/integrations/microsoft_teams/_index.md diff --git a/config/_default/menus/main.en.yaml b/config/_default/menus/main.en.yaml index 0a978c2138c9b..a63760b095717 100644 --- a/config/_default/menus/main.en.yaml +++ b/config/_default/menus/main.en.yaml @@ -2525,6 +2525,7 @@ menu: parent: incidents_integrations identifier: incidents_integrations_jira weight: 901 +<<<<<<< HEAD - name: Slack url: service_management/incident_management/integrations/slack parent: incidents_integrations @@ -2539,6 +2540,17 @@ menu: url: service_management/incident_management/integrations/statuspage parent: incidents_integrations identifier: incidents_integrations_statuspage +======= + - name: Microsoft Teams + url: service_management/incident_management/integrations/microsoft_teams + parent: incidents_integrations + identifier: incidents_microsoft_teams + weight: 902 + - name: Statuspage + url: service_management/incident_management/integrations/statuspage + parent: incidents_integrations + identifier: incidents_statuspage +>>>>>>> 184b5fb736 (Move MS Teams from Settings to Integrations) weight: 904 - name: On-Call url: service_management/on-call/ diff --git a/content/en/service_management/incident_management/incident_settings/integrations.md b/content/en/service_management/incident_management/incident_settings/integrations.md index 70fdd639ed037..c5998d9beb3ba 100644 --- a/content/en/service_management/incident_management/incident_settings/integrations.md +++ b/content/en/service_management/incident_management/incident_settings/integrations.md @@ -24,53 +24,7 @@ For a full overview of Slack configuration options in Datadog Incident Managemen ## Microsoft Teams -To use Incident Management's Microsoft Teams features, you must first [install the Microsoft Teams integration for Datadog][5]. - -After you do that, go to **[Service Management > Incidents > Settings > Integrations][2]** to configure the Microsoft Teams features for Incident Management. - -### Declaring and managing incidents in Microsoft Teams - -To declare or manage an incident from a specific team: -1. [Add the Datadog application][6] to the team. -2. Add the **Datadog** tab to any channel in that team. -3. From this tab, declare incidents and manage existing ones (for example, update fields, impacts, and responders). - -**Note**: In an incident channel, the tab shows and lets you manage the incident associated with that channel. In other channels, you can only declare new incidents. - -### Incident channels - -#### Automatic channel creation - -You can configure Incident Management to automatically create an incident Microsoft Teams channel for each incident or for incidents meeting criteria you define. - -After you enable this automation, you can define a **channel name template** for Datadog to follow when creating the channel. The following variables are available in channel name templates: - -* `{{public_id}}`: Incident's numeric ID -* `{{title}}`: Incident's title -* `{{created}}`: Incident's creation date in format MM_DD_YYYY -* `{{yyyy}}`: Incident's four-digit creation year -* `{{mm}}`: Incident's two-digit creation month -* `{{dd}}`: Incident's two-digit creation day of month -* `{{random_adjective}}`: Random adjective -* `{{random_noun}}`: Random noun - -#### Channel message syncing - -You can configure Incident Management to push all incident Microsoft Teams channel messages to the incident timeline. - -The author of a synced message does not need an Incident Management or Incident Response seat for the message to be recorded. In organizations with usage-based billing for Incident Management, the author is not counted as a monthly active user. - -#### Other incident channel features - -You can configure Incident Management to: - -* Automatically archive an incident channel after the incident is resolved - -### Other Microsoft Teams features - -*Send incident updates to a global channel*: You can configure Incident Management to notify a selected channel when an incident's state, severity, title, or incident commander changes. - -To customize this behavior, deactivate this setting and [define a notification rule][7] instead. +For a full overview of Microsoft Teams configuration options in Datadog Incident Management, including incident declaration, channel automation, message syncing, responder management, and notification settings, see [Integrate Microsoft Teams with Datadog Incident Management][17]. ## Other integrations @@ -104,3 +58,4 @@ In addition to integrating with Slack and Microsoft Teams, Incident Management a [14]: /integrations/statuspage/ [15]: /integrations/servicenow/ [16]: /integrations/zoom_incident_management/ +[17]: /service_management/incident_management/integrations/microsoft_teams \ No newline at end of file diff --git a/content/en/service_management/incident_management/integrations/_index.md b/content/en/service_management/incident_management/integrations/_index.md index f04af4d18503d..5592b41ce0eb0 100644 --- a/content/en/service_management/incident_management/integrations/_index.md +++ b/content/en/service_management/incident_management/integrations/_index.md @@ -24,10 +24,11 @@ Configure and manage incident-related integrations from the **Incident Settings* ## Setup {{< whatsnext desc="Set up and use the following integrations within the context of Datadog Incident Management:">}} + {{< nextlink href="/service_management/incident_management/integrations/atlassian_statuspage" >}}Atlassian Statuspage{{< /nextlink >}} {{< nextlink href="/service_management/incident_management/integrations/jira" >}}Jira{{< /nextlink >}} + {{< nextlink href="/service_management/incident_management/integrations/microsoft_teams" >}}Microsoft Teams{{< /nextlink >}} {{< nextlink href="/service_management/incident_management/integrations/slack" >}}Slack{{< /nextlink >}} {{< nextlink href="/service_management/incident_management/integrations/status_pages" >}}Status Pages{{< /nextlink >}} - {{< nextlink href="/service_management/incident_management/integrations/statuspage" >}}Atlassian Statuspage{{< /nextlink >}} {{< /whatsnext >}} ## Further reading diff --git a/content/en/service_management/incident_management/integrations/microsoft_teams/_index.md b/content/en/service_management/incident_management/integrations/microsoft_teams/_index.md new file mode 100644 index 0000000000000..c86c15f297e2c --- /dev/null +++ b/content/en/service_management/incident_management/integrations/microsoft_teams/_index.md @@ -0,0 +1,180 @@ +--- +title: Integrate Microsoft Teams with Datadog Incident Management +further_reading: +- link: "logs/processing/pipelines" + tag: "Documentation" + text: "Log processing pipelines" +--- +To use Incident Management's Microsoft Teams features, you must first [install the Microsoft Teams integration for Datadog][6]. + +After you do that, go to **[Service Management > Incidents > Settings > Integrations][2]** to configure the Microsoft Teams features for Incident Management. + +### Declaring and managing incidents in Microsoft Teams + +To declare or manage an incident from a specific team: +1. [Add the Datadog application][7] to the team. +2. Add the **Datadog** tab to any channel in that team. +3. From this tab, declare incidents and manage existing ones (for example, update fields, impacts, and responders). + +**Note**: In an incident channel, the tab shows and lets you manage the incident associated with that channel. In other channels, you can only declare new incidents. + +### Incident channels + +#### Automatic channel creation + +You can configure Incident Management to automatically create an incident Microsoft Teams channel for each incident or for incidents meeting criteria you define. + +After you enable this automation, you can define a **channel name template** for Datadog to follow when creating the channel. The following variables are available in channel name templates: + +* `{{public_id}}`: Incident's numeric ID +* `{{title}}`: Incident's title +* `{{created}}`: Incident's creation date in format MM_DD_YYYY +* `{{yyyy}}`: Incident's four-digit creation year +* `{{mm}}`: Incident's two-digit creation month +* `{{dd}}`: Incident's two-digit creation day of month +* `{{random_adjective}}`: Random adjective +* `{{random_noun}}`: Random noun + +#### Channel message syncing + +You can configure Incident Management to push all incident Microsoft Teams channel messages to the incident timeline. + +The author of a synced message does not need an Incident Management or Incident Response seat for the message to be recorded. In organizations with usage-based billing for Incident Management, the author is not counted as a monthly active user. + +#### Other incident channel features + +You can configure Incident Management to: + +* Automatically archive an incident channel after the incident is resolved + +### Other Microsoft Teams features + +*Send incident updates to a global channel*: You can configure Incident Management to notify a selected channel when an incident's state, severity, title, or incident commander changes. + +To customize this behavior, deactivate this setting and [define a notification rule][5] instead. + +## Other integrations + +In addition to integrating with Slack and Microsoft Teams, Incident Management also integrates with: + +- [PagerDuty][8] and [Opsgenie][9] to send incident notifications to your on-call engineers. +- [CoScreen][10] to launch collaborative meetings with multi-user screen sharing, remote control, and built-in audio and video chat. +- [Jira][11] to create a Jira ticket for an incident. +- [Webhooks][12] to send incident notifications using webhooks (for example, [sending SMS to Twilio][13]). +- [Statuspage][14] to create and update Statuspage incidents. +- [ServiceNow][15] to create a ServiceNow ticket for an incident. +- [Zoom][16] to create Zoom meetings for an incident. + +--- + +Integrations page + +### Incident Usage + +#### Incidents + +To declare a new incident from Microsoft Teams: + +1. Start a conversation in a channel in any team, or a chat with the Datadog app. +2. Type `@Datadog incident` +3. An adaptive card appears. Click the **Declare Incident** button to open the Datadog tab and declare an incident. + +A user must connect their Microsoft Teams account to their Datadog account to declare an incident. + +To update an incident, follow a similar process as creation: + +1. Start a conversation while in an incident team. +2. Type `@Datadog` or use the `...` button to open the **Messaging extensions** menu and select the **Datadog** App. +3. Select **Update Incident**. +4. Complete the form with your desired information. +5. Click **Update**. + +List all open (active and stable) incidents with: + +``` +@Datadog list incidents +``` + +Use the "More actions" menu on any message inside an incident team on the far right to send that message to the incident Timeline. + +#### Incident updates channel + +Using an incident updates channel provides your stakeholders with organization-wide visibility into the status of all incidents directly from Microsoft Teams. Select which team and channel in your account to post these updates to, and the channel receives the following posts: + +- Newly declared incidents. +- Changes to severity, status transition, and incident commander. +- Links to the incident's overview page in App. +- Link to join the dedicated incident team. + +Once the Microsoft Teams App has been installed, you can navigate to the **Incident Settings** page. From this, you can scroll down to the **Incident Updates** Channel section and begin the set-up flow. + +#### How to set up an incident channel: + +1. Navigate to [Incidents Settings][304]. +2. Under the Microsoft Teams section, select your connected Microsoft Teams tenant. +3. Toggle on **Automatically create a Microsoft Teams channel for every incident**. +4. Select the Team in which you want to automatically create new channels. +5. Save your settings. + +{{< img src="integrations/microsoft_teams/ms_teams_incident_updates_v2.png" alt="Microsoft Teams Incident Update Channel Settings." >}} + +#### Enabling one-click Microsoft Teams meetings + +Delegated permissions are required for one-click Microsoft Teams meetings. To enable one-click Microsoft Teams meetings for incidents: + +1. Navigate to [Incident Settings][304]. +2. Under the Microsoft Teams section, select your connected Microsoft Teams tenant. +3. Toggle on **Enable meeting creation**. +4. Save your settings. + +After enabling one-click Microsoft Teams meetings, start a meeting by clicking **Start Teams Meeting** from the incident header. + +You are redirected to instantly join the meeting through the browser. + +![ms_teams_one_click_meeting](images/microsoft_teams_create_one_click_meetings.png) + +#### Enabling automatic meeting creation + +Delegated permissions are required for automatic, criteria-based Microsoft Teams meetings. To enable automatic, criteria-based Microsoft Teams meetings for incidents: + +1. Navigate to [Incident Settings][304]. +2. Under the Microsoft Teams section, select your connected Microsoft Teams tenant. +3. Toggle on **Enable meeting creation**. + 1. Toggle on **Automatically create Microsoft Teams meetings**. + 2. (Optional) Specify the incident criteria that creates a Microsoft Teams meeting. If left blank, any changes to an incident without an existing Microsoft Teams meeting will create a Microsoft Teams meeting. +4. Save your settings. + +![ms_teams_automatic_meeting](images/microsoft_teams_enable_automatic_meeting_creation.png) + +## Further reading + +{{< partial name="whats-next/whats-next.html" >}} + +[1]: https://app.datadoghq.com/integrations +[2]: https://app.datadoghq.com/incidents/settings#Integrations +[3]: /integrations/slack/?tab=slackapplicationbeta#using-the-slack-app +[4]: /service_management/on-call/ +[5]: /service_management/incident_management/incident_settings/notification_rules +[6]: /integrations/microsoft-teams/?tab=datadogapprecommended +[7]: /integrations/microsoft-teams/?tab=datadogapprecommended#datadog-incident-management-in-microsoft-teams +[8]: /integrations/pagerduty/ +[9]: /integrations/opsgenie/ +[10]: /coscreen +[11]: /integrations/jira/ +[12]: /integrations/webhooks/ +[13]: /integrations/webhooks/#sending-sms-through-twilio +[14]: /integrations/statuspage/ +[15]: /integrations/servicenow/ +[16]: /integrations/zoom_incident_management/ + +[301]: https://docs.datadoghq.com/monitors/notify/#notification +[302]: https://docs.datadoghq.com/help/ +[303]: /integrations/microsoft-teams +[304]: /incidents/settings#Integrations +[305]: https://learn.microsoft.com/en-us/azure/active-directory/manage-apps/grant-admin-consent?pivots=ms-graph#prerequisites +[306]: https://learn.microsoft.com/en-us/graph/permissions-reference +[307]: https://docs.datadoghq.com/dashboards/sharing/scheduled_reports/ +[308]: https://learn.microsoft.com/en-us/microsoftteams/app-permissions#what-can-apps-do-in-teams +[309]: https://learn.microsoft.com/en-us/microsoftteams/private-channels#private-channel-limitations +[3010]: https://devblogs.microsoft.com/microsoft365dev/retirement-of-office-365-connectors-within-microsoft-teams/ +[3011]: https://learn.microsoft.com/en-us/graph/permissions-overview \ No newline at end of file From 6e285daa259e1045a6711b94cd1419b1934e552a Mon Sep 17 00:00:00 2001 From: Esther Kim Date: Mon, 10 Nov 2025 15:00:04 -0500 Subject: [PATCH 2/9] Consolidate integration info --- .../integrations/microsoft_teams/_index.md | 187 ++++++++---------- 1 file changed, 80 insertions(+), 107 deletions(-) diff --git a/content/en/service_management/incident_management/integrations/microsoft_teams/_index.md b/content/en/service_management/incident_management/integrations/microsoft_teams/_index.md index c86c15f297e2c..ffa92c4a96b79 100644 --- a/content/en/service_management/incident_management/integrations/microsoft_teams/_index.md +++ b/content/en/service_management/incident_management/integrations/microsoft_teams/_index.md @@ -1,87 +1,48 @@ --- title: Integrate Microsoft Teams with Datadog Incident Management further_reading: -- link: "logs/processing/pipelines" +- link: "/service_management/incident_management/incident_settings/integrations" tag: "Documentation" - text: "Log processing pipelines" + text: "Incident Integrations Settings" +- link: "/integrations/microsoft-teams" + tag: "Documentation" + text: "Microsoft Teams Integration" --- -To use Incident Management's Microsoft Teams features, you must first [install the Microsoft Teams integration for Datadog][6]. - -After you do that, go to **[Service Management > Incidents > Settings > Integrations][2]** to configure the Microsoft Teams features for Incident Management. - -### Declaring and managing incidents in Microsoft Teams - -To declare or manage an incident from a specific team: -1. [Add the Datadog application][7] to the team. -2. Add the **Datadog** tab to any channel in that team. -3. From this tab, declare incidents and manage existing ones (for example, update fields, impacts, and responders). - -**Note**: In an incident channel, the tab shows and lets you manage the incident associated with that channel. In other channels, you can only declare new incidents. - -### Incident channels - -#### Automatic channel creation - -You can configure Incident Management to automatically create an incident Microsoft Teams channel for each incident or for incidents meeting criteria you define. - -After you enable this automation, you can define a **channel name template** for Datadog to follow when creating the channel. The following variables are available in channel name templates: - -* `{{public_id}}`: Incident's numeric ID -* `{{title}}`: Incident's title -* `{{created}}`: Incident's creation date in format MM_DD_YYYY -* `{{yyyy}}`: Incident's four-digit creation year -* `{{mm}}`: Incident's two-digit creation month -* `{{dd}}`: Incident's two-digit creation day of month -* `{{random_adjective}}`: Random adjective -* `{{random_noun}}`: Random noun - -#### Channel message syncing - -You can configure Incident Management to push all incident Microsoft Teams channel messages to the incident timeline. - -The author of a synced message does not need an Incident Management or Incident Response seat for the message to be recorded. In organizations with usage-based billing for Incident Management, the author is not counted as a monthly active user. - -#### Other incident channel features -You can configure Incident Management to: +## Overview -* Automatically archive an incident channel after the incident is resolved +The Microsoft Teams integration for Datadog Incident Management enables you to declare and manage incidents, automatically create incident channels, sync messages to timelines, and keep your team informed, all from within Microsoft Teams. -### Other Microsoft Teams features +## Setup -*Send incident updates to a global channel*: You can configure Incident Management to notify a selected channel when an incident's state, severity, title, or incident commander changes. +To use Incident Management's Microsoft Teams features, you must first [install the Microsoft Teams integration for Datadog][1]. -To customize this behavior, deactivate this setting and [define a notification rule][5] instead. - -## Other integrations +After installation, go to **[Service Management > Incidents > Settings > Integrations][2]** to configure the Microsoft Teams features for Incident Management. -In addition to integrating with Slack and Microsoft Teams, Incident Management also integrates with: +## Declaring and managing incidents -- [PagerDuty][8] and [Opsgenie][9] to send incident notifications to your on-call engineers. -- [CoScreen][10] to launch collaborative meetings with multi-user screen sharing, remote control, and built-in audio and video chat. -- [Jira][11] to create a Jira ticket for an incident. -- [Webhooks][12] to send incident notifications using webhooks (for example, [sending SMS to Twilio][13]). -- [Statuspage][14] to create and update Statuspage incidents. -- [ServiceNow][15] to create a ServiceNow ticket for an incident. -- [Zoom][16] to create Zoom meetings for an incident. - ---- +### From the Datadog tab -Integrations page +To declare or manage an incident from a specific team: +1. [Add the Datadog application][3] to the team. +2. Add the **Datadog** tab to any channel in that team. +3. From this tab, declare incidents and manage existing ones (for example, update fields, impacts, and responders). -### Incident Usage +**Note**: In an incident channel, the tab shows and lets you manage the incident associated with that channel. In other channels, you can only declare new incidents. -#### Incidents +### Using @mentions -To declare a new incident from Microsoft Teams: +To declare a new incident from Microsoft Teams using @mentions: 1. Start a conversation in a channel in any team, or a chat with the Datadog app. -2. Type `@Datadog incident` +2. Type `@Datadog incident`. 3. An adaptive card appears. Click the **Declare Incident** button to open the Datadog tab and declare an incident. -A user must connect their Microsoft Teams account to their Datadog account to declare an incident. +**Note**: A user must connect their Microsoft Teams account to their Datadog account to declare an incident. -To update an incident, follow a similar process as creation: +### Updating incidents + +To update an incident: 1. Start a conversation while in an incident team. 2. Type `@Datadog` or use the `...` button to open the **Messaging extensions** menu and select the **Datadog** App. @@ -89,28 +50,27 @@ To update an incident, follow a similar process as creation: 4. Complete the form with your desired information. 5. Click **Update**. +### Listing incidents + List all open (active and stable) incidents with: ``` @Datadog list incidents ``` -Use the "More actions" menu on any message inside an incident team on the far right to send that message to the incident Timeline. +### Sending messages to the timeline -#### Incident updates channel +Use the "More actions" menu on any message inside an incident team on the far right to send that message to the incident timeline. -Using an incident updates channel provides your stakeholders with organization-wide visibility into the status of all incidents directly from Microsoft Teams. Select which team and channel in your account to post these updates to, and the channel receives the following posts: +## Incident channels -- Newly declared incidents. -- Changes to severity, status transition, and incident commander. -- Links to the incident's overview page in App. -- Link to join the dedicated incident team. +### Automatic channel creation -Once the Microsoft Teams App has been installed, you can navigate to the **Incident Settings** page. From this, you can scroll down to the **Incident Updates** Channel section and begin the set-up flow. +You can configure Incident Management to automatically create an incident Microsoft Teams channel for each incident or for incidents meeting criteria you define. -#### How to set up an incident channel: +To set up automatic incident channel creation: -1. Navigate to [Incidents Settings][304]. +1. Navigate to [Incident Settings][4]. 2. Under the Microsoft Teams section, select your connected Microsoft Teams tenant. 3. Toggle on **Automatically create a Microsoft Teams channel for every incident**. 4. Select the Team in which you want to automatically create new channels. @@ -118,63 +78,76 @@ Once the Microsoft Teams App has been installed, you can navigate to the **Incid {{< img src="integrations/microsoft_teams/ms_teams_incident_updates_v2.png" alt="Microsoft Teams Incident Update Channel Settings." >}} -#### Enabling one-click Microsoft Teams meetings +After you enable this automation, you can define a **channel name template** for Datadog to follow when creating the channel. The following variables are available in channel name templates: + +* `{{public_id}}`: Incident's numeric ID +* `{{title}}`: Incident's title +* `{{created}}`: Incident's creation date in format MM_DD_YYYY +* `{{yyyy}}`: Incident's four-digit creation year +* `{{mm}}`: Incident's two-digit creation month +* `{{dd}}`: Incident's two-digit creation day of month +* `{{random_adjective}}`: Random adjective +* `{{random_noun}}`: Random noun + +### Channel message syncing + +You can configure Incident Management to push all incident Microsoft Teams channel messages to the incident timeline. + +The author of a synced message does not need an Incident Management or Incident Response seat for the message to be recorded. In organizations with usage-based billing for Incident Management, the author is not counted as a monthly active user. + +### Automatic channel archiving + +You can configure Incident Management to automatically archive an incident channel after the incident is resolved. + +## Microsoft Teams meetings + +### One-click meeting creation Delegated permissions are required for one-click Microsoft Teams meetings. To enable one-click Microsoft Teams meetings for incidents: -1. Navigate to [Incident Settings][304]. +1. Navigate to [Incident Settings][4]. 2. Under the Microsoft Teams section, select your connected Microsoft Teams tenant. 3. Toggle on **Enable meeting creation**. 4. Save your settings. -After enabling one-click Microsoft Teams meetings, start a meeting by clicking **Start Teams Meeting** from the incident header. +After enabling one-click Microsoft Teams meetings, start a meeting by clicking **Start Teams Meeting** from the incident header. You are redirected to instantly join the meeting through the browser. -You are redirected to instantly join the meeting through the browser. +{{< img src="path/to/your/image-name-here.png" alt="Your image description" style="width:100%;" >}} -![ms_teams_one_click_meeting](images/microsoft_teams_create_one_click_meetings.png) + -#### Enabling automatic meeting creation +### Automatic meeting creation Delegated permissions are required for automatic, criteria-based Microsoft Teams meetings. To enable automatic, criteria-based Microsoft Teams meetings for incidents: -1. Navigate to [Incident Settings][304]. +1. Navigate to [Incident Settings][4]. 2. Under the Microsoft Teams section, select your connected Microsoft Teams tenant. 3. Toggle on **Enable meeting creation**. 1. Toggle on **Automatically create Microsoft Teams meetings**. 2. (Optional) Specify the incident criteria that creates a Microsoft Teams meeting. If left blank, any changes to an incident without an existing Microsoft Teams meeting will create a Microsoft Teams meeting. 4. Save your settings. -![ms_teams_automatic_meeting](images/microsoft_teams_enable_automatic_meeting_creation.png) +{{< img src="path/to/your/image-name-here.png" alt="Your image description" style="width:100%;" >}} + + + +## Incident updates channel + +Using an incident updates channel provides your stakeholders with organization-wide visibility into the status of all incidents directly from Microsoft Teams. Select which team and channel in your account to post these updates to, and the channel receives the following posts: + +- Newly declared incidents +- Changes to severity, status transition, and incident commander +- Links to the incident's overview page in App +- Link to join the dedicated incident team + +To customize this behavior, deactivate this setting and [define a notification rule][5] instead. ## Further reading {{< partial name="whats-next/whats-next.html" >}} -[1]: https://app.datadoghq.com/integrations +[1]: /integrations/microsoft-teams/?tab=datadogapprecommended [2]: https://app.datadoghq.com/incidents/settings#Integrations -[3]: /integrations/slack/?tab=slackapplicationbeta#using-the-slack-app -[4]: /service_management/on-call/ +[3]: /integrations/microsoft-teams/?tab=datadogapprecommended#datadog-incident-management-in-microsoft-teams +[4]: /incidents/settings#Integrations [5]: /service_management/incident_management/incident_settings/notification_rules -[6]: /integrations/microsoft-teams/?tab=datadogapprecommended -[7]: /integrations/microsoft-teams/?tab=datadogapprecommended#datadog-incident-management-in-microsoft-teams -[8]: /integrations/pagerduty/ -[9]: /integrations/opsgenie/ -[10]: /coscreen -[11]: /integrations/jira/ -[12]: /integrations/webhooks/ -[13]: /integrations/webhooks/#sending-sms-through-twilio -[14]: /integrations/statuspage/ -[15]: /integrations/servicenow/ -[16]: /integrations/zoom_incident_management/ - -[301]: https://docs.datadoghq.com/monitors/notify/#notification -[302]: https://docs.datadoghq.com/help/ -[303]: /integrations/microsoft-teams -[304]: /incidents/settings#Integrations -[305]: https://learn.microsoft.com/en-us/azure/active-directory/manage-apps/grant-admin-consent?pivots=ms-graph#prerequisites -[306]: https://learn.microsoft.com/en-us/graph/permissions-reference -[307]: https://docs.datadoghq.com/dashboards/sharing/scheduled_reports/ -[308]: https://learn.microsoft.com/en-us/microsoftteams/app-permissions#what-can-apps-do-in-teams -[309]: https://learn.microsoft.com/en-us/microsoftteams/private-channels#private-channel-limitations -[3010]: https://devblogs.microsoft.com/microsoft365dev/retirement-of-office-365-connectors-within-microsoft-teams/ -[3011]: https://learn.microsoft.com/en-us/graph/permissions-overview \ No newline at end of file From 40eb207768c93258a3a7794aa383c7442894846e Mon Sep 17 00:00:00 2001 From: Esther Kim Date: Mon, 10 Nov 2025 19:29:53 -0500 Subject: [PATCH 3/9] Fix links --- .../integrations/microsoft_teams/_index.md | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) diff --git a/content/en/service_management/incident_management/integrations/microsoft_teams/_index.md b/content/en/service_management/incident_management/integrations/microsoft_teams/_index.md index 41a7890a4d53f..645ba8cbc6e81 100644 --- a/content/en/service_management/incident_management/integrations/microsoft_teams/_index.md +++ b/content/en/service_management/incident_management/integrations/microsoft_teams/_index.md @@ -58,7 +58,7 @@ Use the "More actions" menu on any message inside an incident team on the far ri You can configure Incident Management to automatically create an incident Microsoft Teams channel for each incident or for incidents meeting criteria you define. To set up automatic incident channel creation: -1. Navigate to [Incident Settings][4] and select **Microsoft Teams**. +1. Navigate to [Incident Settings][2] and select **Microsoft Teams**. 2. From the **Tenant** dropdown, select your connected Microsoft Teams tenant. 3. Toggle on **Automatically create a Microsoft Teams channel for every incident**. 4. Select the Team in which you want to automatically create new channels. @@ -91,7 +91,7 @@ You can configure Incident Management to automatically archive an incident chann Delegated permissions are required for one-click Microsoft Teams meetings. To enable one-click Microsoft Teams meetings for incidents: -1. Navigate to [Incident Settings][4]. +1. Navigate to [Incident Settings][2]. 2. In Microsoft Teams, select your connected Microsoft Teams tenant. 3. Toggle on **Enable meeting creation**. 4. Save your settings. @@ -102,7 +102,7 @@ After enabling one-click Microsoft Teams meetings, start a meeting by clicking * Delegated permissions are required for automatic, criteria-based Microsoft Teams meetings. To enable automatic, criteria-based Microsoft Teams meetings for incidents: -1. Navigate to [Incident Settings][4]. +1. Navigate to [Incident Settings][2]. 2. In Microsoft Teams, select your connected Microsoft Teams tenant. 3. Toggle on **Enable meeting creation**. 1. Toggle on **Automatically create Microsoft Teams meetings**. @@ -118,7 +118,7 @@ Using an incident updates channel provides your stakeholders with organization-w - Links to the incident's overview page in App - Link to join the dedicated incident team -To customize this behavior, deactivate this setting and [define a notification rule][5] instead. +To customize this behavior, deactivate this setting and [define a notification rule][4] instead. ## Further reading @@ -127,5 +127,4 @@ To customize this behavior, deactivate this setting and [define a notification r [1]: /integrations/microsoft-teams/?tab=datadogapprecommended [2]: https://app.datadoghq.com/incidents/settings#Integrations [3]: /integrations/microsoft-teams/?tab=datadogapprecommended#datadog-incident-management-in-microsoft-teams -[4]: /incidents/settings#Integrations -[5]: /service_management/incident_management/incident_settings/notification_rules +[4]: /service_management/incident_management/incident_settings/notification_rules \ No newline at end of file From b97fb034c4eec730a16591b47ffd3d12cf55dbc0 Mon Sep 17 00:00:00 2001 From: Esther Kim Date: Tue, 11 Nov 2025 09:34:40 -0500 Subject: [PATCH 4/9] Reorder content --- .../integrations/microsoft_teams/_index.md | 66 +++++++++---------- 1 file changed, 33 insertions(+), 33 deletions(-) diff --git a/content/en/service_management/incident_management/integrations/microsoft_teams/_index.md b/content/en/service_management/incident_management/integrations/microsoft_teams/_index.md index 645ba8cbc6e81..f854a36122d8b 100644 --- a/content/en/service_management/incident_management/integrations/microsoft_teams/_index.md +++ b/content/en/service_management/incident_management/integrations/microsoft_teams/_index.md @@ -19,39 +19,6 @@ To use Incident Management's Microsoft Teams features, you must first [install t After installation, go to **[Service Management > Incidents > Settings > Integrations][2]** to configure the Microsoft Teams features for Incident Management. -## Declaring and managing incidents from Microsoft Teams - -To declare or manage an incident from a specific team: -1. [Add the Datadog application][3] to the team. -1. Add the **Datadog** tab to any channel in that team. -1. Start a conversation in a channel, or a chat with the Datadog app. -1. Type `@Datadog incident`. -1. An adaptive card appears. Click the **Declare Incident** button to open the Datadog tab and declare an incident. - -**Note**: In an incident channel (a channel created specifically for an incident) the Datadog tab displays that specific incident's information and allows you to manage it. In non-incident-specific channels, you can only declare new incidents. - -### Updating incidents - -To update an incident: - -1. Start a conversation while in an incident team. -2. Type `@Datadog` or use the `...` button to open the **Messaging extensions** menu and select the **Datadog** App. -3. Select **Update Incident**. -4. Complete the form with your desired information. -5. Click **Update**. - -### Listing incidents - -List all open (active and stable) incidents with: - -``` -@Datadog list incidents -``` - -### Sending messages to the timeline - -Use the "More actions" menu on any message inside an incident team on the far right to send that message to the incident timeline. - ## Incident channels ### Automatic channel creation @@ -120,6 +87,39 @@ Using an incident updates channel provides your stakeholders with organization-w To customize this behavior, deactivate this setting and [define a notification rule][4] instead. +## Declaring and managing incidents from Microsoft Teams + +To declare or manage an incident from a specific team: +1. [Add the Datadog application][3] to the team. +1. Add the **Datadog** tab to any channel in that team. +1. Start a conversation in a channel, or a chat with the Datadog app. +1. Type `@Datadog incident`. +1. An adaptive card appears. Click the **Declare Incident** button to open the Datadog tab and declare an incident. + +**Note**: In an incident channel (a channel created specifically for an incident) the Datadog tab displays that specific incident's information and allows you to manage it. In non-incident-specific channels, you can only declare new incidents. + +### Updating incidents + +To update an incident: + +1. Start a conversation while in an incident team. +2. Type `@Datadog` or use the `...` button to open the **Messaging extensions** menu and select the **Datadog** App. +3. Select **Update Incident**. +4. Complete the form with your desired information. +5. Click **Update**. + +### Listing incidents + +List all open (active and stable) incidents with: + +``` +@Datadog list incidents +``` + +### Sending messages to the timeline + +Use the "More actions" menu on any message inside an incident team on the far right to send that message to the incident timeline. + ## Further reading {{< partial name="whats-next/whats-next.html" >}} From 2366c829cca9392906a4dfd8ab4021ef7e8bb95a Mon Sep 17 00:00:00 2001 From: Esther Kim Date: Tue, 11 Nov 2025 09:38:53 -0500 Subject: [PATCH 5/9] Update main.en.yaml --- config/_default/menus/main.en.yaml | 4 ---- 1 file changed, 4 deletions(-) diff --git a/config/_default/menus/main.en.yaml b/config/_default/menus/main.en.yaml index e25ed605b6522..2fe4c7366121b 100644 --- a/config/_default/menus/main.en.yaml +++ b/config/_default/menus/main.en.yaml @@ -2539,10 +2539,6 @@ menu: url: service_management/incident_management/integrations/statuspage parent: incidents_integrations identifier: incidents_integrations_statuspage - - name: Statuspage - url: service_management/incident_management/integrations/statuspage - parent: incidents_integrations - identifier: incidents_statuspage weight: 904 - name: Microsoft Teams url: service_management/incident_management/integrations/microsoft_teams From df9f08fdc7cef464431bbf7ee67f12bd0d27c141 Mon Sep 17 00:00:00 2001 From: Esther Kim Date: Wed, 12 Nov 2025 15:58:11 -0500 Subject: [PATCH 6/9] Remove unnecessary instructions --- .../incident_management/incident_settings/integrations.md | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/content/en/service_management/incident_management/incident_settings/integrations.md b/content/en/service_management/incident_management/incident_settings/integrations.md index c5998d9beb3ba..d1fcabde9c474 100644 --- a/content/en/service_management/incident_management/incident_settings/integrations.md +++ b/content/en/service_management/incident_management/incident_settings/integrations.md @@ -16,10 +16,6 @@ Then, configure the integration for Incident Management by navigating to [**Inci ## Slack -To use Incident Management's Slack features, you must first [install the Slack integration for Datadog][3]. - -Then, go to **[Service Management > Incidents > Settings > Integrations][2]** to configure the Slack features for Incident Management. - For a full overview of Slack configuration options in Datadog Incident Management, including incident declaration, channel automation, message syncing, responder management, and notification settings, see the [Slack integration documentation][4]. ## Microsoft Teams @@ -58,4 +54,4 @@ In addition to integrating with Slack and Microsoft Teams, Incident Management a [14]: /integrations/statuspage/ [15]: /integrations/servicenow/ [16]: /integrations/zoom_incident_management/ -[17]: /service_management/incident_management/integrations/microsoft_teams \ No newline at end of file +[17]: /service_management/incident_management/integrations/microsoft_teams From dc396a7e247d941a14278e93bd6f3da10843fe6d Mon Sep 17 00:00:00 2001 From: Esther Kim Date: Wed, 12 Nov 2025 17:14:58 -0500 Subject: [PATCH 7/9] Apply suggestions from code review --- .../integrations/_index.md | 6 +- .../integrations/microsoft_teams/_index.md | 75 ++++++++++++------- 2 files changed, 53 insertions(+), 28 deletions(-) diff --git a/content/en/service_management/incident_management/integrations/_index.md b/content/en/service_management/incident_management/integrations/_index.md index 5592b41ce0eb0..1d50e371cddec 100644 --- a/content/en/service_management/incident_management/integrations/_index.md +++ b/content/en/service_management/incident_management/integrations/_index.md @@ -24,11 +24,11 @@ Configure and manage incident-related integrations from the **Incident Settings* ## Setup {{< whatsnext desc="Set up and use the following integrations within the context of Datadog Incident Management:">}} - {{< nextlink href="/service_management/incident_management/integrations/atlassian_statuspage" >}}Atlassian Statuspage{{< /nextlink >}} - {{< nextlink href="/service_management/incident_management/integrations/jira" >}}Jira{{< /nextlink >}} - {{< nextlink href="/service_management/incident_management/integrations/microsoft_teams" >}}Microsoft Teams{{< /nextlink >}} {{< nextlink href="/service_management/incident_management/integrations/slack" >}}Slack{{< /nextlink >}} + {{< nextlink href="/service_management/incident_management/integrations/microsoft_teams" >}}Microsoft Teams{{< /nextlink >}} + {{< nextlink href="/service_management/incident_management/integrations/jira" >}}Jira{{< /nextlink >}} {{< nextlink href="/service_management/incident_management/integrations/status_pages" >}}Status Pages{{< /nextlink >}} + {{< nextlink href="/service_management/incident_management/integrations/statuspage" >}}Atlassian Statuspage{{< /nextlink >}} {{< /whatsnext >}} ## Further reading diff --git a/content/en/service_management/incident_management/integrations/microsoft_teams/_index.md b/content/en/service_management/incident_management/integrations/microsoft_teams/_index.md index f854a36122d8b..7b317dcb41b18 100644 --- a/content/en/service_management/incident_management/integrations/microsoft_teams/_index.md +++ b/content/en/service_management/incident_management/integrations/microsoft_teams/_index.md @@ -52,6 +52,18 @@ The author of a synced message does not need an Incident Management or Incident You can configure Incident Management to automatically archive an incident channel after the incident is resolved. +## Global channel for incident updates + +Use an incident updates channel to provide your stakeholders with organization-wide visibility into the status of all incidents directly from Microsoft Teams. + +1. In Datadog, navigate to [**Incidents > Settings > Integrations**][2]. +1. Select the Microsoft Teams integration and enable **Send all incident updates to a global channel**. +1. Select the Team and channel where you want the incident updates to be posted. + +Datadog automatically notifies the selected channel about any newly declared incidents, as well as changes to incident states, severities, and incident commanders. + +To customize this behavior, deactivate this setting and [define a notification rule][4] instead. + ## Microsoft Teams meetings ### One-click meeting creation @@ -76,27 +88,18 @@ Delegated permissions are required for automatic, criteria-based Microsoft Teams 2. (Optional) Specify the incident criteria that creates a Microsoft Teams meeting. If left blank, any changes to an incident without an existing Microsoft Teams meeting will create a Microsoft Teams meeting. 4. Save your settings. -## Incident updates channel - -Using an incident updates channel provides your stakeholders with organization-wide visibility into the status of all incidents directly from Microsoft Teams. Select which team and channel in your account to post these updates to, and the channel receives the following posts: - -- Newly declared incidents -- Changes to severity, status transition, and incident commander -- Links to the incident's overview page in App -- Link to join the dedicated incident team - -To customize this behavior, deactivate this setting and [define a notification rule][4] instead. - ## Declaring and managing incidents from Microsoft Teams -To declare or manage an incident from a specific team: +In an incident channel (a channel created specifically for an incident) the Datadog tab displays that specific incident's information and allows you to manage it. In non-incident channels, you can only declare new incidents. + +To declare an incident from a specific team: 1. [Add the Datadog application][3] to the team. -1. Add the **Datadog** tab to any channel in that team. -1. Start a conversation in a channel, or a chat with the Datadog app. -1. Type `@Datadog incident`. -1. An adaptive card appears. Click the **Declare Incident** button to open the Datadog tab and declare an incident. +1. In any **non-incident** channel, click on the **Datadog** tab. +1. Fill out the incident details and click **Declare Incident**. -**Note**: In an incident channel (a channel created specifically for an incident) the Datadog tab displays that specific incident's information and allows you to manage it. In non-incident-specific channels, you can only declare new incidents. +To manage an incident from a specific team: +1. In an **incident channel**, click on the **Datadog** tab. +1. Edit the incident details and attributes. ### Updating incidents @@ -108,18 +111,40 @@ To update an incident: 4. Complete the form with your desired information. 5. Click **Update**. -### Listing incidents - -List all open (active and stable) incidents with: - -``` -@Datadog list incidents -``` - ### Sending messages to the timeline Use the "More actions" menu on any message inside an incident team on the far right to send that message to the incident timeline. +## Microsoft Teams commands + +You can view the full list of available commands at any time by typing `@Datadog help` in Microsoft Teams. + + + + + + + + + + + + + + + + + + + + + + + + +
CategoryCommandDescription
Global commands (run anywhere)@Datadog incidentDeclare a new incident.
@Datadog list incidentsShow a list of all open incidents.
@Datadog helpShow all supported commands.
+ + ## Further reading {{< partial name="whats-next/whats-next.html" >}} From d1d22129d132262a2858dba45b9237d71ef9cae1 Mon Sep 17 00:00:00 2001 From: Esther Kim Date: Mon, 17 Nov 2025 09:59:37 -0500 Subject: [PATCH 8/9] Add description and remove incorrect info --- .../integrations/microsoft_teams/_index.md | 11 +---------- 1 file changed, 1 insertion(+), 10 deletions(-) diff --git a/content/en/service_management/incident_management/integrations/microsoft_teams/_index.md b/content/en/service_management/incident_management/integrations/microsoft_teams/_index.md index 7b317dcb41b18..14ebe69cb898a 100644 --- a/content/en/service_management/incident_management/integrations/microsoft_teams/_index.md +++ b/content/en/service_management/incident_management/integrations/microsoft_teams/_index.md @@ -1,5 +1,6 @@ --- title: Integrate Microsoft Teams with Datadog Incident Management +description: Integrate Microsoft Teams with Datadog Incident Management to automate incident channel creation, synchronize messages, and collaborate with your team directly within Microsoft Teams. further_reading: - link: "/service_management/incident_management/incident_settings/integrations" tag: "Documentation" @@ -101,16 +102,6 @@ To manage an incident from a specific team: 1. In an **incident channel**, click on the **Datadog** tab. 1. Edit the incident details and attributes. -### Updating incidents - -To update an incident: - -1. Start a conversation while in an incident team. -2. Type `@Datadog` or use the `...` button to open the **Messaging extensions** menu and select the **Datadog** App. -3. Select **Update Incident**. -4. Complete the form with your desired information. -5. Click **Update**. - ### Sending messages to the timeline Use the "More actions" menu on any message inside an incident team on the far right to send that message to the incident timeline. From ccb4ee0a382a945774c7713f2d9d6abbc80d0c84 Mon Sep 17 00:00:00 2001 From: Esther Kim Date: Mon, 17 Nov 2025 10:08:21 -0500 Subject: [PATCH 9/9] Update the header structure for Datadog in MS teams section --- .../integrations/microsoft_teams/_index.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/content/en/service_management/incident_management/integrations/microsoft_teams/_index.md b/content/en/service_management/incident_management/integrations/microsoft_teams/_index.md index 14ebe69cb898a..515353d4f9f47 100644 --- a/content/en/service_management/incident_management/integrations/microsoft_teams/_index.md +++ b/content/en/service_management/incident_management/integrations/microsoft_teams/_index.md @@ -89,10 +89,12 @@ Delegated permissions are required for automatic, criteria-based Microsoft Teams 2. (Optional) Specify the incident criteria that creates a Microsoft Teams meeting. If left blank, any changes to an incident without an existing Microsoft Teams meeting will create a Microsoft Teams meeting. 4. Save your settings. -## Declaring and managing incidents from Microsoft Teams +## Using the Datadog tab in Microsoft Teams In an incident channel (a channel created specifically for an incident) the Datadog tab displays that specific incident's information and allows you to manage it. In non-incident channels, you can only declare new incidents. +### Declaring and managing incidents + To declare an incident from a specific team: 1. [Add the Datadog application][3] to the team. 1. In any **non-incident** channel, click on the **Datadog** tab.