Microsoft Teams alerts that someone claims by name.

Uptimia posts an Adaptive Card into the Teams channel you choose, the moment a failure is confirmed by independent checkpoints. With an escalation policy attached (Professional plan and above), one button on that card claims the incident — the ladder stops, and a name and a time go on record.

Post alerts into Teams → See what it watches
Setup guideConnecting Teams through Workflows, step by step Open the guide

Outage news travels bottom-up

A customer hits a dead page, calls support, support raises a ticket, and it gets triaged to the engineer who can fix it. That hour went on delivery, not repair.

The assumption

Watching the site is someone’s job

Site down
11:47 · silent
whose, exactly?
Everyone assumes someone
nobody is assigned

Refreshing the website all day is nobody’s actual job — so the site only gets checked once something already feels wrong.

The usual route

The news arrives as a ticket

Site down
11:47 · silent
58 min later
“Checkout not working”
ticket #4188 · 12:45

By the time the ticket is triaged and routed, the outage has been public for most of an hour — and the clock only starts for engineering now.

Flip the direction: let the outage file its own report, straight to the people who fix it. The same 11:47 failure, with Uptimia posting to the Ops channel.

The morning the checkout stopped working

The checkout at caldmont.com started returning HTTP 503 at 11:47. The homepage was still green, no ticket had been raised, and the card was already sitting in Ops › Alerts.

11:47 Checkout — caldmont.com goes downHTTP 503, confirmed by 3 checkpoints — the card lands in Ops › Alerts Ops › Alerts
11:49 Priya claims it from the cardOne click on Acknowledge — no sign-in, escalation stops, MTTA on record Ops › Alerts
11:54 The web team joins in the replies“The 11:40 deploy hung — restarting the pool now” Ops › Alerts
12:09 The all-clear posts to the same channelRecovery card: UP after 22 minutes — the ticket queue never heard Ops › Alerts
22 mindown → up
The helpdesk never rang0 tickets
Detection, ownership, fix and confirmation all happened in the channel. Support took zero calls about it, because it was over before lunch traffic.
3 checkpoints agreedclaimed in 2 mindown 22 min0 tickets raised
The escalation ladder stayed cold. Priya’s click at step one meant no SMS, no phone tree, no manager ping. ladder stopped

Webhook, routing, safety net

The webhook is made inside Teams and pasted into Uptimia. Nothing is installed on your servers, and no bot needs tenant approval.

Step 12 min

Add the Workflows webhook

Open the Workflows app in Teams, search “webhooks” and pick Send webhook alerts to a channel. Choose the team and channel, copy the link, paste it into Uptimia, save it, then press Test.

Ops › Alerts Send test
test card in Ops › Alerts · wiring proven
Step 21 min

Choose what posts where

Outages to the Ops channel, certificate warnings to a quieter one, performance alerts to the web team. Each monitor names its own destination.

Alert this monitor to
Ops › AlertsOps › WarningsEmail
Checkout — caldmont.com → posts to Ops › Alerts
Step 3optional

Add the safety net

If nobody claims a card, Uptimia escalates — SMS to the on-call engineer, then the next name on the list. Escalation policies come with the Professional plan and above; maintenance windows keep planned work silent on every plan.

If nobody acknowledges — escalate
Ops › Alerts → +5 min SMS on-call → +15 min email
maintenance windows muted · quiet hours honoured
Technical setup guide

Connect Microsoft Teams to Uptimia

Every click, in the Help Center: building the Workflows webhook, pasting the URL into Uptimia, and attaching the Teams contact to the monitors that should post there.

  • Why the setup uses the Workflows app
  • Add the Microsoft Teams integration
  • Attach the Teams contact to your monitors
  • If alerts still don’t arrive
Open the setup guide → help.uptimia.com

Every monitor type posts here

The portal answering doesn’t prove the certificate is valid, the domain is paid for or last night’s backup ran. Twelve monitor types cover those failures — uptime, transactions, page speed, SSL, domains, malware, blacklists, DNS records, API chains, servers, heartbeats and real-user data — and each posts to the channel you picked.

Uptime checksEvery public URL you own
SSL certificatesAlerted on your expiry threshold
Domain expiryLapse dates on watch
Server metricsThe VM under the site
1 Teams channel Ops › Alerts — one channel, full coverage
Heartbeats & cronScheduled jobs, verified
TransactionsSign-in & checkout, replayed
Virus & malwareSite reputation, rescanned on schedule
Page speedRegressions caught early
Whichever check fails first, Ops sees the same card format — the certificate, the DNS zone, the server or the site itself. 12 types · 1 channel

Three channels, three urgencies

A Workflows webhook belongs to one channel, and each monitor picks which webhook it uses. So what must be seen now can sit apart from what gets reviewed on a Friday.

Ops › Alerts
Claims attention now — notifications on for the rotation.
Uptime & HTTP checks
Sign-in & checkout flows
Server metrics & heartbeats
urgent · on-call watches it
Ops › Warnings
Reviewed in the weekly ops sync, fixed on schedule.
SSL certificate expiry
Domain expiry
Virus & malware flags
planned · never pages
Web › Performance
The web team’s own feed — trends, not alarms.
Page speed & Core Web Vitals
Uptime on marketing pages
Campaign landing pages
informational
Engineering lives somewhere else? The same alert also reaches SlackDiscordTelegramPagerDutyWebhooksEmail & SMS

Put downtime on the Ops channel.Before it reaches the helpdesk.

Every monitor type, every channel, 30 days free.

