Skip to main content
Connect a Microsoft Teams channel to receive DevPerform’s weekly team-health digest — the same content as the Slack digest, delivered to the channel of your choice. It’s optional, admin-only, and takes about a minute to set up. Unlike Slack, Teams delivery is webhook-based — there’s no app to install and no admin consent needed. You create a webhook on the channel and paste the URL into DevPerform.

​
1. Create a channel webhook

In Microsoft Teams, use the built-in Workflows app to create an incoming webhook:
  1. Next to the channel name, click ⋯ (More options) → Workflows (or open the Workflows app).
  2. In the template search box, type webhook and choose “Send webhook alerts to a channel.”
  3. Confirm the connection, pick the team and channel you want, and click Add workflow.
  4. Copy the workflow’s URL — that’s your webhook. (Paste it into DevPerform in the next step.)
Pick “Send webhook alerts to a channel” — not the “from specific people” or “from people in an org” variants. Those add a sender allowlist, and since DevPerform posts from outside your organization, they will block its messages. Also avoid the “…to a chat” template — you want a channel.
Microsoft renamed this template (it was formerly “Post to a channel when a webhook request is received”) and replaced the older “Incoming Webhook” connector with Workflows. If you close the dialog before copying the URL, get it back via the channel’s ⋯ → Workflows → your workflow → edit (the trigger step shows the URL), or from make.powerautomate.com → My flows.

​
2. Connect it in DevPerform

  1. Go to Admin → Connections → Microsoft Teams.
  2. Paste the webhook URL (and an optional label, e.g. #engineering).
  3. Click Connect Teams. DevPerform posts a confirmation card to the channel — if you see it, you’re set.
For security, DevPerform only accepts webhook URLs on Microsoft’s domains (webhook.office.com, logic.azure.com, or powerplatform.com) — every URL Teams or Power Automate generates qualifies. If yours is rejected, copy it again from the workflow’s trigger step rather than a proxy or shortened link.

​
What you get

  • Weekly team-health digest — every Monday, a card with last week’s delivery headline (PRs opened/merged, median cycle time), current open-PR count, notable week-over-week changes, and (if enabled) AI highlights.
  • Stale-PR nudges — a periodic card listing open PRs that are getting old or still need a review, so nothing slips.
  • Anomaly alerts — a heads-up when a delivery metric regresses week-over-week (deduped to at most once per week).
  • Send digest now / Send test — preview any time from the Admin panel.
  • Per-feature toggles — turn the weekly digest, nudges, or anomaly alerts on/off independently, without disconnecting.
Per-person survey DMs over Teams are on the roadmap (they require a Teams bot, unlike the channel posts above).

​
Managing the connection

Everything lives under Admin → Connections → Microsoft Teams: send a test, send the digest immediately, toggle the weekly schedule, or Disconnect. Only account admins can manage it. To change channels, create a new webhook and reconnect.

​
If posts stop arriving

Teams webhooks can be deleted or rotated on the Teams side (for example when the Workflows flow is removed or the channel is archived). When that happens, DevPerform detects the failing webhook and the Connections card shows an amber “Teams webhook is failing” state with a field to paste a fresh webhook URL — create a new webhook (step 1 above) and reconnect. Digests, nudges, and alerts resume immediately.