Microsoft deprecated Office 365 Teams connectors. What do I do?

Microsoft announced the retirement of the Office 365 connectors used to deliver incoming webhooks to Microsoft Teams. The replacement is Power Automate Workflows (sometimes called "Workflows" in the Teams UI).

Oh Dear supports both, so you can migrate on your own schedule.

Which one do I have?

In your monitor's notification settings or team-level notifications, look at your Microsoft Teams destinations:

  • Microsoft Teams (legacy): the old connector-based channel. Uses a webhook URL like https://your-org.webhook.office.com/webhookb2/.... This is what Microsoft is deprecating.
  • Microsoft Teams: the new Workflows-based channel. Uses a URL under *.logic.azure.com or the newer workflow endpoint pattern.

If yours looks like the legacy pattern, it's time to migrate.

How to migrate

  1. In Microsoft Teams, create a new Workflow to deliver messages to your channel:
    • Open the channel
    • Go to Workflows > Post to a channel when a webhook request is received
    • Save the workflow and copy the generated URL
  2. In Oh Dear, add a new Microsoft Teams notification destination (the non-legacy one).
  3. Paste the URL from step 1.
  4. Select which events should go to this channel.
  5. Send a test notification to confirm everything works.
  6. Once the new channel is working, delete the legacy Microsoft Teams channel.

Why two separate channels?

Microsoft made the new and old endpoints incompatible, so we expose both as separate channels. That lets you migrate one monitor at a time and fall back if anything goes wrong.

Full docs: Microsoft Teams notifications.

Related Questions

View all Notifications questions →

Want to get started? We offer a no-strings-attached 10 day trial. No credit card required.

Start monitoring

You're all set in
less than a minute!