Home / Integrations / Microsoft Teams
Microsoft Teams integration — channel alerts through a workflow webhook
Route new Feedback DevTools items to a Microsoft Teams channel through a Teams Workflows webhook. Posts a card with title, page, file:line and a link back, plus an optional Shipped card when the fix merges. Automatic retries with backoff. Notify-only: not a Teams app, no replies, no two-way sync.
What it does
- Notify-only. When a new feedback item is created, FDT posts one card to the Teams channel you picked. It does not read the channel, reply to messages, or add a bot.
- Card contents: title, project, type and priority, the page URL, the source
file:line when capture mapped it, and an Open in Feedback DevTools button. - Workflow webhooks only. The address must be a Microsoft workflow URL (for example
https://….logic.azure.com/workflows/… or https://….powerplatform.com/…). Other addresses are rejected. - Retries / backoff. If Teams is busy or down, delivery is retried automatically with backoff. Permanent errors (a deleted workflow, a cut-off address) show on the destination.
- Shipped cards (optional). Tick "Also post when it ships" on the destination and FDT posts a second card, with a link to the merged pull request, when an Autopilot PR for that item merges. Items closed by hand do not trigger it.
How to connect
About two minutes. You need permission to add workflows to the channel; no admin or developer setup.
- In Microsoft Teams, open the channel that should get alerts, click its ••• menu and choose Workflows.
- Pick the template Post to a channel when a webhook request is received, give it a name (for example "Feedback DevTools"), and confirm the team and channel.
- Teams shows a long web address when it finishes. Click Copy and keep the whole address; it ends in a long code that must not be cut off.
- In the FDT project dashboard: Project → Settings → Destinations → Add → Microsoft Teams, then paste that address.
- Press Send test. A sample card should appear in the channel within a minute. If it does not, the panel says why in plain words, and the workflow's run history in Teams shows what happened on the Teams side.
Honest limits
This is not a Teams app: there is no bot, no replies, no editing earlier cards, and nothing from Teams flows back into Feedback DevTools. Teams accepts each card first and posts it a few seconds later, so a workflow that was turned off or lost access to the channel can accept a card without posting it; check the workflow's run history if a card is missing.
The older Office 365 "Incoming Webhook" connector addresses (….webhook.office.com) still work while Microsoft keeps them running, but new setups should use Workflows.
See also Slack, Jira Cloud, Zapier Catch Hook, and docs.