PullNotifier Logo

PullNotifier

Free Templates

Microsoft Teams incident report templates with adaptive cards

Five ready-to-use Microsoft Teams incident report templates. Each includes a markdown report template AND a Microsoft Teams adaptive card JSON for posting status updates to your incident channel. Use them with Power Automate Workflows or PullNotifier.

Targeting: microsoft teams incident report template · Last updated 2026-05-02

Contents

Try the templatesWhen to use each templateHow to send these to a Microsoft Teams channel

Skip the manual setup

PullNotifier installs from Microsoft AppSource in 5 minutes — no YAML, no Power Automate flows.

Try the templates

Switch between the five Microsoft Teams incident report templates below. Each tab contains a markdown document for the running record and a complete Adaptive Card v1.5 JSON payload for posting status to your incident channel.

Initial alertUse case: Post immediately when an incident is declared.

Initial incident notification template (microsoft teams incident channel template)

Post this the moment an incident is declared. The adaptive card gives the team an at-a-glance status, severity and runbook link; the markdown bulletin lives in the threaded conversation as the canonical record.

Microsoft Teams card preview

INCIDENT DECLARED · P1

INC-1042 — Checkout returning 500 errors

Started 14:32 UTC · @sarah-chen

Elevated error rate on the checkout service since 14:32 UTC. On-call paged, investigation in progress.

Severity

P1 — full outage

Next update

By 15:00 UTC

View runbookJoin war room

Markdown incident report template

Paste this into the threaded reply under the adaptive card, or copy it into your wiki / runbook tool.

markdown

# Incident declared — INC-XXXX

**Status:** Investigating
**Severity:** P1
**Started:** 2026-05-02 14:32 UTC
**Owner:** @incident-commander
**Comms lead:** @comms-lead

## What's happening

_One or two sentences describing the user-facing symptom._

## Affected systems

- Service / system 1
- Service / system 2

## Current actions

