Microsoft Teams Integration
Post rich incident Adaptive Cards to Microsoft Teams channels with severity coloring, AI summaries, and action buttons. No bot installation required.
How It Works
Create an Incoming Webhook
In Microsoft Teams, go to your channel > Connectors > Incoming Webhook. Create a webhook and copy the URL to configure in TigerOps.
Configure the TigerOps Connector
In TigerOps Settings > Alerting > Microsoft Teams, paste the webhook URL and configure the card format, severity filter, and channel routing rules.
Choose Card Format
Select between Adaptive Card (rich, interactive) and MessageCard (legacy, broader compatibility) formats. Adaptive Cards include action buttons for acknowledge and mute.
Route by Team and Channel
Configure multiple Teams webhooks for different channels. Route infrastructure alerts to the DevOps channel and SLO breaches to the Engineering Leadership channel.
What You Get Out of the Box
Adaptive Card Notifications
Rich Adaptive Card messages with severity badges, metric charts, affected service details, and action buttons (Acknowledge, Mute 1h, Open Incident) — all from Teams.
AI Incident Summary
The TigerOps AI root cause analysis is included in the card body, giving engineers immediate context about why the alert fired without leaving Teams.
Severity Color Coding
Cards are color-coded by severity: red header for critical, amber for warning, green for recovery. Visual triage at a glance before opening the full incident.
Multi-Channel Routing
Route different alert categories to different Teams channels using TigerOps label-based routing rules. Configure separate webhooks per team, environment, or alert type.
Alert Deduplication
TigerOps sends a single Teams message per incident and updates it on state changes rather than flooding the channel with repeated notifications.
Recovery & SLO Reports
Automatic recovery cards when incidents resolve, and weekly SLO summary cards with error budget consumption charts posted to your engineering channel.
Teams Connector Webhook Config
Configure multi-channel Teams routing with Adaptive Card format and severity mapping.
# tigerops-teams-config.yaml — Microsoft Teams integration
integrations:
microsoft_teams:
# Engineering incidents channel
- name: eng-incidents
webhookUrl: "${TEAMS_INCIDENTS_WEBHOOK}"
cardFormat: adaptive # adaptive | messagecard
minSeverity: critical
# General monitoring channel
- name: monitoring
webhookUrl: "${TEAMS_MONITORING_WEBHOOK}"
cardFormat: adaptive
minSeverity: warning
digestMode:
enabled: true
intervalMinutes: 10
routing_rules:
- match:
labels:
env: production
severity: critical
teams:
channel: eng-incidents
cardColor: attention # attention | warning | good | default
includeAISummary: true
actions:
- type: OpenUrl
title: "View in TigerOps"
url: "{{ .IncidentURL }}"
- type: OpenUrl
title: "Acknowledge"
url: "{{ .AckURL }}"
- type: OpenUrl
title: "Runbook"
url: "{{ .RunbookURL }}"
- match:
labels:
env: production
teams:
channel: monitoring
cardColor: warning
includeAISummary: true
# Weekly SLO digest — posted every Monday 9am
slo_digest:
enabled: true
channel: eng-incidents
schedule: "0 9 * * MON"
timezone: "America/New_York"Common Questions
Does TigerOps support Microsoft Teams Adaptive Cards v1.5?
Yes. TigerOps supports Adaptive Cards schema version 1.5 for Teams desktop and mobile clients. For older Teams clients that do not support Adaptive Cards, TigerOps automatically falls back to the MessageCard format.
Can I use a Teams bot instead of an incoming webhook?
Incoming webhooks are the recommended approach for alert notifications as they require no bot installation or Azure app registration. If your organization requires bot-based integration, contact TigerOps support for the Teams App manifest.
Can TigerOps @mention users or channels in Teams?
Yes, with the Teams bot integration. The incoming webhook approach supports @mentioning channels but not individual users. For individual @mentions in critical alerts, use the TigerOps Teams bot integration.
How do I send alerts to a Teams private channel?
Private channels in Teams support incoming webhooks just like public channels. Create the webhook in the private channel settings and paste the URL into TigerOps. Access is controlled entirely by the Teams channel permissions.
Can TigerOps integrate with Teams through Microsoft Power Automate?
Yes. Use the TigerOps webhook output to trigger a Power Automate flow, which can then perform additional routing, approval gates, or integration with other Microsoft 365 tools before posting to Teams.
Incident Cards Where Your Team Already Works
Adaptive Cards with AI summaries and action buttons delivered to your Teams channels. Setup in 2 minutes.