HowlOps
FeaturesHow it worksPricingIntegrationsDocsChangelogContactLog inStart free
DOCS

Microsoft Teams via Power Automate Workflows

Microsoft retired Office 365 Connector webhooks. Re-create your Teams notification channel with a Workflows webhook.

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

  1. In Teams, open the channel you want alerts in.
  2. Select … next to the channel name → Workflows.
  3. Choose the template Post to a channel when a webhook request is received.
  4. Confirm the team and channel, then Add workflow.
  5. Copy the generated URL. It is on the logic.azure.com host — for example https://prod-12.westeurope.logic.azure.com/workflows/….

Point HowlOps at it

  1. Go to Settings → Notification channels.
  2. Open the Teams channel marked Needs migration (or create a new one).
  3. Paste the new logic.azure.com URL over the old one and save.
  4. 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.

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.

Was this page helpful?