Send monitor notifications to a Microsoft Teams channel

Connect your Microsoft tenant to Datadog.

1. In Datadog, navigate to Integrations > Microsoft Teams.
2. Click Add Tenant, which redirects you to Microsoft.
3. Follow the prompts and click OK.

Once the bot has been added to the team, configure the notification handle in Datadog.

1. Under a configured tenant, click Add Handle. Give the handle a name, select the desired team and channel from the drop-down menus, and click Save.

Migrate legacy connectors to tenant-based integration

Microsoft has announced that Office 365 connectors for Microsoft Teams are being deprecated. This has the following effects:

• All Datadog Connectors will stop working on January 31, 2025.
• Incoming Webhook Connectors without updated URLs will stop working on January 31, 2025.
• All connectors will stop working on December 31, 2025 (previously October 1, 2024).

See Microsoft’s blog post for more information.

To migrate all notification handles currently using the legacy Office 365 connectors over to Datadog’s tenant-based integration:

Usage

From a Datadog monitor, send a notification to Microsoft Teams using the @-notification feature. Send the notification to the address @teams-<HANDLE>, replacing <HANDLE> with the name of your Microsoft Teams handle. To mute a triggered monitor from Microsoft Teams, click Mute Monitor, select a Mute Duration, and click Mute.

User mentions

User mentions allow you to notify specific users in your Microsoft Teams channels when monitor alerts are triggered. This helps ensure that the right people are notified about important events. To mention a specific user, follow the steps below to find their User Principal Name (UPN).

Syntax: <at>{User Principal Name}</at>

Example: <at>user@microsoft.com</at>

Complete notification example: @teams-CHANNEL_NAME <at>user@microsoft.com</at> <at>another.user@microsoft.com</at>

To find a user’s User Principal Name (UPN):

1. Method 1 (only works if UPN matches email):

   • In Microsoft Teams, click on the user’s profile picture or name to open their contact card.
   • The email shown in the Chat field is often the UPN. If they differ, use Method 2 below.

2. Method 2 (always works, but requires Azure Portal permissions):

   • Sign in to the Microsoft Azure Portal.
   • Navigate to Microsoft Entra ID > Manage > Users
   • Locate the user in the list and copy their UPN from the User principal name column.

Datadog recommends testing your monitor notifications to ensure reliable delivery. See Test notifications for instructions.

Dashboards

You can post dashboard widget snapshots on any team or chat. For a list of supported widgets, see Scheduled Reports.

To share a dashboard widget in Teams:

1. In Datadog, hover over a dashboard widget and press CMD + C or CTRL + C, or click the Copy button from the share menu.
2. Paste the link into Teams.

Limit edit access

By default, all users have full access to connected Microsoft Teams tenants.

Use Granular Access Control to limit which roles can edit a specific tenant:

1. While viewing a tenant, click the gear icon in the upper-right corner to open the settings menu.
2. Select Permissions.
3. Click Restrict Access. The dialog box updates to show that members of your organization have Viewer access by default.
4. Use the dropdown to select one or more roles, teams, or users that can edit the Microsoft Teams tenant.
5. Click Add. The dialog box updates to show that the role you selected has the Editor permission.
6. Click Save.

Note: To maintain your edit access to the tenant, you must include at least one role you belong to before saving.

If you have edit access, you can restore general access to a restricted tenant by completing the following steps:

1. While viewing the tenant, click the gear icon in the upper-right corner to open the settings menu.
2. Select Permissions.
3. Click Restore Full Access.
4. Click Save.

To edit tenant permissions through the API:

1. Navigate to the Microsoft Teams integration tile.
2. Click the Tenants tab.
3. Copy the tenant ID shown for the selected tenant.
4. Use the Restriction Policies API, where the Resource Type is integration-account and the id is microsoft-teams:<tenant_id>.

What are Microsoft Workflows Webhooks?

Workflows / Power Automate is a Microsoft product for creating automated workflows. Microsoft Workflows can be used to send notifications with incoming webhooks. If you are unable to install the Datadog app in your Microsoft Teams tenant (recommended), or you want to send notifications to private channels, you can configure Datadog handles to send notifications to Microsoft Teams channels through Microsoft Workflows. This integration is intended for use with the following Microsoft Workflows template: Post to a channel when a webhook request is received

