From 14c73eef24c24c241361a356b237dc6978ee1d1a Mon Sep 17 00:00:00 2001 From: Esther Kim Date: Tue, 23 Dec 2025 11:56:18 -0500 Subject: [PATCH 1/4] Move troubleshooting information to separate guide --- content/en/integrations/guide/_index.md | 1 + .../guide/microsoft_teams_troubleshooting.md | 83 +++++++++++++++++++ 2 files changed, 84 insertions(+) create mode 100644 content/en/integrations/guide/microsoft_teams_troubleshooting.md diff --git a/content/en/integrations/guide/_index.md b/content/en/integrations/guide/_index.md index a606969dfc1..40fc888d2b1 100644 --- a/content/en/integrations/guide/_index.md +++ b/content/en/integrations/guide/_index.md @@ -31,6 +31,7 @@ cascade: {{< nextlink href="integrations/guide/application-monitoring-vmware-tanzu" tag=" VMWare Tanzu" >}}Datadog Application Monitoring for VMware Tanzu{{< /nextlink >}} {{< nextlink href="integrations/guide/cluster-monitoring-vmware-tanzu" tag=" VMWare Tanzu" >}}Datadog Cluster Monitoring for VMware Tanzu{{< /nextlink >}} {{< nextlink href="integrations/guide/fips-integrations" tag=" fips" >}}FIPS Verified Agent Integrations{{< /nextlink >}} + {{< nextlink href="integrations/guide/microsoft_teams_troubleshooting" tag=" Microsoft Teams" >}}Troubleshooting Microsoft Teams{{< /nextlink >}} {{< /header-list >}} {{< header-list header="AWS guides" >}} diff --git a/content/en/integrations/guide/microsoft_teams_troubleshooting.md b/content/en/integrations/guide/microsoft_teams_troubleshooting.md new file mode 100644 index 00000000000..10fbf91b597 --- /dev/null +++ b/content/en/integrations/guide/microsoft_teams_troubleshooting.md @@ -0,0 +1,83 @@ +--- +title: Troubleshooting Microsoft Teams +description: Troubleshooting steps and solutions for issues with the Microsoft Teams integration. +further_reading: +- link: "https://docs.datadoghq.com/integrations/microsoft-teams/?tab=datadogapprecommended" + tag: "Documentation" + text: "Datadog Microsoft Teams Integration" +- link: "https://app.datadoghq.com/integrations?integrationId=microsoft-teams" + tag: "App" + text: "Microsoft Teams Integration Tile" +--- + +## 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 {{< region-param key="microsoft_teams_app_name" >}} 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 `@{{< region-param key="microsoft_teams_app_name" >}} sync`, select the `{{< region-param key="microsoft_teams_app_name" >}}` 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 readd {{< region-param key="microsoft_teams_app_name" >}} 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 {{< region-param key="microsoft_teams_app_name" >}} app. +5. Click **Remove**. +6. Re-add the {{< region-param key="microsoft_teams_app_name" >}} app by following the [setup steps][16]. + + +## Bot support for private channels + +Private channels are not supported by the bot, due to the private channel limitations in [Microsoft Teams][9]. If you want to send notifications to private channels, see [Microsoft Workflows Webhooks][12]. + +## Adding multiple user mentions in monitor notifications + +
When multiple user mentions are included in a notification and one is invalid, the valid users will still receive notifications, but invalid user mentions may cause the mentions to appear out of order.
+ +To include multiple user mentions in a single notification and ensure all relevant team members are notified, use the following format: + +```text +@teams-handle user1@microsoft.com user2@microsoft.com user3@microsoft.com +``` + +## 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 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][13]. +- 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 + +- 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 + +{{< partial name="whats-next/whats-next.html" >}} + From 9f7d63658366d405da024d4e3786e4d484281ed0 Mon Sep 17 00:00:00 2001 From: Esther Kim Date: Tue, 23 Dec 2025 12:13:52 -0500 Subject: [PATCH 2/4] Fix links --- .../guide/microsoft_teams_troubleshooting.md | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/content/en/integrations/guide/microsoft_teams_troubleshooting.md b/content/en/integrations/guide/microsoft_teams_troubleshooting.md index 10fbf91b597..7ad45af6ad8 100644 --- a/content/en/integrations/guide/microsoft_teams_troubleshooting.md +++ b/content/en/integrations/guide/microsoft_teams_troubleshooting.md @@ -36,12 +36,12 @@ You can try to either: 3. Go to the tab labelled **Apps**. 4. Click the three dots next to the {{< region-param key="microsoft_teams_app_name" >}} app. 5. Click **Remove**. -6. Re-add the {{< region-param key="microsoft_teams_app_name" >}} app by following the [setup steps][16]. +6. Re-add the {{< region-param key="microsoft_teams_app_name" >}} app by following the [setup steps][1]. ## Bot support for private channels -Private channels are not supported by the bot, due to the private channel limitations in [Microsoft Teams][9]. If you want to send notifications to private channels, see [Microsoft Workflows Webhooks][12]. +Private channels are not supported by the bot, due to the private channel limitations in [Microsoft Teams][2]. If you want to send notifications to private channels, see [Microsoft Workflows Webhooks][3]. ## Adding multiple user mentions in monitor notifications @@ -65,7 +65,7 @@ Lastly, it is possible that the delegated user's token has expired or been revok ## 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][13]. +- Your app version is 3.1.23 or higher. See instructions on how to [update your app version][4]. - 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. @@ -81,3 +81,7 @@ You can also declare an incident by clicking the `+` sign at the top of a channe {{< partial name="whats-next/whats-next.html" >}} +[1]: /integrations/microsoft-teams/?tab=datadogapprecommended#setup +[2]: https://learn.microsoft.com/microsoftteams/private-channels#private-channel-limitations +[3]: /integrations/microsoft-teams/?tab=microsoftworkflowswebhooks#what-are-microsoft-workflows-webhooks +[4]: https://support.microsoft.com/office/update-an-app-in-microsoft-teams-3d53d136-5c5d-4dfa-9602-01e6fdd8015b \ No newline at end of file From 57433457b7d02dec704e618d123b55c98be082d1 Mon Sep 17 00:00:00 2001 From: Esther Kim Date: Mon, 29 Dec 2025 11:40:23 -0500 Subject: [PATCH 3/4] Format link, remove setup instructions --- .../guide/microsoft_teams_troubleshooting.md | 14 ++------------ 1 file changed, 2 insertions(+), 12 deletions(-) diff --git a/content/en/integrations/guide/microsoft_teams_troubleshooting.md b/content/en/integrations/guide/microsoft_teams_troubleshooting.md index 7ad45af6ad8..a57c794b08f 100644 --- a/content/en/integrations/guide/microsoft_teams_troubleshooting.md +++ b/content/en/integrations/guide/microsoft_teams_troubleshooting.md @@ -2,7 +2,7 @@ title: Troubleshooting Microsoft Teams description: Troubleshooting steps and solutions for issues with the Microsoft Teams integration. further_reading: -- link: "https://docs.datadoghq.com/integrations/microsoft-teams/?tab=datadogapprecommended" +- link: "/integrations/microsoft-teams/?tab=datadogapprecommended" tag: "Documentation" text: "Datadog Microsoft Teams Integration" - link: "https://app.datadoghq.com/integrations?integrationId=microsoft-teams" @@ -43,16 +43,6 @@ You can try to either: Private channels are not supported by the bot, due to the private channel limitations in [Microsoft Teams][2]. If you want to send notifications to private channels, see [Microsoft Workflows Webhooks][3]. -## Adding multiple user mentions in monitor notifications - -
When multiple user mentions are included in a notification and one is invalid, the valid users will still receive notifications, but invalid user mentions may cause the mentions to appear out of order.
- -To include multiple user mentions in a single notification and ensure all relevant team members are notified, use the following format: - -```text -@teams-handle user1@microsoft.com user2@microsoft.com user3@microsoft.com -``` - ## 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. @@ -84,4 +74,4 @@ You can also declare an incident by clicking the `+` sign at the top of a channe [1]: /integrations/microsoft-teams/?tab=datadogapprecommended#setup [2]: https://learn.microsoft.com/microsoftteams/private-channels#private-channel-limitations [3]: /integrations/microsoft-teams/?tab=microsoftworkflowswebhooks#what-are-microsoft-workflows-webhooks -[4]: https://support.microsoft.com/office/update-an-app-in-microsoft-teams-3d53d136-5c5d-4dfa-9602-01e6fdd8015b \ No newline at end of file +[4]: https://support.microsoft.com/office/update-an-app-in-microsoft-teams-3d53d136-5c5d-4dfa-9602-01e6fdd8015b From 813856b249a05154c8a71376e28c230e1bfa0db3 Mon Sep 17 00:00:00 2001 From: Esther Kim Date: Mon, 29 Dec 2025 13:57:30 -0500 Subject: [PATCH 4/4] Apply suggestions from code review Co-authored-by: Alicia Thuerk --- .../guide/microsoft_teams_troubleshooting.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/content/en/integrations/guide/microsoft_teams_troubleshooting.md b/content/en/integrations/guide/microsoft_teams_troubleshooting.md index a57c794b08f..b997fd94502 100644 --- a/content/en/integrations/guide/microsoft_teams_troubleshooting.md +++ b/content/en/integrations/guide/microsoft_teams_troubleshooting.md @@ -27,11 +27,11 @@ You can try to either: 3. Type `@{{< region-param key="microsoft_teams_app_name" >}} sync`, select the `{{< region-param key="microsoft_teams_app_name" >}}` 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 readd {{< region-param key="microsoft_teams_app_name" >}} app +### Remove and re-add {{< region-param key="microsoft_teams_app_name" >}} 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. +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 {{< region-param key="microsoft_teams_app_name" >}} app. @@ -46,8 +46,8 @@ Private channels are not supported by the bot, due to the private channel limita ## 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 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 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. @@ -64,7 +64,7 @@ You can also declare an incident by clicking the `+` sign at the top of a channe ## Limitations for US1-FED -- 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. +- 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