Microsoft Teams alert channel
Microsoft Teams is a native alert channel in PulseStack™. Every failure and recovery arrives as a card in the channel your team already works in, posted through a Teams Workflows webhook, so incidents get seen and actioned without anyone opening a dashboard.
Native Teams channel via a Workflows webhook. Works on every paid plan. 14-day trial and Free plan, no card needed.
🔴 Monitor DOWN
🟢 Monitor RECOVERED
Example cards. The recovery card also carries the URL, Type and Time facts.
8
native alert channels
9
monitor types to Teams
30s
fastest check interval
2
events: failure and recovery
Email alerts get buried and dashboards only help the person looking at them. Microsoft Teams is where most organisations coordinate day to day, so that is exactly where an outage should surface. PulseStack posts a clear, structured card as soon as a monitor is confirmed down, and posts again when it recovers.
The whole channel sees the same card at once. No forwarding, no chasing, no waiting for someone to refresh a dashboard.
Monitor name, URL, type, the failing locations with their status codes and the time are all on the card, so triage starts immediately.
Multi-location monitors need two of the three locations to fail and other checks are re-tested, so a single flaky check does not spam the channel.
The setup uses a Teams Workflows webhook, which replaced the Office 365 Incoming Webhook connector that Microsoft switched off in May 2026. No custom app, no code.
In Teams, open the channel's More options (...) menu, choose Workflows and pick the template Send webhook alerts to a channel (older tenants list it as Post to a channel when a webhook request is received). Confirm the team and channel, then copy the HTTP POST URL it generates.
Open Alert Contacts, click Add contact, choose Microsoft Teams, paste the URL into Webhook URL and give it a label naming the Teams channel it posts to.
Tick the contact under Notify on failure on each monitor that should post to Teams. A monitor with nothing ticked alerts every contact.
Click Send test next to the contact. A PulseStack™ Test Alert card should appear in the channel; if Teams refuses it, the error shows the status code Teams returned.
PulseStack cards are built to answer the first questions of any incident before anyone has to ask them. Each alert is self-contained.
{
"@type": "MessageCard",
"@context": "http://schema.org/extensions",
"themeColor": "dc2626",
"summary": "Monitor DOWN: Acme API",
"sections": [{
"activityTitle": "🔴 Monitor DOWN",
"facts": [
{ "name": "Monitor", "value": "Acme API" },
{ "name": "URL", "value": "https://api.acme.co/health" },
{ "name": "Type", "value": "HTTP" },
{ "name": "Detail", "value": "Down from 2/3 locations: London, New York" },
{ "name": "Time", "value": "2026-07-25T08:41:07.000Z" },
{ "name": "Failing Locations", "value": "London (503), New York (503)" },
{ "name": "Passing Locations", "value": "Sydney (291ms)" }
],
"markdown": true
}]
}Microsoft Teams is one of eight channels built into PulseStack. Mix and match them per monitor. Zapier and Google Chat are not native but connect through the Webhook channel.
SMS alerts are included on the Team and Enterprise plans, and available as an add-on on Starter and Pro. See all integrations.
Any check that can fail can post to your Teams channel, including SSL certificate, DNS record and domain expiry monitors. Build the coverage you need across web, network and infrastructure.
Status codes and response time on any URL.
Confirm a page contains, or is missing, specific text.
TCP connection checks to any host and port.
Verify a specific TCP port is open and accepting connections.
Endpoint checks with custom headers and request bodies.
Watch cron jobs and workers that must check in on schedule.
A card a set number of days before expiry (7 by default), or when the certificate is not trusted.
A card when no record of the chosen type holds the value you expect.
A card a set number of days before the registration runs out (7 by default).
Route production HTTP and API monitors to the on-call channel so incidents surface fast and get owned.
TCP Ping, Port and DNS monitors post to the infra channel, catching reachability and record changes before customers notice.
SSL certificate and domain expiry alerts land in Teams a set number of days ahead (7 by default, adjustable per monitor), giving admins time to renew without a last-minute scramble.
Heartbeat monitors watch cron jobs and workers, alerting the channel the moment a scheduled task fails to check in.
One Teams channel per client keeps every account's alerts separated and easy to hand to the right responder.
Keyword monitors flag broken pages or missing text, so the team hears about a botched deploy in the same channel they plan in.
The Microsoft Teams channel unlocks from the very first paid tier. Pick the plan that matches how many monitors you run.
GBP 0
5 monitors, HTTP only, no chat channels
GBP 9/mo
50 monitors, all monitor types, Teams alerts
GBP 19/mo
150 monitors, 30s checks, competitor tracking
GBP 39/mo
500 monitors, 30s checks, server diagnostics, 3 seats
GBP 99/mo
2,000 monitors, 30s checks, 5 seats
Every paid plan includes a 14-day trial, and neither the trial nor Free needs a card.
Start with Send test next to the contact on the Alert Contacts page. It posts a test card straight away, and if Teams refuses it the error shows the status code Teams returned.
Microsoft switched off Office 365 connector webhooks (the old Incoming Webhook connector, with webhook.office.com or outlook.office.com/webhook URLs) in May 2026, Message Center MC1181996. The contact form accepts any https:// address, so an old connector URL still saves but no longer posts. Create a Workflows webhook as in step 1 and replace the URL.
The URL only works while its workflow exists and is turned on, and it runs as the account that created it, so removing that account or deleting the workflow stops the posts. Some organisations also restrict the Workflows app; an administrator has to allow it.
If a monitor has any contacts ticked under Notify on failure, only those are alerted. Tick the Teams contact, or untick everything so the monitor alerts every contact.
Cards are posted when a monitor goes down or recovers, not on every check, so a monitor that was already down when you added Teams posts nothing until it recovers. If a card you did get looks wrong, see why a monitor status can be wrong.
PulseStack™ posts each alert once and does not retry, so a card the workflow rejected or never received at that moment is not sent again.
Yes. Microsoft Teams is one of PulseStack™'s eight native alert channels, alongside Email, SMS, Slack, Discord, PagerDuty, Telegram and Webhooks. You connect it with a Teams Workflows webhook URL, so there is no PulseStack™ app to install.
Each alert is a MessageCard posted to the channel your workflow targets. The title reads Monitor DOWN or Monitor RECOVERED, followed by facts for Monitor, URL, Type, Detail and Time, plus Failing Locations and Passing Locations for monitors checked from London, New York and Sydney.
In Teams, create a workflow from the template Send webhook alerts to a channel (older tenants list it as Post to a channel when a webhook request is received), pick the team and channel, and copy the HTTP POST URL it generates. In PulseStack™, open Alert Contacts, click Add contact, choose Microsoft Teams, paste the URL and click Send test. Every contact gets both failure and recovery alerts.
When a monitor goes down and again when it recovers. There is no consecutive-failure setting: HTTP, keyword, API, ping and port monitors are marked down only when at least two of the three locations fail, and SSL, DNS, domain expiry and heartbeat checks are re-tested 3 seconds after a failure, so a single blip does not post a card.
All nine monitor types: HTTP(S), Keyword, TCP Ping, Port, API, Heartbeat, SSL certificate, DNS record and Domain expiry.
Yes. Create one workflow per Teams channel, add each URL as its own Microsoft Teams contact, then tick the right contact under Notify on failure on each monitor. Infrastructure alerts can go to your ops channel while marketing sites post elsewhere.
Set up the native Teams channel in minutes and let every failure and recovery post straight to the channel your team already watches.