Post a confirmed outage
The card goes out once enough independent EU locations fail the check often enough in a row, both thresholds sit in your package, not on the first failed request.
Use Uptimeify with Microsoft Teams.
One Power Automate workflow, and every confirmed outage arrives as a card in the channel your team already lives in. No second tool to check.
What lands in Microsoft Teams
Everything the alert pipeline sends into Microsoft Teams is on this list, and nothing beyond it. Read it once and you know what your team will see.
Post the recovery
The same channel gets the all clear, carrying the time it resolved and how many minutes the outage lasted.
Send an Adaptive Card
Power Automate workflows receive the Adaptive Card they expect, titled green, amber or red depending on how bad the event is.
Match the format to the URL
A Power Automate workflow gets the Adaptive Card, a leftover Office 365 connector URL still gets MessageCard, the format Microsoft switched off in May 2026.
Fill the card with facts
Status, the error with its status code, customer, organisation, the checking locations and the start time sit in the card as a fact set.
Warn before certificates and domains expire
Expiring TLS certificates, expiring domains and blocklist hits reach the same channel, early enough to act without a rush.
A channel per monitor
Each channel is its own workflow URL, so a client's outage reaches the people who look after that client instead of everyone.
Send a test message
The dashboard posts a test card into the channel while you set it up, so the first real alert is not the first delivery attempt.
Keep the workflow URL encrypted
The workflow URL is stored encrypted rather than as plain text, and only an https target is accepted.
Teams that run their monitoring on Uptimeify
Minutes to set up. Then it runs on its own.
1. Create the workflow in Teams
Open the channel, then the three dot menu, then Workflows, and pick the template that posts to a channel when a webhook request arrives.
2. Name it and pick the channel
Give the workflow a name, choose the team and the channel the alerts should land in, then add it.
Workflow URL
prod-14.westeurope.logic.azure.com/workflows/xxxxStored encrypted
3. Paste the URL into Uptimeify
Add the URL as a Teams channel, assign the monitors it covers, and send the test message.
Before you connect Microsoft Teams.
No. Microsoft switched Office 365 connectors off in May 2026, so a connector URL on an old channel no longer delivers anything. A Power Automate workflow is the route now, and it is what the setup creates.
Yes. Every channel is its own workflow URL, and you assign monitors and clients to it. A client's outage then reaches the people who look after that client, not everyone.
No. Your quota covers monitors and the monthly SMS and voice allowance. Alerts over email, webhook, Teams or Slack do not draw on it.
The attempt shows up under History & Logs → Alerts with the status code Teams returned, and a hanging endpoint is cut off after fifteen seconds so it cannot stall the alerts queued behind it.
As soon as the outage is confirmed. How many re-checks that takes is yours to set per package, which is the same setting that keeps a single slow response from paging anyone.
Every alert, where your team already works.
Connect Microsoft Teams once, and every confirmed outage reaches the channel that is already open.