Microsoft Teams

Notification

Synopsis

Sends alert notifications to Microsoft Teams channels using incoming webhooks, supporting Adaptive Card formatting with titles, text, facts, actions, and theme colors.

Schema

- msteams:
    webhook_url: <string>
    title: <string>
    text: <string>
    subtitle: <string>
    image: <string>
    theme_color: <string>
    width: <string>
    facts: <fact[]>
    actions: <action[]>
    description: <text>
    if: <script>
    ignore_failure: <boolean>
    on_failure: <processor[]>
    on_success: <processor[]>
    tag: <string>

Configuration

Field	Required	Default	Description
`webhook_url`	N	`${MSTEAMS_WEBHOOK_URL}`	Microsoft Teams incoming webhook URL
`title`	Y	-	Card title displayed prominently
`text`	Y	-	Main message body text
`subtitle`	N	-	Subtitle displayed below the title
`image`	N	VirtualMetric icon	URL to image displayed in the card
`theme_color`	N	`#47BEFF`	Card accent color: `good`, `warning`, `danger`, `info`, or hex code
`width`	N	`Full`	Card width: `Full` for full-width cards
`facts`	N	-	Array of fact objects with `title` and `value` fields
`actions`	N	-	Array of action objects with `title` and `url` fields
`description`	N	-	Explanatory note
`if`	N	-	Condition to run
`ignore_failure`	N	`false`	See Handling Failures
`on_failure`	N	-	See Handling Failures
`on_success`	N	-	See Handling Success
`tag`	N	-	Identifier
`disabled`	N	`false`	When `true`, the processor is skipped and the event continues to the next one. Lets you take a processor out of the path without removing its configuration

Details

The msteams processor sends notifications to Microsoft Teams channels using incoming webhooks with Adaptive Card formatting.

Webhook Setup: Create an incoming webhook in Teams:

Open the target channel
Click "..." → "Connectors" or "Workflows"
Add "Incoming Webhook" connector
Copy the webhook URL

Theme Colors: Visual severity indicators for the card's accent stripe:

good / green hex: Success, resolved incidents
warning / orange hex: Warnings, degraded states
danger / red hex: Errors, critical alerts
info / blue hex: Informational messages
Custom hex codes (e.g., #FF5733) for brand colors

Facts: Key-value pairs displayed in a structured format:

facts:
  - title: "Server"
    value: "{{hostname}}"
  - title: "CPU"
    value: "{{cpu_usage}}%"

Actions: Clickable buttons linking to external resources:

actions:
  - title: "View Dashboard"
    url: "https://dashboard.example.com/{{server}}"

Template Support: Five top-level fields are template-expanded — title, text, subtitle, image and theme_color — along with the title and value of each entry in facts, and the title and url of each entry in actions. Use {{field_name}} for the escaped value and {{{field_name}}} for the raw one. No other field is expanded.

For integration patterns with schema validation, see Schema Drift Detection.

Examples

Basic Alert

Sending a simple alert notification...

{
  "alert_name": "High CPU Usage",
  "server": "prod-server-01",
  "cpu_usage": "95%"
}

- msteams:
    webhook_url: "${MSTEAMS_WEBHOOK_URL}"
    title: "Alert: {{alert_name}}"
    text: "CPU usage is at {{cpu_usage}} on server {{server}}"
    theme_color: "danger"

Red-themed alert card sent to Teams channel...

Card with Facts

Including structured data as facts...

{
  "alert_name": "Schema Drift Detected",
  "schema": "ASimNetworkSessionLogs",
  "missing": "3 required fields"
}

- msteams:
    webhook_url: "${MSTEAMS_WEBHOOK_URL}"
    title: "{{alert_name}}"
    text: "Schema validation failed"
    theme_color: "warning"
    facts:
      - title: "Schema"
        value: "{{schema}}"
      - title: "Missing Fields"
        value: "{{missing}}"

Facts displayed in structured format below text...

Card with Actions

Adding clickable action buttons...

{
  "alert_name": "Database Connection Failed",
  "server": "db-server-01"
}

- msteams:
    webhook_url: "${MSTEAMS_WEBHOOK_URL}"
    title: "{{alert_name}}"
    text: "Connection to {{server}} failed"
    theme_color: "danger"
    actions:
      - title: "View Dashboard"
        url: "https://dashboard.example.com/servers/{{server}}"
      - title: "View Logs"
        url: "https://logs.example.com/{{server}}"

Action buttons link to analytics views and logs...

Complete Card

Full-featured card with all elements...

{
  "alert_type": "Critical",
  "server": "prod-server-01",
  "cpu_usage": "95%",
  "memory_used": "87%",
  "disk_space": "92%"
}

- msteams:
    webhook_url: "${MSTEAMS_WEBHOOK_URL}"
    title: "{{alert_type}} Alert"
    subtitle: "Server: {{server}}"
    text: "Server resources are critically high"
    image: "https://example.com/alert-icon.png"
    theme_color: "danger"
    width: "Full"
    facts:
      - title: "CPU Usage"
        value: "{{cpu_usage}}"
      - title: "Memory Used"
        value: "{{memory_used}}"
      - title: "Disk Space"
        value: "{{disk_space}}"
    actions:
      - title: "View Dashboard"
        url: "https://dashboard.example.com/{{server}}"

Full-width card with image, facts, and actions...

Schema Drift Alert

Alerting on schema validation failures...

processors:
  - check_schema:
      schema: "ASimNetworkSessionLogs"
      target_field: "schema_check"
      on_missing:
        - msteams:
            webhook_url: "${MSTEAMS_WEBHOOK_URL}"
            title: "Schema Validation Failed"
            subtitle: "Data Quality Alert"
            text: "Missing required fields detected"
            theme_color: "danger"
            facts:
              - title: "Schema"
                value: "ASimNetworkSessionLogs"
              - title: "Valid"
                value: "{{schema_check.is_valid}}"

Alert triggered automatically when schema drift detected...

Synopsis​

Schema​

Configuration​

Details​

Examples​

Basic Alert​

Card with Facts​

Card with Actions​

Complete Card​

Schema Drift Alert​