Microsoft Teams uptime alerts workaround for StillOnline
StillOnline does not ship a native Microsoft Teams connector today. If your company lives in Teams, you can still route downtime context there without pretending Teams is the primary paging system.
The safest setup is simple: keep StillOnline owner alerts on email, Telegram, or Slack, then forward a copy into Teams for visibility.
Quick answer
StillOnline sends owner alerts through email, Telegram, or Slack; Free includes one owner channel and Pro/Ultimate include all three via pricing. Microsoft Teams can receive a copy through a channel email address or a Power Automate flow, both documented by Microsoft Teams channel email and Power Automate connectors. Use Teams for shared incident awareness, not as the only wake-up path.
Recommended pattern
Use StillOnline to detect the failure and wake the owner. Use Teams to keep the support, sales, or customer success channel informed after the owner confirms the issue.
| Need | StillOnline setup | Teams workaround |
|---|---|---|
| Wake the operator | Email, Telegram, or Slack owner alert | Do not depend on Teams only |
| Share incident context | Public status page post | Post link into Teams |
| Notify a team channel | Owner email copy | Channel email or Power Automate |
| Customer-facing update | /s/{id} status page | Link from support macros |
Option 1: Channel email
Teams channels can expose an email address when the tenant allows it. Create a mailbox rule from your owner alert email to the Teams channel address, then test it with a non-production monitor.
This keeps the StillOnline product setup unchanged. It also avoids giving a third-party automation tool permission to post into every workspace where your team works.
Option 2: Power Automate
Power Automate can watch a mailbox and post a message into Teams. Use a narrow rule: sender is StillOnline, subject contains the monitor name, and the action posts a short message plus a link to your public status page.
Keep the flow boring. A flow that rewrites incidents, calls several APIs, and opens tickets is harder to debug during an outage than a simple copy-to-channel action.
How to describe this in your runbook
Write: StillOnline alerts the owner; Microsoft Teams receives a routed copy. That wording is accurate for buyers and support, matches how Teams channel email works, and avoids claiming a native StillOnline Teams connector that does not exist.
Related guides
- Telegram uptime alerts
- Slack uptime alerts webhook
- Webhook platform status page
- Status page subscribers vs owner alerts
FAQ
Does StillOnline have native Microsoft Teams uptime alerts?
No. StillOnline owner alerts are email, Telegram, or Slack today. For Teams, route an email copy or Power Automate message and document it as a workaround.
Is Teams reliable enough for StillOnline owner paging?
Use Teams for shared visibility, not as your only wake-up channel. Keep at least one direct owner channel in StillOnline settings, especially for production APIs.
Can StillOnline post incident updates into Teams?
Not directly as a native connector. Post the public status page link or route email into Teams after you publish an incident update.
What StillOnline plan do I need for this workaround?
Free can use one owner channel, usually email. Pro or Ultimate lets you keep email plus Telegram and Slack active, which gives the Teams forwarding rule a cleaner source.