Microsoft Teams
Incident updates through a workflow your team owns
Subscriber updates capability
On this page4
Post your incidents, updates and scheduled maintenance into a Microsoft Teams channel. Teams does not offer simple incoming webhooks any more; a channel receives outside posts through a Workflow, which gives you a URL. InBrief posts to that URL.
Dashboard → Alerts → Channels, then Add channel → Microsoft Teams. Owners and admins can manage it; it is part of the Subscriber updates capability.
Key features
- Incident, update, resolution and maintenance posts in the language you choose, scoped to the services you choose.
- A test button, pause and resume, and a delivery history on the screen.
- The workflow URL is write-only after saving; the card shows the environment it belongs to and a short reference.
- Two Teams-specific warnings at setup time, when they can still save you a support ticket: the co-owner, and the channel type.
Connecting a channel
Dashboard → Alerts → Channels, then Add channel → Microsoft Teams. This is the list; the form behind Add channel walks you through the four steps:
Creating the workflow in Teams
- In Teams, open the channel, then More options → Workflows, and choose Send webhook alerts to a channel.
- Set Who can trigger the flow? to Anyone. InBrief sends no sign-in token, so any other setting refuses the posts.
- Add a co-owner to the workflow. A workflow belongs to the person who made it, not to the team, so it stops working the day that person leaves if nobody else owns it. Somebody leaving is the normal way this destination dies.
- Save the workflow, copy the URL it gives you, and paste it into Workflow URL here.
The fields
| Field | What it does |
|---|---|
| Workflow URL | Must be on api.powerplatform.com. Microsoft retired
the older logic.azure.com URLs on 30 November 2025, so a URL copied from an old connector
will not work. |
| Standard or shared channel | A checkbox you tick to say the channel is a standard or shared one. The Workflows app cannot post into private channels, and nothing in the URL reveals the channel type, so this is your statement rather than a check; a private channel simply never receives the updates. |
| What to call this destination | Shown here and in the audit log. Never sent to Microsoft. |
| Language and services | One language per destination, and either every service or the ones you tick. |
After saving
The card shows the workflow's environment, a short reference for the URL, and Last result for the most recent delivery. Press Send a test straight away; the one thing you cannot see from here is whether the person who made the workflow set its trigger correctly, and a test finds that out in a second.
Saving or deleting can ask you to confirm it is you, by a link emailed to you. If posts fail five times in a row the destination is paused; replace the URL with a fresh one from a workflow that still has an owner and turn it back on.