Send alerts to Microsoft Teams

A Microsoft Teams channel posts each Pingstack incident alert as a card in one Teams channel. It uses a Teams Workflows webhook, so there is no app to install or workspace to connect. Microsoft Teams channels are available on every plan. An Editor or Admin can create and change the channel.

Prerequisites

• A Teams channel where you can add a workflow.
• A workflow made from the Send webhook alerts to a channel template (or Post to a channel when a webhook request is received). Copy the HTTP POST URL it shows when you save it. See Microsoft’s guide, Create incoming webhooks with Workflows for Microsoft Teams.

Office 365 connector webhook URLs (on webhook.office.com) no longer work; Microsoft has retired them. Pingstack rejects them with a message asking for a Workflows URL instead.

Create the channel

1. In Teams, open the channel’s … menu, choose Workflows, pick Send webhook alerts to a channel, and copy the URL it gives you.
2. In Pingstack, open Notification channels and choose Add a channel, or choose Add destination on the Microsoft Teams card.
3. Select Microsoft Teams, paste the URL into Workflow URL and choose the notification group.
4. Save, open the channel and choose Send test alert.
5. Assign the notification group to the checks that should post to Teams.

Expected result: Pingstack shows “Test message sent to Microsoft Teams.” The Teams channel shows a Test alert from Pingstack card, and the channel’s recent deliveries list one successful send.

Treat the workflow URL as a secret, because anyone who has it can post to the channel. After saving, Pingstack shows it only as its last four characters, for example Microsoft Teams workflow ••••1234, and never shows it in delivery errors. Leave the field blank when editing to keep the saved URL, or paste a new one to replace it.

Pingstack accepts URLs from the Workflows hosts that Teams uses (logic.azure.com, logic.azure.us and api.powerplatform.com).

What the card shows

Each incident open, status change and recovery posts a new card with:

• The alert, for example “API is now down (HTTP 503).”, in red while the incident is open and green once the check recovers.
• When the incident started and, after recovery, when it resolved.
• The URL, service or DNS name the check watches.
• The cause and probe locations, when there are any.
• A View check button that opens the check in Pingstack.

Delivery failures

Teams rejecting the URL (for example a deleted or turned-off workflow) is not retried; create a new workflow, paste its URL and send a test alert. Rate limits and Teams outages are retried automatically with increasing delays. Every attempt and its error appear in the channel’s recent deliveries and in notification history.

A workflow runs under the account of the person who created it. If that person leaves the organization or loses access to the channel, the workflow can stop posting; recreate it under an account that will stay.