Troubleshooting Microsoft Teams

이 페이지는 아직 한국어로 제공되지 않습니다. 번역 작업 중입니다.
현재 번역 프로젝트에 대한 질문이나 피드백이 있으신 경우 언제든지 연락주시기 바랍니다.

Overview

This guide addresses common issues and FAQs for the Datadog Microsoft Teams integration, including missing teams, syncing channels, private channel support, user mentions, incident troubleshooting, and prompt resolution.

The team doesn’t show up in the integration tile

If you added the bot to the team before adding the tenant to Datadog, then Datadog would have missed the team join event to know that the team exists. You can try to either:

  • Synchronize your team standard channels to Datadog by running a sync command from any standard channel for that team
  • Remove the app from the team, then add it back again

Synchronize your team standard channels to Datadog

  1. Navigate to a standard channel in the Team that you want to synchronize.
  2. Start a post on the channel.
  3. Type @ sync, select the app, and then choose the sync command.
  4. Post the message to the channel and wait for a confirmation in the thread indicating success.

Remove and re-add app

This removes configured connectors for that team. Perform this action only when you are ready to migrate all connectors for that team to Datadog's tenant-based integration.
  1. Click the three dots next to the Team name in the left sidebar.
  2. Click Manage Team.
  3. Go to the tab labelled Apps.
  4. Click the three dots next to the app.
  5. Click Remove.
  6. Re-add the app by following the setup steps.

Bot support for private channels

Private channels are not supported by the bot, due to the private channel limitations in Microsoft Teams. If you want to send notifications to private channels, see Microsoft Workflows Webhooks.

Troubleshooting Incident features when using delegated permissions

First, ensure that the service account user is a member of the team that the feature is being used in.

  • If an incident tab is not being created, ensure that you have allowed members to create, update, and remove tabs in channels in that team.
  • If new incident channels are not being created or renamed, ensure that you have allowed members to create and update channels in that team.
  • If incident channels are not being archived, ensure that you have allowed members to delete and restore channels in that team.

Lastly, it is possible that the delegated user’s token has expired or been revoked. If that’s the case, re-connect the delegated user.

App configuration prompts when declaring an incident

If you are seeing a prompt when decalring an incident, verify the following:

  • Your app version is 3.1.23 or higher. See instructions on how to update your app version.
  • If you’re using application permissions, ensure you have granted the TeamsTab.Create application permission
  • If you’re using delegated permissions, ensure you have granted the TeamsTab.Create and TeamsTab.Read.All delegated permissions.
  • If you’re using delegated permissions, ensure that the service account is a member of the team you’re running the @Datadog incident command in.

You can also declare an incident by clicking the + sign at the top of a channel and searching for the Datadog app.

Limitations for US1-FED

  • Government Community Cloud (GCC) and GCC High tenants are not supported by the app. The Datadog for Government app only supports Datadog US1-FED customers who are trying to connect to their commercial Microsoft Teams tenant.
  • Datadog Incident management features are not supported.

Further reading