Files
coder/docs/admin/monitoring/notifications/teams.md
T
Nick Vigilante bc77c40296 docs: add front-matter titles to mechanical and no-H1 pages (Phase 3) (#28030)
## Summary

**Batch A of Phase 3** of the H1 → front-matter migration (`DOCS-484`;
parent `DOCS-477`). Adds a front-matter `title` to every navigable docs
page whose title can be migrated **mechanically**, with no editorial
judgment.

This is the content step that Phase 1 (renderers prefer front-matter
title, `DOCS-482`) and Phase 2 (tooling + generators front-matter-aware,
`DOCS-483`) unblocked. Both are merged; coder.com #964/#974 are merged
and live.

**Rendered no-op.** The renderers already resolve the page title from
the manifest and hide the leading body H1 (Phase 1), so no page changes
visually. This just moves the title into front matter where Fumadocs and
the migrated tooling can read it.

## What's in this batch

Dry-run on `main` (464 navigable pages) splits into:

| category | count | this PR |
|----------|-------|---------|
| already has front-matter title (Reference, from Phase 2 generators) |
196 | skipped (idempotent) |
| **mechanical** — leading body H1 equals the manifest label | 138 | ✅
add front-matter `title`, drop the duplicate H1 |
| **no body H1** — renders under the manifest label only | 4 | ✅ add
front-matter `title` only |
| **mismatch** — body H1 differs from the manifest label | 126 | ⏭️
deferred (needs an editorial decision, see below) |

142 files changed, all under `docs/`.

## Deliberately out of scope: the 126 mismatches

Pages where the body H1 is richer than the short sidebar label (e.g.
label **Modules** / H1 *Contributing modules*, label **Install** / H1
*Installing Coder*) need a canonical-title decision, not a script. A few
even look like the body H1 is the redundant one (`install/cli.md` and
`install/index.md` both carry the H1 *Installing Coder*). These will
land in follow-up batches **by nav section** once the policy is set, so
each gets real review.

## Verification

AI was the primary author of this PR (see disclosure below); per the [AI
Contribution
Guidelines](https://coder.com/docs/about/contributing/AI_CONTRIBUTING)
here is the manual verification.

- Every added front-matter block parses as YAML and its `title`
round-trips to the manifest label (checked programmatically across all
142 files).
- Every removed line is a leading `# H1` that equalled the manifest
title; no body prose was reflowed. Front matter is correctly hoisted
above pre-existing `<!-- markdownlint-disable -->` comments on the two
pages that had them.
- `pnpm check-docs` (markdownlint-cli2 + table formatter) passes on the
changed set: `Summary: 0 error(s)`. `MD041` stays off (re-enabled in
Phase 4); `MD025` is not tripped because the duplicate body H1s are
removed.

```
$ pnpm exec markdownlint-cli2 $(git diff --name-only origin/main)
Linting: 142 file(s)
Summary: 0 error(s)
```

Linear: DOCS-484

> This PR was created with AI assistance (Coder Agents).
2026-08-27 12:34:13 -04:00

4.9 KiB

title
title
Microsoft Teams Notifications

Microsoft Teams is a widely used collaboration platform, and with Coder's integration, you can enable automated notifications directly within Teams using workflows and Adaptive Cards

Administrators can configure Coder to send notifications via an incoming webhook endpoint. These notifications appear as messages in Teams chats, either with the Flow Bot or a specified user/service account.

Requirements

Before setting up Microsoft Teams notifications, ensure that you have the following:

  • Administrator access to the Teams platform
  • Coder platform >=v2.16.0

Build Teams Workflow

The process of setting up a Teams workflow consists of three key steps:

  1. Configure the Webhook Trigger.

    Begin by configuring the trigger: "When a Teams webhook request is received".

    Ensure the trigger access level is set to "Anyone".

  2. Setup the JSON Parsing Action.

    Add the "Parse JSON" action, linking the content to the "Body" of the received webhook request. Use the following schema to parse the notification payload:

    {
        "type": "object",
        "properties": {
            "_version": {
                "type": "string"
            },
            "payload": {
                "type": "object",
                "properties": {
                    "_version": {
                        "type": "string"
                    },
                    "user_email": {
                        "type": "string"
                    },
                    "actions": {
                        "type": "array",
                        "items": {
                            "type": "object",
                            "properties": {
                                "label": {
                                    "type": "string"
                                },
                                "url": {
                                    "type": "string"
                                }
                            },
                            "required": ["label", "url"]
                        }
                    }
                }
            },
            "title_markdown": {
                "type": "string"
            },
            "body_markdown": {
                "type": "string"
            }
        }
    }
    

    This action parses the notification's title, body, and the recipient's email address.

  3. Configure the Adaptive Card Action.

    Finally, set up the "Post Adaptive Card in a chat or channel" action with the following recommended settings:

    Post as: Flow Bot

    Post in: Chat with Flow Bot

    Recipient: user_email

    Use the following Adaptive Card template:

    {
        "$schema": "https://adaptivecards.io/schemas/adaptive-card.json",
        "type": "AdaptiveCard",
        "version": "1.0",
        "body": [
            {
                "type": "Image",
                "url": "https://coder.com/coder-logo-horizontal.png",
                "height": "40px",
                "altText": "Coder",
                "horizontalAlignment": "center"
            },
            {
                "type": "TextBlock",
                "text": "**@{replace(body('Parse_JSON')?['title_markdown'], '"', '\"')}**"
            },
            {
                "type": "TextBlock",
                "text": "@{replace(body('Parse_JSON')?['body_markdown'], '"', '\"')}",
                "wrap": true
            },
            {
                "type": "ActionSet",
                "actions": [@{replace(replace(join(body('Parse_JSON')?['payload']?['actions'], ','), '{', '{"type": "Action.OpenUrl",'), '"label"', '"title"')}]
            }
        ]
    }
    

    Notice: The Coder actions format differs from the ActionSet schema, so its properties need to be modified: include Action.OpenUrl type, rename label to title. Unfortunately, there is no straightforward solution for for-each pattern.

    Feel free to customize the payload to modify the logo, notification title, or body content to suit your needs.

Enable Webhook Integration

To enable webhook integration in Coder, define the POST webhook endpoint created by your Teams workflow:

export CODER_NOTIFICATIONS_WEBHOOK_ENDPOINT=https://prod-16.eastus.logic.azure.com:443/workflows/f8fbe3e8211e4b638...`

Finally, go to the Notification Settings in Coder and switch the notifier to Webhook.

Limitations

  1. Public Webhook Trigger: The Teams webhook trigger must be open to the public ("Anyone" can send the payload). It's recommended to keep the endpoint secret and apply additional authorization layers to protect against unauthorized access.

  2. Markdown Support in Adaptive Cards: Note that Adaptive Cards support a limited set of Markdown tags.