- Open Workflows in TeamsIn the Teams channel, open the channel's More options menu and choose Workflows.
- Pick the webhook templateSearch for "webhook" and choose "Send webhook alerts to a channel" (older name: "Post to a channel when a webhook request is received").
- Select team and channelName the workflow, confirm the team and channel, and save it.
- Copy the URLCopy the webhook URL shown when the workflow is created, or from the workflow's details page.
- Add the destinationIn Uptime Tracker go to Integrations → Add destination, choose "Set up Microsoft Teams" (or "Use a webhook URL" where the Teams app is offered), paste the Workflows webhook URL and choose "Add destination".
- Send a testChoose "Send test" and check the channel.
Microsoft Teams alerts are available on the Pro and Team plans. Uptime Tracker posts an Adaptive Card to a Teams channel through a Workflows webhook, the Power Automate-based replacement for the retired Office 365 connectors.
Before you start
- A workspace on Pro or Team. On Free the Microsoft Teams card shows Needs Pro.
- Permission to create workflows in Teams. Some organizations restrict this; ask your Microsoft 365 administrator if the templates are missing.
Quickest: add the Uptime Tracker Teams app
- In Integrations → Add destination, find Microsoft Teams and choose Connect Microsoft Teams (Pro or Team; owners, admins and operators). The connection wizard opens on Integrations → Destinations; choose Add to Microsoft Teams and Teams opens its install dialog; nothing needs to be downloaded.
- Add the app to a team channel, a group chat or a personal chat.
- On the app's welcome message, press Connect to Uptime Tracker, sign in if asked, and pick the workspace. The destination appears verified on Integrations → Destinations. Choose Send test.
If Teams says the app isn't available, your organization only allows approved apps. Ask your Microsoft 365 administrator to allow it, or choose Download app package and upload it as a custom app (Apps → Manage your apps → Upload an app). You can also connect with a one-time code: choose Connect with a code and post @Uptime Tracker connect <code> in the channel (in a personal chat, just connect <code>).
Acknowledge from Teams: alert cards have Acknowledge and View incident buttons. The first press sends you a private link to link your Teams account to your Uptime Tracker sign-in; after that, presses acknowledge as you and the card shows who acknowledged. The bot also answers link and help. Removing the app, or deleting the channel or team, disables the destination; connecting the same channel again re-enables it.
If your organization blocks the app, use the Workflows webhook below, which needs no app.
Create the workflow in Teams
- In Microsoft Teams, go to the channel that should receive alerts.
- Open the channel's More options menu (…) and choose Workflows. You can also open the Workflows app from the Teams app bar.
- Search for "webhook" and choose Send webhook alerts to a channel. In older tenants the template is called Post to a channel when a webhook request is received.
- Name the workflow, for example "Uptime Tracker", confirm the Team and Channel, and save (Add workflow or Save).
- Copy the webhook URL that Teams shows. You can find it again on the workflow's details page.
The URL is on *.logic.azure.com or *.powerplatform.com. Treat it like a password: anyone who has it can post to the channel. Menu names in Teams change from time to time; if the channel menu has no Workflows entry, use the Workflows app.
Add it in Uptime Tracker
- Go to Integrations → Add destination, find Microsoft Teams and choose Set up Microsoft Teams (Use a webhook URL where the Teams app is offered).
- Enter a Name and paste the Workflows webhook URL.
- Choose Add destination, then Send test, and check that the card appears in the channel.
How to confirm delivery
A Workflows webhook accepts every request (HTTP 202) before the workflow runs, so Uptime Tracker cannot tell whether the card was actually posted. Under Integrations → Deliveries, accepted only means Teams received the request. The integration card and each Teams destination say so too. Confirm delivery in the Teams channel itself, and if nothing appears, open the workflow's run history in Teams or Power Automate: a failed run there shows why the card was not posted.
Legacy connector URLs
Older incoming-webhook URLs on *.webhook.office.com are accepted while Microsoft still delivers them. Microsoft has retired those connectors, so create a Workflows URL for new setups and replace legacy ones.
What you receive
- A card when a monitor's failure is confirmed, titled DOWN: monitor name, with the time, a Reason: line (for example
HTTP 503 Service Unavailable) and the redacted target. - A recovery card with the measured outage length when the monitor comes back.
- Repeat reminders until acknowledged, if your routing rule enables them.
Change the workflow URL
To move alerts to another channel or replace a legacy connector URL, create the new workflow, then choose Edit connection on the destination, paste the new URL and choose Save connection. Saving also re-enables a destination that was disabled after delivery failures.
Troubleshooting
- "The endpoint is not a valid teams URL": the host must end in
.logic.azure.com,.powerplatform.comor.webhook.office.com. - Deliveries says accepted but nothing appears: Workflows accept every request first and post afterwards, so the failure happens inside Power Automate and is never reported back. Open the workflow's run history in Teams or Power Automate to see why; common causes are a deleted channel, a turned-off workflow or a workflow owner who left the organization.
- HTTP 401, 403 or 404 under Integrations → Deliveries: the workflow URL is no longer valid. The destination is disabled with a reason. Create a new workflow and paste its URL with Edit connection.
Google Chat, Pushover, ntfy, Gotify, Mattermost and Rocket.Chat are also on Pro; see their own articles in the Alerts section.
Frequently asked questions
Which plan do I need for Microsoft Teams alerts?
Pro or Team. Free includes email, Slack, Discord, Telegram and generic webhooks.
Which Teams template should I use?
"Send webhook alerts to a channel" in Workflows. In older tenants it is called "Post to a channel when a webhook request is received".
Do old Office 365 connector webhooks still work?
Legacy *.webhook.office.com URLs are accepted while Microsoft still delivers them. Use a Workflows URL for new setups.
Can I alert several Teams channels?
Yes. Create one workflow and one destination per channel, then use routing rules to choose which monitors go where.
Why does Deliveries show accepted when nothing was posted?
Teams Workflows accept every request before the workflow runs, so accepted only means Teams received it. Check the channel and the workflow's run history in Power Automate.