Are you migrating legacy connectors to the Microsoft Workflows Webhooks integration?

Microsoft has announced that Office 365 connectors for Microsoft Teams are being deprecated, and existing connector URLs will stop working on January 31, 2025. Microsoft promotes using incoming webhooks from Microsoft Workflows as a replacement for legacy connectors. Follow the steps below to migrate all notification handles currently using legacy Office 365 connectors over to Datadog’s Microsoft Workflows webhooks integration.

For each legacy notification connector handle in the Microsoft Teams Integration Tile:

1. Follow the setup steps to create a workflow webhook handle for the desired Microsoft Teams channel.
2. Under the Microsoft Workflows Webhooks section, give the new handle the same name as the connector handle it should replace. For example, if your legacy connector handle is named channel-123, name your new handle in the Microsoft Workflows Webhooks section with the name channel-123. This new handle overrides the existing legacy connector handle.

Create a Microsoft Workflows Webhook

Prerequisites

• When creating a new workflow, a Microsoft account is required for both ownership of the workflow and sending notifications to channels (these do not need to be the same Microsoft account).
• The account that owns the workflow (configured in step 2 below) is the account that can edit and renew the workflow. For easier shared access, use a service account.
• The account that sends notifications to channels (configured in step 8 below) posts as the user of the account. This account must be part of the team that you want to send notifications to. If sending notifications to a private channel, then this account must be also be added to the channel. If you want to give this account a name like “Datadog Notifications,” use a service account.

Instructions

Note: Most of these steps are in Microsoft Workflows. As Microsoft makes changes to Workflows, the steps below may not reflect the most recent changes.

1. In Microsoft Teams, add the Workflows app to all teams you want to notify. If you are unable to add the app to your team, follow the instructions in the “Private channels” section below.

2. Create a new workflow in Power Automate from Microsoft’s Post to a channel when a webhook request is received template.

3. Choose the Microsoft account that you would like to use to own the workflow (use a service account for easier shared access), then click Continue.

4. Click Edit in advanced mode.

5. Expand Send each adaptive card, then click Post card in a chat or channel.

6. Use the Post As dropdown to set Post as to Flow bot. Notifications will appear to be sent by “<NAME> via Workflows”. To receive these notifications, the Workflows application must be added to the desired team. If sending notifications to a private channel, Post As must be set to a user in the channel. See the “Private channels” section below for more information. Note: Changing Post as will reset the Post in field.

7. To access the team and channel drop-downs, remove the @ symbols by deleting them or clicking the X icons.

8. Use the drop-downs to select the desired team and channel.

9. Ensure that the workflow is connected to the intended Microsoft account for sending notifications (such as a service account named “Datadog Notifications”). Notifications will appear to be sent by “<NAME> through Workflows”. This account must have access to the configured Microsoft Teams channel. To change the account, click Change connection and follow the prompts to configure another Microsoft account.

10. Click the Save button.

11. To find your webhook link, click the first block of the workflow.

12. Make sure that Anyone can trigger the flow, and then copy the link.

13. Click the Back button to navigate to the dashboard for the workflow.

14. Ensure that the workflow is on by checking the dashboard. If it is off, click the “Turn on” button.

15. In Datadog, navigate to Integrations > Microsoft Teams.

16. On the Configuration tab, go to the Microsoft Workflows Webhooks section and click Add Handle. Give the handle a name (if migrating from a legacy connector handle, use the same name as the corresponding connector handle), and paste the webhook URL.

17. Click Save.

Private channels

To send notifications to private channels, the account configured within the Post Card to chat or channel block must have access to the channel. This enables the workflow to send notifications on behalf of that user account.

1. Within the Post Card to chat or channel block, change Post as to User.

2. Then to choose the account, click Change connection and follow the prompts to change the account.

Limitations

• If you are a Microsoft 365 customer, workflows will automatically turn off after 90 days of no successful triggers. When a workflow is nearing expiration, Microsoft sends an email to the account that owns the workflow. This 90 day timer can be reset by running a test within Microsoft Workflows.

• When using the template, all messages are appended with a line of text stating who created the workflow along with a link to the template.

  To remove this, go to your workflow and click Save As to make a copy, navigate to the copy by finding it within My Flows, and use the new webhook from the copied workflow instead of the original workflow.

