StatusPulse StatusPulse
← All features

Integrations · Pro+

Microsoft Teams integration

Your company standardised on Microsoft 365 — your alerts should land in Teams, not in a Slack channel nobody opens.

Why you need it

Microsoft retired the legacy Office 365 Connectors at the end of 2025. StatusPulse skipped that dead end and ships against the supported Power Automate Workflows path — so your Teams integration keeps working long after a competitor built on the old connector goes dark.

  • Alerts that look native to Teams. Adaptive Card 1.4 payloads render with probe name, region, status pill, latency, and the change reason laid out the way a Teams user expects — not a forwarded email or a raw JSON blob.
  • One workflow per channel, route by status page. Create the Workflow once in Power Automate, drop the URL on the page's Settings tab, alerts land in the right channel for the right product team.
  • Both Microsoft host paths supported. *.logic.azure.com for older flows, *.api.powerplatform.com for newer ones — your URL gets accepted whether your tenant migrated or not.
  • Send-test before you trust it. One button posts a labelled sample card so you confirm the wiring is right before a real incident depends on it.
  • Tamper-resistant. Changing the hostname on a saved Workflow URL pops a confirmation modal and writes an audit-log entry, so an attacker can't quietly redirect your alerts to their tenant.

Where it pays off

The default chat-ops integration for any organisation on Microsoft 365:

  • Enterprise customers on Teams. Your buyer standardised on Microsoft 365 three years ago. Slack isn't on the table. Alerts go where the team already is.
  • Multi-product Teams tenants. One workflow per status page — billing alerts land in the billing channel, search alerts in the search channel, each squad sees its own signal.
  • Customer-shared incident channels. Some enterprise contracts ask for a shared Teams channel where outages get posted in real time. Wire one workflow there and the contract clause writes itself.
  • Compliance-heavy environments. Workflows run inside your Microsoft 365 tenant, which keeps the data-residency story short for regulated buyers.

Not the right tool when: your team actually uses Slack day-to-day (use the Slack integration) or you need rotation-based paging with acknowledgement (point an outbound webhook at PagerDuty or Opsgenie).

Available on Pro+. Already on StatusPulse? See the full config in Help →

Related

Try Microsoft Teams integration in StatusPulse

5 probes, 1 status page, forever. No credit card. US or EU host — you choose.

Start free See pricing