Start your free 30-day trial →
30 days free no credit card cancel anytime

The platform behind the card

Teams is the delivery route. Detection, evidence and the customer-facing side come from the Uptimia account underneath it.

Monitors, incidents and history

Monitors, incidents, response times and history — the overview for when a card isn’t enough.

Store — caldmont.comUPTIME · 99.98% Checkout flowTRANSACTION · OK caldmont.comSSL · 61 DAYS

Confirmed, not guessed

A failed check is re-run from up to 3 other checkpoints. Only their agreement sends a card.

171+ checkpoints · 70+ countries

Status pages for stakeholders

A public status page on your own domain tells customers and management the same story, automatically.

● status.caldmont.com · live

Reports for the review

Monthly uptime PDFs land in the inbox — evidence for SLAs and vendor reviews.

June · 99.98% · PDF sent

MTTA, measured

Every claim is timestamped, so response time is a number you can report, not a feeling.

avg. response · 2 min

Escalation, quiet hours, maintenance

Unclaimed cards climb to SMS and the next responder. Change windows and nights stay quiet.

Step 1 — Ops › AlertsTEAMS Step 2 — on-callSMS · +5 MIN Change windowMUTED

How Microsoft Teams alerts work

Uptimia checks your websites, certificates, servers and key user flows from 171+ locations, and posts Adaptive Cards into Microsoft Teams through a Workflows webhook. A card names the monitor, what failed and when it started, and tags the alert type and its priority; on an escalation-policy incident (Professional plan and above) it also carries the incident number and an Acknowledge button that pauses the ladder for everyone. Recovery posts to the same channel with how long it was down. Uptimia uses the current Workflows method and still accepts the older Office 365 connector URLs Microsoft has been retiring.

“The alert email goes to IT”

Shared mailboxes don’t escalate

Site down
11:47 · confirmed
read when?
it-alerts@ mailbox
many readers · no owner

A shared mailbox has plenty of readers and no owner. Everyone can see the alert; no one is on the hook for it.

Teams notifications

A channel has witnesses

Site down
11:47 · confirmed
seconds
Ops › Alerts
claimed, by name

Posted where the team already works, the alert is public, claimable and hard to quietly miss — and the claim goes on the record.

Every event

The cards Uptimia posts to Teams

One card per stage of the incident, escalation included — the channel ends up reading like its log.

See all 12 alert channels →
CardPosts whenWhat it carries
Down alertIndependent checkpoints agree it failedMonitor, what failed, since when — plus the Acknowledge button on escalation-policy incidents
AcknowledgementSomeone opens the Acknowledge linkWho claimed it, at what time, ladder paused
EscalationNobody claims it in timeThe next responder — SMS, another channel, or both
Grouped incidentRelated monitors fail togetherOne card for the group, a follow-up as others join
RecoveryThe monitor comes backThe all-clear and how long it was down
Test cardYou connect the webhookProof the wiring works, before anything real

Microsoft Teams alerts FAQ

01How do I get website-down notifications in Microsoft Teams?+
In the channel you want, open the Workflows app, search “webhooks” and add Send webhook alerts to a channel. Copy the link it creates and paste it into Uptimia as a Microsoft Teams contact. Save it, send the test card, then assign the monitors that should use it.
02Does IT need to roll anything out?+
The webhook is created with the Workflows app that ships with Teams — no software on your servers, no bot to approve, no tenant-wide install. Where a tenant restricts who may add workflows to a channel, the channel owner or an admin does it once.
03We still have old webhook.office.com connector URLs — do they work?+
Yes. Microsoft has been retiring the legacy Office 365 connectors, and Uptimia uses the current Workflows method — but older connector URLs are still accepted, so an existing setup keeps working while you migrate.
04Which channel should the alerts go to?+
Wherever the people who act on them already are — most orgs use an Ops or IT alerts channel. Each monitor picks its own destination, so outages, certificate warnings and performance digests can go to different channels in different teams.
05What if a card scrolls past unseen?+
On the Professional plan and above, the escalation ladder catches it: if nobody clicks Acknowledge within the window you set, Uptimia moves to SMS, then to the next responder on the list. Claiming the card at any point stops the climb.
06Can we prove how fast we responded?+
Yes — every acknowledgement is timestamped and every incident keeps its time-to-acknowledge, so MTTA is a reportable number for the ops review, not an estimate.
07What exactly is in a card?+
The monitor’s name, what failed, the time it started, the alert type and the priority. On an escalation-policy incident (Professional plan and above) the card also carries the incident number and the Acknowledge button. The recovery card adds how long it was down, so the channel documents the whole incident.
08Will planned maintenance spam the channel?+
No — maintenance windows mute alerts for planned work, related failures are grouped into one incident instead of a card per monitor, and quiet hours hold non-urgent notices overnight.
09What can Uptimia watch besides the website being up?+
Twelve: uptime, multi-step sign-in and checkout flows, page speed, SSL certificates, domain expiry, malware, blacklists, DNS records, API chains, server metrics, heartbeats from scheduled jobs, and real-user monitoring. All of them post to Teams.
10Is the Teams integration licensed separately?+
No — Microsoft Teams is one of 12 built-in alert channels on every Uptimia plan, including the 30-day free trial. No credit card required to test it.

The next outage posts itself.

Webhook, test card, monitors assigned — from then on Ops is the first to know, and every incident carries a name and a time.

Set up Teams alerts →
Works with Workflows webhooks Nothing to install 30-day free trial No credit card
Microsoft Teams is one of 12 built-in alert channels — every Uptimia monitor type can post to it.