Microsoft Teams

Create an incoming webhook URL

To post a Microsoft Teams notification, you need to create an incoming webhook URL. To create the incoming webhook URL, follow the steps mentioned here.

Configuring a Microsoft Teams destination

You can configure a Microsoft Teams destination in the Destinations tab. As part of the configuration, enter the Microsoft Teams Incoming Webhook URL.

Configuring an Microsoft Teams subscription

Create a subscription to associate the Microsoft Teams destination to a topic.

How do Microsoft Teams notification from Event Notifications looks

Event notification generates Microsoft Teams notifications from incoming payload. The template event notification use to send to Microsoft Teams looks like following -

{
   "type": "message",
   "attachments": [
      {
         "contentType": "application/vnd.microsoft.card.adaptive",
         "content": {
            "type": "AdaptiveCard",
            "body": [
               {
                  "items": [
                     {
                        "size": "large",
                        "text": "{{event.ibmendefaultshort}}",
                        "type": "TextBlock"
                     }
                  ],
                  "type": "Container"
               },
               {
                  "text": "{{event.ibmendefaultlong}}",
                  "type": "TextBlock",
                  "weight": "Bolder",
                  "wrap": true
               },
               {
                  "actions": [
                     {
                        "targetElements": [
                           "stacktrace"
                        ],
                        "title": "Show Data",
                        "type": "Action.ToggleVisibility"
                     }
                  ],
                  "type": "ActionSet"
               },
               {
                  "id": "stacktrace",
                  "isVisible": false,
                  "items": [
                     {
                        "fontType": "monospace",
                        "isSubtle": true,
                        "size": "Small",
                        "text": "{{event.data}}",
                        "type": "TextBlock",
                        "weight": "Bolder",
                        "wrap": true
                     }
                  ],
                  "type": "Container"
               }
            ],
            "$schema": "http://adaptivecards.io/schemas/adaptive-card.json",
            "version": "1.4"
         }
      }
   ]
}

Here -

ibmendefaultshort is the default short payload provided in the incoming payload. ibmendefaultlong is tbe default long payload provided in the incoming payload. data is the data JSON provided in the incoming payload and will be formated as json in the Microsoft Teams notification.

Testing a Microsoft™ Teams destination configuration

You can test a Microsoft™ Teams destination in the options menu provided againts the destination. You can effortlessly test a destination, whether the provided configuration is correct or not with a single click.

For more information on testing a destination, see here.

Microsoft Teams retry policy

When publishing an Microsoft Teams notification, issues such as network errors and application glitches can cause the requests to fail. A retry is used to provide resiliency to external requests. Attempt to retry the requests in such situations by using the following values:

• Limit = 60 seconds: total time that the service retries.
• Step = 5 seconds: after each failure, the service waits 5 seconds before retrying. This delay prevents bombarding of the external services (webhook).

In addition, the following timeout conditions cause the Microsoft Teams call to fail:

• A connection timeout of 10 seconds
• A response timeout of 60 seconds

If a call to the Microsoft Teams webhook URL fails even after retry attempts, the notification is lost.