Transitioning from Office 365 Connectors

This guide shows how to migrate to a Workflow‑based integration in minutes.

If your Microsoft Teams alerts from IsDown stopped, you were likely using the legacy Office 365 Connector (“Incoming Webhook”). Microsoft has retired this feature in Teams and replaced it with the Workflows app.

Why alerts stopped?

Microsoft phased out Office 365 Connectors. The URLs used no longer accept posts. The connector may still appear in the UI, but messages will not reach Teams.

To restore alerts:

• Create a new Webhook in Workflows

• Update the URL in IsDown

No changes to alert rules or status‑page selections in IsDown are needed—only the Teams connection.

---

Migration checklist

You don’t edit the old connector. Create a new Workflow Webhook and update the URL in IsDown.

1. Identify the channel

1. Open Teams and go to the channel where IsDown alerts used to appear.

2. Note the Team name and Channel name for the new workflow.

2. Create the new Teams endpoint (Workflow)

1. Follow our guide in this article.

3. Update the URL in IsDown

1. Open IsDown Dashboard → Alerts & Integrations → Microsoft Teams.

2. Set Integration method to Workflows.

3. Paste the new Webhook URL into the Webhook URL field.

4. Click Save.

Once complete, you can ignore or remove the old Office 365 Connector in Teams.

---

Technical notes for admins

1. Workflow ownership and lifecycle

• Each workflow is owned by the user who created it.

• If that account is disabled, the workflow stops running.

• For critical alerts, consider:

  • Creating the workflow under a dedicated service account, or

  • Adding co‑owners in Teams Workflows/Power Automate so others can maintain it.

2. Private channels

• Workflows can post to private channels if:

  • The workflow creator is a member, and

  • Tenant policies allow Workflows/Power Automate.

• When migrating alerts from a connector in a private channel, create the workflow while signed in with an account that has access.

• If permission errors occur, test first in a standard channel, then adjust private channel permissions with your Teams/M365 admin.