How do I send uptime alerts to Microsoft Teams?

In UpDog, create (or pick) a monitor, then create an alert. In the alert modal, choose Microsoft Teams as the destination and follow the prompts to connect Teams (often via an incoming webhook/connector). Pick a channel and send a test alert.

Can I send Microsoft Teams uptime alerts to a specific channel?

Yes. Route production incidents to an ops channel and keep lower-urgency notifications elsewhere to avoid drowning the main team channels.

What should a Microsoft Teams uptime alert include?

Monitor name, state change (down/recovered), timestamp, and one link back to UpDog for the timeline and latest check details.

Why are Microsoft Teams uptime alerts not arriving?

Verify the Teams connection/webhook, confirm the channel selection, and ensure the monitor is assigned to the Teams notification target.

How do I reduce noise from Microsoft Teams uptime alerts?

Post only high-severity or high-signal monitors to Teams, separate prod from staging/dev, and tune check intervals and retries to avoid flapping spam.

How do I send downtime notifications to Teams and still page on-call?

Use Teams for visibility and coordination, then add an on-call tool (like PagerDuty) for escalation when a human must respond immediately.

Microsoft Teams alerts for uptime monitoring

Send uptime alerts to Microsoft Teams so incidents show up where the organization already coordinates. Keep posts consistent, route by ownership, and avoid noisy channels.

Start free All integrations

How UpDog + Microsoft Teams works

UpDog posts to Teams when a monitor changes state so incidents show up in the same place people coordinate. Use consistent naming and routing so the right team sees the right alerts.

What the alert includes

Monitor/service name + environment
State change (down/recovery) and timestamp
One link back to UpDog for timeline + check details

Recommended channel setup

Dedicated ops/status channel for production
Separate Teams channels for staging/dev
Route by ownership (API, frontend, infra, support)

What you can do with UpDog + Microsoft Teams

Send Microsoft Teams uptime alerts for downtime and recovery updates.
Route to the right channel (frontend, API, infra, support) so incidents land with the team that owns them.
Standardize incident posts so responders immediately know what broke and where to click next.

How to set it up (step-by-step)

Create an uptime monitor in UpDog (website, API endpoint, or scheduled job/heartbeat).
Create an alert for that monitor.
In the alert modal, choose Microsoft Teams as the destination.
Connect Teams using your org’s preferred method (commonly an incoming webhook or connector).
Select the Teams channel, save, then send a test alert.

Best practices

Keep production separate from staging/dev

Put production incidents in a dedicated ops/status channel. Keep staging and development monitors out of the main incident flow.

Make it obvious what’s broken

Name monitors so a message can be understood in one glance: service + environment + endpoint.

Use escalation for “must respond” incidents

Teams is excellent for coordination. If you need guaranteed response, pair it with an on-call tool like PagerDuty or SMS.

Troubleshooting

Teams alerts aren’t arriving: confirm the webhook/connection and that the monitor is assigned to Teams notifications.
Wrong channel: verify you’re using the correct webhook/channel mapping.
Spammy alerts: route only high-signal monitors to Teams and tune retries/intervals to reduce flapping.
Teams rejects the post: check connector permissions and any message formatting restrictions in your tenant.

FAQ

Create an alert in UpDog, choose Microsoft Teams in the alert modal, connect Teams, pick a channel, and send a test notification.

Yes. Route by ownership so the right team sees the alert first.

Service/monitor name, state change, timestamp, and one link back to UpDog for incident context.

Check the Teams webhook/connector, the selected channel, and that the monitor’s alert is routed to Teams.

Send only high-severity monitors to Teams, split prod from non-prod, and tune check intervals and retries.

Post to Teams for visibility, and route the same incident to PagerDuty or SMS for escalation when needed.

Related features

Other integrations

Build your alert stack:

PagerDuty – On-call schedules and escalation
Slack – For teams using both platforms
Email – Reliable inbox delivery
SMS – High-urgency escalation

Start monitoring for free

Create a monitor, connect Teams, and get the first alert where your org already coordinates.

Start free