Microsoft Teams via Power Automate Workflows
Microsoft retired Office 365 Connector webhooks. Re-create your Teams notification channel with a Workflows webhook, and see how the Acknowledge/Resolve/Silence buttons work.
Microsoft retired Office 365 Connector ("Incoming Webhook") webhooks for Teams in May 2026. Any URL on
outlook.office.com/webhook/… or <tenant>.webhook.office.com/webhookb2/… now rejects requests.
If your Teams channel used one of those URLs, it has stopped delivering alerts. HowlOps marks such channels as Needs migration and will not attempt delivery to a dead endpoint. Follow the steps below to restore notifications.
Create the Workflows webhook
- In Teams, open the channel you want alerts in.
- Select … next to the channel name → Workflows.
- Choose the template Post to a channel when a webhook request is received.
- Confirm the team and channel, then Add workflow.
- Copy the generated URL. It is on the
logic.azure.comhost — for examplehttps://prod-12.westeurope.logic.azure.com/workflows/….
Point HowlOps at it
- Go to Settings → Notification channels.
- Open the Teams channel marked Needs migration (or create a new one).
- Paste the new
logic.azure.comURL over the old one and save. - Use Send test to confirm the card arrives.
The channel keeps its name, throttle settings and alert routing — only the URL changes. HowlOps rejects a
legacy office.com webhook URL at save time, so you cannot accidentally re-create a dead channel.
What we send
An Adaptive Card at schema version 1.4, wrapped in the message envelope Workflows expects. We pin 1.4 deliberately: Workflows does not reliably render newer schema versions.
Alert bodies are truncated if the payload would exceed the 28 KB limit Power Automate enforces.
Acknowledge, resolve or silence from Teams
Incident alerts posted to Teams include Acknowledge, Resolve, and Silence buttons, so you can act on an incident without switching to HowlOps.
On Teams, these buttons open a short confirmation page in your browser instead of updating the message
in place. This is a Microsoft limitation, not a choice we made: Teams Workflows webhooks cannot run an
in-place action button. The legacy actionable-card POST that used to make this possible was retired by
Microsoft, and the newer card action types either aren't rendered by Workflows (Action.Http,
Action.Submit) or need a registered bot (Action.Execute), which a plain incoming webhook doesn't
have. So the Teams buttons are links: one tap opens a page that confirms the action. It's still one
click from the alert, just not the same in-place "Acknowledged" update you'd see in Slack or Mattermost.
Known limitations
These are Microsoft's constraints, not ours:
- Messages are posted by the Workflows bot rather than by a named connector app.
- A workflow is owned by the user who created it. If that person leaves the organisation the flow stops. Add co-owners in Power Automate so the flow survives.
- Power Automate throttles a flow at roughly 4 requests per second. A very noisy alert storm may be delayed by Microsoft, not by us.
- The Acknowledge / Resolve / Silence buttons open a browser confirmation page rather than updating the Teams message in place. See Acknowledge, resolve or silence from Teams above.
Was this page helpful?