- [ ] Paged on-call SRE
- [ ] Opened war room: [Microsoft Teams meeting](https://teams.microsoft.com/l/meetup-join/...)
- [ ] Updated status page to "Investigating"

## Next update

By **HH:MM UTC** in this thread.

Microsoft Teams adaptive card JSON (v1.5)

Paste this JSON into a Power Automate "Post adaptive card" action, a custom webhook payload, or PullNotifier's incident channel routing.

adaptive-card.json

{
  "type": "AdaptiveCard",
  "$schema": "http://adaptivecards.io/schemas/adaptive-card.json",
  "version": "1.5",
  "body": [
    {
      "type": "Container",
      "style": "attention",
      "bleed": true,
      "items": [
        {
          "type": "ColumnSet",
          "columns": [
            {
              "type": "Column",
              "width": "auto",
              "items": [
                {
                  "type": "TextBlock",
                  "weight": "Bolder",
                  "color": "attention",
                  "text": "INCIDENT DECLARED"
                }
              ]
            },
            {
              "type": "Column",
              "width": "auto",
              "items": [
                {
                  "type": "TextBlock",
                  "weight": "Bolder",
                  "color": "attention",
                  "text": "P1"
                }
              ]
            }
          ]
        }
      ]
    },
    {
      "type": "TextBlock",
      "size": "Large",
      "weight": "Bolder",
      "text": "INC-1042 — Checkout returning 500 errors",
      "wrap": true
    },
    {
      "type": "TextBlock",
      "text": "Elevated error rate on the checkout service since 14:32 UTC. On-call paged, investigation in progress.",
      "wrap": true
    },
    {
      "type": "FactSet",
      "facts": [
        { "title": "Severity", "value": "P1 — full outage" },
        { "title": "Started", "value": "2026-05-02 14:32 UTC" },
        { "title": "Incident commander", "value": "@sarah-chen" },
        { "title": "Next update", "value": "By 15:00 UTC" }
      ]
    }
  ],
  "actions": [
    {
      "type": "Action.OpenUrl",
      "title": "View runbook",
      "url": "https://example.com/runbooks/checkout-500"
    },
    {
      "type": "Action.OpenUrl",
      "title": "Join war room",
      "url": "https://teams.microsoft.com/l/meetup-join/..."
    },
    {
      "type": "Action.OpenUrl",
      "title": "Status page",
      "url": "https://status.example.com"
    }
  ]
}

How to use this in Microsoft Teams

  1. Pick your incident channel. Most teams keep a dedicated #incidents channel plus a per-incident channel created when severity is P0 or P1.
  2. Send the adaptive card. Use a Power Automate Workflow ("Post adaptive card in a chat or channel"), PullNotifier, or a webhook tester such as /tools/microsoft-teams-webhook-tester to deliver the JSON.
  3. Post the markdown report. Reply to the adaptive card in the same thread with the markdown above. The card stays at-a-glance, the markdown captures the detail.

Severity colour key

Red — live incident

Amber — status update

Green — resolved

Blue — post-mortem

Purple — customer comm

When to use each template

TemplateWhen to postAudienceCard colour
Initial incident notificationThe moment the incident is declaredIncident channel + on-call rotationRed (attention)
Status updateEvery 15-30 min during active mitigationIncident channelAmber (warning)
Resolved incidentWhen metrics confirm full recoveryIncident channel + leadershipGreen (good)
Post-mortem (5 Whys)24-72 hours after resolutionEngineering + leadership reviewBlue (accent)
Customer-facing statementWhile drafting the external commCustomer-comms channel (support, legal, leadership)Purple (accent)

How to send these to a Microsoft Teams channel

There are three common paths to push an adaptive card into a Microsoft Teams incident channel. Pick whichever matches your team's tooling — the JSON payloads above work with all three.

  • Power Automate Workflow. Use the "Post adaptive card in a chat or channel" action. Trigger it from PagerDuty, Datadog, Sentry, OpsGenie, an HTTP request, or a manual button. Best when you want a no-code automation owned by ops. See the Workflows migration guide for the full setup.
  • PullNotifier. Configure your incident channel and route GitHub events (PRs, deploys, CI failures) plus incident status updates with a single Microsoft Teams app install — no Workflow author required.
  • Manual webhook test. Drop the JSON into /tools/microsoft-teams-webhook-tester to validate rendering before you wire up automation. This is the fastest path for one-off tests or iterating on copy.
  1. Initial incident notification template

    (https://pullnotifier.com/tools/microsoft-teams-incident-report-template#initial-incident-notification)

    Markdown bulletin and red-status adaptive card to declare an incident in a Microsoft Teams incident channel.

  2. Status update template

    (https://pullnotifier.com/tools/microsoft-teams-incident-report-template#status-update)

    Amber-status adaptive card and incremental markdown post for the running thread during an active incident.

  3. Resolved incident notification template

    (https://pullnotifier.com/tools/microsoft-teams-incident-report-template#resolved-notification)

    Green-status adaptive card and resolution summary markdown including MTTR and post-mortem link.

  4. Post-mortem template (5 Whys)

    (https://pullnotifier.com/tools/microsoft-teams-incident-report-template#post-mortem)

    Full blameless post-mortem markdown plus an announcement adaptive card with action item count.

  5. Customer-facing incident statement template

    (https://pullnotifier.com/tools/microsoft-teams-incident-report-template#customer-statement)

    External customer comm draft markdown and a review-flow adaptive card for sign-off in a customer-comms channel.


Frequently asked

Why use Microsoft Teams adaptive cards for incident communication?

Adaptive cards give the channel an at-a-glance status with colour-coded headers, structured fact sets and direct action buttons (join war room, view runbook, open dashboard). They render faster than reading a long Slack-style DM thread, survive scroll-back searching, and let on-call responders triage without opening every reply.

Can I customise these templates?

Yes. Edit the markdown freely — add your own fields, severity matrix or compliance section. The adaptive card JSON is also yours to modify: tweak the FactSet, add an Image element with your logo, or swap Action.OpenUrl for Action.Submit if you have a bot that handles in-Teams interactions.

How do I post an adaptive card to a Microsoft Teams incident channel?

Three paths: (1) Power Automate Workflow with the "Post adaptive card in a chat or channel" action — see our /tools/office-365-connector-migration-guide for the full setup; (2) PullNotifier, which installs from Microsoft AppSource and routes events to channels for you; (3) /tools/microsoft-teams-webhook-tester for one-off testing of the JSON before you wire up automation.

What is the difference between a status update card and a markdown post?

The card is at-a-glance — colour-coded badge, severity, time since incident start, current state — designed to be scanned in two seconds in a noisy channel. The markdown post lives in the threaded reply and captures the detail: what changed, what we tried, the timestamps. Together they give responders both the headline and the long-form record.

Do these templates work with the retired Office 365 Connectors?

No. Office 365 Connectors used the legacy MessageCard format and were retired on March 31, 2026. Use Power Automate Workflows or a Microsoft Teams app instead — both support the modern Adaptive Card v1.5 schema used by every template on this page. See /alternatives/office-365-connector for migration paths.

Can I automate sending these from PagerDuty, Datadog or Sentry?

Yes. PagerDuty, Datadog and Sentry all expose Power Automate connectors that accept arbitrary JSON payloads. Drop one of the adaptive card templates into the connector body, map the alert variables to the FactSet values, and the card lands in your incident channel automatically when an alert fires.

Keep reading

Incident Report Templates (parent — Markdown only)Microsoft Teams Adaptive Card TemplatesMicrosoft Teams Webhook Tester

Stop hand-crafting incident JSON — install PullNotifier

Route GitHub PRs, deploys and incident status to Microsoft Teams in 5 minutes. Free for small teams.

PullNotifier Logo

PullNotifier

© 2026 PullNotifier. All rights reserved

Microsoft Teams

Overview

Integration

Setup Guide

Pricing

Code Review Reminders

vs Official @github

O365 Connector Replacement

Read our Blog

Privacy Policy

Terms of Service

Changelog