PingInsight
Start free
Integration

Microsoft Teams alerts for every incident

PingInsight posts confirmed outages and recoveries to a Microsoft Teams channel using a Power Automate Workflow URL — the current, supported method, not the legacy and now-retired Office 365 connectors. Alerts render as an Adaptive Card with the monitor, status, and exact downtime, so your organization stays informed where it already collaborates. Because delivery runs through your own Power Automate flow, throughput is governed by that flow's run limits rather than a chat-app webhook quota.

Set up in minutes

In-app path: Alerting → Channels → Add channel → Microsoft Teams

  1. 1.Create a Power Automate workflow that posts to your Teams channel and copy its URL.
  2. 2.Add a Microsoft Teams channel under Alerting and paste the Workflow URL.
  3. 3.Attach it to monitors, an escalation policy, or an on-call schedule.
  4. 4.Send a test alert to confirm it posts to the channel.
What you can do
  • ✓Adaptive-Card down/up alerts in the Teams channel your org watches
  • ✓Degraded-latency warnings before an outage becomes total
  • ✓SSL and domain-expiry reminders for the whole team
  • ✓Uses Power Automate Workflows, not deprecated O365 connectors
What the alert looks like in Microsoft Teams

A sample Microsoft Teams alert

!PingInsight→ Microsoft Teamsnow
▌ Adaptive Card — Microsoft Teams
🔴 DOWN · api.example.com
Check: HTTP   Error: HTTP 503
Confirmed by 2 of 3 regions · 14:03:07 UTC
[ View incident ]

Exact formatting varies by Microsoft Teams; the live alert includes the monitor, confirming regions, and the precise downtime on recovery.

FAQ

Frequently asked questions

My old Office 365 connector stopped working — what changed?
Microsoft retired Office 365 connectors for Teams. PingInsight uses the supported Power Automate Workflows path instead: create a workflow that posts to your channel, copy its HTTP-trigger URL, and paste it into the Microsoft Teams channel under Alerting.
The Workflow URL is saved but nothing posts to Teams — why?
Open the run history of your Power Automate flow. A common cause is the flow being turned off, or its 'When an HTTP request is received' trigger expecting a different schema. Confirm the flow is on and accepts the posted JSON, then re-send the test alert.
Can different Teams channels get different alerts?
Yes — build one workflow per Teams channel, each with its own URL, and add a separate PingInsight channel for each. Attach them to different monitors or escalation steps so, for example, infrastructure alerts and customer-facing alerts land in different places.

See all alerting integrations or read about incident management.

Start monitoring in under a minute

Free forever, no credit card. Upgrade when you need finer intervals.

Start freeSee pricing