• Microsoft Workflows does not support interactive features for the messages that it posts (such as muting monitors directly from Microsoft Teams).

• Microsoft Workflows does not support shared channels.

• Microsoft Workflows does not support user mentions when posting a Workflows Webhook as a User.

Usage

From a Datadog monitor, send a notification to Microsoft Teams using the @-notification feature. Send the notification to the address @teams-<HANDLE>, replacing <HANDLE> with the name of your Microsoft Teams handle.

User mentions with Microsoft Workflows Webhooks handles

User mentions allow you to notify specific users in your Microsoft Teams channels when monitor alerts are triggered. This helps ensure that the right people are notified about important events. To mention a specific user, follow the steps below to find their User Principal Name (UPN).

Syntax: <at>{User Principal Name}</at>

Example: <at>user@microsoft.com</at>

Complete notification example: @teams-CHANNEL_NAME <at>user@microsoft.com</at> <at>another.user@microsoft.com</at>

To find a user’s User Principal Name (UPN):

1. Method 1 (only works if UPN matches email):

   • In Microsoft Teams, click on the user’s profile picture or name to open their contact card.
   • The email shown in the Chat field is often the UPN. If they differ, use Method 2 below.

2. Method 2 (always works, but requires Azure Portal permissions):

   • Sign in to the Microsoft Azure Portal.
   • Navigate to Microsoft Entra ID > Manage > Users
   • Locate the user in the list and copy their UPN from the User principal name column.

Datadog recommends testing your monitor notifications to ensure reliable delivery, see Test notifications for instructions.

Limit edit access

By default, all users have full access to each Microsoft Workflows webhook handle.

Use Granular Access Control to limit which roles can edit a specific Workflows webhook handle:

1. While viewing the Workflows Webhooks, hover over a handle to reveal actions on the right side of the row.
2. Click the lock icon labeled Permissions.
3. Click Restrict Access. The dialog box updates to show that members of your organization have Viewer access by default.
4. Use the dropdown to select one or more roles, teams, or users that can edit the Workflows webhook handle.
5. Click Add. The dialog box updates to show that the role you selected has the Editor permission.
6. Click Save.

Note: To maintain your edit access to the Workflows webhook handle, you must include at least one role you belong to before saving.

If you have edit access, you can restore general access to a restricted Workflows webhook handle by completing the following steps:

1. While viewing the Workflows Webhooks, hover over the restricted handle to reveal actions on the right side of the row.
2. Click the lock icon labeled Permissions.
3. Click Restore Full Access.
4. Click Save.

To edit Workflows Webhooks permissions through the API:

1. Fetch the Workflows Webhooks IDs using the Microsoft Teams Integration API.
2. Use the Restriction Policies API, where the Resource Type is integration-webhook and the id is microsoft-teams:<workflows_webhook_id>.

Migrate legacy connectors to tenant-based integration

Microsoft has announced that Office 365 connectors for Microsoft Teams are being deprecated. This has the following effects:

• All Datadog Connectors will stop working on January 31, 2025.
• Incoming Webhook Connectors without updated URLs will stop working on January 31, 2025.
• All connectors will stop working on December 31, 2025 (previously October 1, 2024).

See Microsoft’s blog post for more information.

To migrate all notification handles currently using the legacy Office 365 connectors over to the tenant-based Datadog app:

Migrate from legacy connectors to the Microsoft Workflows Webhooks integration

Microsoft has announced that Office 365 connectors for Microsoft Teams are being deprecated. This has the following effects:

• All Datadog Connectors will stop working on January 31, 2025.
• Incoming Webhook Connectors without updated URLs will stop working on January 31, 2025.
• All connectors will stop working on December 31, 2025 (previously October 1, 2024).

See Microsoft’s blog post for more information.

To migrate all notification handles currently using the legacy Office 365 connectors over to Datadog’s Microsoft Workflows webhooks integration, see Microsoft Workflows Webhooks.

Connector setup (deprecated)

1. Choose the ... button next to the channel name in the list of channels and then choose Connectors.

2. Search for Datadog and click Configure.

3. In the connector configuration modal, copy the webhook URL.

4. In Datadog, navigate to Integrations > Microsoft Teams.

5. On the Configuration tab, click Add Handle, give the handle a name, and paste the webhook URL.

6. In the connector configuration modal, click Save.