Uptime and certificate alerts in Microsoft Teams

hostnag posts an Adaptive Card for every alert to a Teams channel through Workflows.

Start free See pricing

Included on Pro and Business.

PlansFreeProBusiness

Down

Heading: [Critical] https://www.example.com/ is down
Text: Down from 2 of 3 locations (US East, Frankfurt). Last error: unexpected_status: 503.
Group: Client A
Monitor: Marketing site
Target: https://www.example.com/
Down since: 12 Sept 2026, 07:58 UTC
Locations: US East, Frankfurt
Status code: 503
Last error: unexpected_status: 503
Buttons: Acknowledge, Open monitor

Set up

01
Create a Workflows webhook
Office 365 connectors were retired. In Teams, open Workflows and use the template 'Post to a channel when a webhook request is received', then paste that URL.
02
Paste the Workflows URL
The URL must be on logic.azure.com or api.powerplatform.com; a retired Office 365 connector URL is refused.

What arrives

Rendered by the same code that sends it.

Back up

Heading: [Recovered] https://www.example.com/ is back up after 1 h 15 min
Text: https://www.example.com/ answered again from every location. It was down for 1 h 15 min.
Group: Client A
Monitor: Marketing site
Target: https://www.example.com/
Down since: 12 Sept 2026, 07:58 UTC
Duration: 1 h 15 min
Buttons: Acknowledge, Open monitor

Degraded

Heading: [Warning] https://www.example.com/ is responding slowly (2400 ms)
Text: https://www.example.com/ is up but slow: 2400 ms median across locations, above the threshold you set.
Group: Client A
Monitor: Marketing site
Target: https://www.example.com/
Latency: 2400 ms
Buttons: Acknowledge, Open monitor

Routing

Every alert follows the group's alert policy: which channels a route goes to and the minimum severity each one takes, in bands of critical, warning and info. Quiet hours hold non-critical alerts for email, Slack, Discord, SMS, Teams and Telegram until the window closes, then deliver one digest; critical alerts are never held, and webhook, PagerDuty and Opsgenie always deliver right away since they hand off to another machine, not a person. A maintenance window on a group or a monitor suppresses alerts for its duration while checks keep running. An alert nobody acknowledges escalates through up to three tiers, each after its own number of minutes, and can be acknowledged with one tap from the alert message itself.

Questions

Why is my old Office 365 connector URL refused?

Microsoft retired Office 365 connectors; hostnag only accepts a Workflows URL.

What does the card show?

The alert title and its facts, with an Acknowledge button next to Open monitor when the alert can be acknowledged.

Watches

Alerting and status pagesEvery alert routed to the right channel at the right severity, held during quiet hours and maintenance, escalated until it's acknowledged.Uptime monitoringWebsites, APIs and anything that answers on a port, checked every minute from up to four places, with a failure confirmed before anyone is paged.

Add a host. Hear about it in Microsoft Teams.

Start free