Microsoft Teams
Send analysis results to a Microsoft Teams channel using a connector webhook
Connect a Teams channel using an Office 365 Connector webhook URL. SigSentry posts Adaptive Cards into the channel.
This page covers outbound notifications. For inbound slash commands in Teams, see Teams chat triggers.
Prerequisites
| Need | Notes |
|---|---|
| Teams workspace + permission to add connectors | If your org has restricted connectors, ask an admin |
| A target channel | The Teams channel where notifications should land |
Setup walkthrough
Add the Incoming Webhook connector
In Teams, navigate to the channel you want notifications in. Click the three-dot menu next to the channel name and pick Connectors (or Manage channel → Connectors in newer Teams clients).
Search for Incoming Webhook and click Configure.
Configure the webhook
| Field | Value |
|---|---|
| Name | SigSentry |
| Image | (Optional) Upload a logo |
Click Create. Teams generates a webhook URL — copy it.
Add the channel in SigSentry
In the dashboard, Project → Channels → Add Channel.
| Field | Value |
|---|---|
| Type | Microsoft Teams |
| Name | Descriptive label, e.g. #prod-incidents-teams |
| Webhook URL | The Teams webhook URL you just copied |
| Severity threshold | Lowest severity that should trigger this channel |
Save and test
Click Save. Run a test analysis to verify the Adaptive Card lands in the Teams channel.
What gets posted
Each Teams message includes:
- A severity badge and the analysis summary
- The root cause and affected services
- A "View full analysis" button linking back to the dashboard
Messages render natively in Teams desktop, web, and mobile.
Posting from a Teams app vs webhook
This setup uses the simpler webhook approach. If your org has a sideloaded Teams app for SigSentry (for inbound slash commands), the same channel can also receive bot-posted messages with deeper interactivity. See Teams chat triggers for the app installation flow.
Troubleshooting
| Error | Fix |
|---|---|
400 BadRequest: Microsoft Teams endpoint returned HTTP error 400 | Card payload rejected — usually a Teams-side issue with attachments. Retry. |
| Webhook URL doesn't work | Connector may have been removed; recreate it in the same or a new channel |
| Connectors disabled in your org | Your IT admin has restricted them — ask for an exception or use the generic webhook channel pointed at a Teams-compatible Adaptive Card endpoint |