Microsoft Teams uptime alerts

Updated 25 October 2026 · By the Upcertain team

Create the workflow in Teams

1. In the Teams channel, open the ... menu and choose Workflows (or add the Workflows app to the channel).
2. Pick the template Post to a channel when a webhook request is received.
3. Confirm the team and channel, then create the workflow.
4. Copy the URL Teams shows. It ends in .webhook.office.com, .logic.azure.com or .powerplatform.com.

Add it in Upcertain

1. In Upcertain, open Settings, Alert channels and choose Microsoft Teams. Owners, admins and editors can add channels.
2. Paste the webhook URL.
3. Pick the events to send: Down, Up (recovery) and SSL certificate expiry.
4. Tick Pre-select on new monitors if this should be the default for monitors you create from now on. Existing monitors keep their own choice.
5. Save, then use Send a test in the channel list to post a test message.
6. Open each monitor that should alert here and add the channel under its alert settings, with an optional delay and repeat interval.

What arrives in the channel

• Down: the monitor's name and address, the cause (for example HTTP 503, a timeout or a missing keyword), when it started, and buttons to acknowledge or view the incident.
• Still down: a reminder with the time so far, if you set a repeat interval on the monitor's channel (every 5 to 1440 minutes). Acknowledging the incident stops reminders.
• Up: the recovery with the cause and the total downtime, in the same channel.
• SSL certificate expiry: a warning on the days you chose before a certificate expires.
• Grouped alert: if alert grouping is on and several monitors fail within a few minutes, one message lists them all instead of one message each.

Each alert is an Adaptive Card with the title, summary and fields, and buttons to acknowledge or open the incident. The acknowledge button opens Upcertain, where a signed-in owner, admin or editor confirms it.

Things that trip people up

• The workflow belongs to its creator. If that person leaves the organisation, the workflow can stop. Create it with a shared or service account if your tenant allows.
• Tenant policy. Some organisations block Workflows or external webhooks; your Microsoft 365 administrator can allow the template.
• Retries. A rejected message is retried at 30 seconds, 1, 2 and 4 minutes, then marked failed.

Routing alerts

Each monitor chooses its channels, so customer-facing services can alert the support channel while internal tools alert only the platform team. Add confirmation checks so a single failed request never posts, and delay a channel for minor services if you prefer.