|
| 1 | +--- |
| 2 | +title: Integrate Microsoft Teams with Datadog Incident Management |
| 3 | +description: Integrate Microsoft Teams with Datadog Incident Management to automate incident channel creation, synchronize messages, and collaborate with your team directly within Microsoft Teams. |
| 4 | +further_reading: |
| 5 | +- link: "/service_management/incident_management/incident_settings/integrations" |
| 6 | + tag: "Documentation" |
| 7 | + text: "Incident Integrations Settings" |
| 8 | +- link: "/integrations/microsoft-teams" |
| 9 | + tag: "Documentation" |
| 10 | + text: "Microsoft Teams Integration" |
| 11 | +--- |
| 12 | + |
| 13 | +## Overview |
| 14 | + |
| 15 | +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. |
| 16 | + |
| 17 | +## Prerequisites |
| 18 | + |
| 19 | +To use Incident Management's Microsoft Teams features, you must first [install the Microsoft Teams integration for Datadog][1] and connect your Microsoft Teams account to your Datadog account. |
| 20 | + |
| 21 | +After installation, go to **[Service Management > Incidents > Settings > Integrations][2]** to configure the Microsoft Teams features for Incident Management. |
| 22 | + |
| 23 | +## Incident channels |
| 24 | + |
| 25 | +### Automatic channel creation |
| 26 | + |
| 27 | +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: |
| 28 | + |
| 29 | +1. Navigate to [Incident Settings][2] and select **Microsoft Teams**. |
| 30 | +2. From the **Tenant** dropdown, select your connected Microsoft Teams tenant. |
| 31 | +3. Toggle on **Automatically create a Microsoft Teams channel for every incident**. |
| 32 | +4. Select the Team in which you want to automatically create new channels. |
| 33 | +5. Save your settings. |
| 34 | + |
| 35 | +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: |
| 36 | + |
| 37 | +* `{{public_id}}`: Incident's numeric ID |
| 38 | +* `{{title}}`: Incident's title |
| 39 | +* `{{created}}`: Incident's creation date in format MM_DD_YYYY |
| 40 | +* `{{yyyy}}`: Incident's four-digit creation year |
| 41 | +* `{{mm}}`: Incident's two-digit creation month |
| 42 | +* `{{dd}}`: Incident's two-digit creation day of month |
| 43 | +* `{{random_adjective}}`: Random adjective |
| 44 | +* `{{random_noun}}`: Random noun |
| 45 | + |
| 46 | +### Channel message syncing |
| 47 | + |
| 48 | +You can configure Incident Management to push all incident Microsoft Teams channel messages to the incident timeline. |
| 49 | + |
| 50 | +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. |
| 51 | + |
| 52 | +### Automatic channel archiving |
| 53 | + |
| 54 | +You can configure Incident Management to automatically archive an incident channel after the incident is resolved. |
| 55 | + |
| 56 | +## Global channel for incident updates |
| 57 | + |
| 58 | +Use an incident updates channel to provide your stakeholders with organization-wide visibility into the status of all incidents directly from Microsoft Teams. |
| 59 | + |
| 60 | +1. In Datadog, navigate to [**Incidents > Settings > Integrations**][2]. |
| 61 | +1. Select the Microsoft Teams integration and enable **Send all incident updates to a global channel**. |
| 62 | +1. Select the Team and channel where you want the incident updates to be posted. |
| 63 | + |
| 64 | +Datadog automatically notifies the selected channel about any newly declared incidents, as well as changes to incident states, severities, and incident commanders. |
| 65 | + |
| 66 | +To customize this behavior, deactivate this setting and [define a notification rule][4] instead. |
| 67 | + |
| 68 | +## Microsoft Teams meetings |
| 69 | + |
| 70 | +### One-click meeting creation |
| 71 | + |
| 72 | +Delegated permissions are required for one-click Microsoft Teams meetings. To enable one-click Microsoft Teams meetings for incidents: |
| 73 | + |
| 74 | +1. Navigate to [Incident Settings][2]. |
| 75 | +2. In Microsoft Teams, select your connected Microsoft Teams tenant. |
| 76 | +3. Toggle on **Enable meeting creation**. |
| 77 | +4. Save your settings. |
| 78 | + |
| 79 | +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. |
| 80 | + |
| 81 | +### Automatic meeting creation |
| 82 | + |
| 83 | +Delegated permissions are required for automatic, criteria-based Microsoft Teams meetings. To enable automatic, criteria-based Microsoft Teams meetings for incidents: |
| 84 | + |
| 85 | +1. Navigate to [Incident Settings][2]. |
| 86 | +2. In Microsoft Teams, select your connected Microsoft Teams tenant. |
| 87 | +3. Toggle on **Enable meeting creation**. |
| 88 | + 1. Toggle on **Automatically create Microsoft Teams meetings**. |
| 89 | + 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. |
| 90 | +4. Save your settings. |
| 91 | + |
| 92 | +## Using the Datadog tab in Microsoft Teams |
| 93 | + |
| 94 | +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. |
| 95 | + |
| 96 | +### Declaring and managing incidents |
| 97 | + |
| 98 | +To declare an incident from a specific team: |
| 99 | +1. [Add the Datadog application][3] to the team. |
| 100 | +1. In any **non-incident** channel, click on the **Datadog** tab. |
| 101 | +1. Fill out the incident details and click **Declare Incident**. |
| 102 | + |
| 103 | +To manage an incident from a specific team: |
| 104 | +1. In an **incident channel**, click on the **Datadog** tab. |
| 105 | +1. Edit the incident details and attributes. |
| 106 | + |
| 107 | +### Sending messages to the timeline |
| 108 | + |
| 109 | +Use the "More actions" menu on any message inside an incident team on the far right to send that message to the incident timeline. |
| 110 | + |
| 111 | +## Microsoft Teams commands |
| 112 | + |
| 113 | +You can view the full list of available commands at any time by typing `@Datadog help` in Microsoft Teams. |
| 114 | + |
| 115 | +<table> |
| 116 | + <thead> |
| 117 | + <tr> |
| 118 | + <th scope="col">Category</th> |
| 119 | + <th scope="col">Command</th> |
| 120 | + <th scope="col">Description</th> |
| 121 | + </tr> |
| 122 | + </thead> |
| 123 | + <tbody> |
| 124 | + <tr> |
| 125 | + <td rowspan="3">Global commands (run anywhere)</td> |
| 126 | + <td><code>@Datadog incident</code></td> |
| 127 | + <td>Declare a new incident.</td> |
| 128 | + </tr> |
| 129 | + <tr> |
| 130 | + <td><code>@Datadog list incidents</code></td> |
| 131 | + <td>Show a list of all open incidents.</td> |
| 132 | + </tr> |
| 133 | + <tr> |
| 134 | + <td><code>@Datadog help</code></td> |
| 135 | + <td>Show all supported commands.</td> |
| 136 | + </tr> |
| 137 | + </tbody> |
| 138 | +</table> |
| 139 | + |
| 140 | + |
| 141 | +## Further reading |
| 142 | + |
| 143 | +{{< partial name="whats-next/whats-next.html" >}} |
| 144 | + |
| 145 | +[1]: /integrations/microsoft-teams/?tab=datadogapprecommended |
| 146 | +[2]: https://app.datadoghq.com/incidents/settings#Integrations |
| 147 | +[3]: /integrations/microsoft-teams/?tab=datadogapprecommended#datadog-incident-management-in-microsoft-teams |
| 148 | +[4]: /service_management/incident_management/incident_settings/notification_rules |
0 commit comments