Teams Workflows alerts after connectors
Published . Updated .
This guide explains how to post a down and a recovery into a Teams channel with the webhook Microsoft documents now, and why an older connector URL will be rejected.
Create a workflow whose trigger is a webhook request, copy the URL on logic.azure.com, and paste that URL on the Teams card. Do not paste an Office 365 connector URL. Microsoft has retired those connectors. A client can point at a different channel. Send a test and confirm the card appears in the channel you chose.
Why the old URL stopped working
Microsoft's developer blog on the retirement of Office 365 connectors in Teams says those connectors are going away and tells customers to move webhook traffic to the Workflows app. The same post has described a final disable window in May 2026. An address on outlook.office.com or webhook.office.com is the old connector. The Watchbill refuses those hosts on purpose. A Workflows URL is on logic.azure.com or logic.azure.us.
Microsoft Learn's incoming-webhook page, cited above, says the Workflows app can receive an HTTP request and post a message or an Adaptive Card. It names the trigger as a Teams webhook request. This pass read that page's description of the trigger and the copy-the-link step. Teams menus still move, so if the button in your tenant is worded differently, follow the Learn page rather than a screenshot from last year.
Create the webhook
In Teams, open the Workflows app. Use the template that posts to a channel when a webhook request is received, or build a flow with that trigger. Choose the team and the channel. Save the flow. Copy the webhook URL. It should contain logic.azure.com or logic.azure.us.
Paste that URL on Alerting, then Microsoft Teams, and save. Leave the signing-secret field empty. Teams does not use the webhook signing secret. The URL itself is the credential, so it is stored encrypted and it is not shown again.
If the URL is on outlook.office.com, stop and create the Workflows URL instead. Saving the old host will be rejected.
What the channel sees
The message is an Adaptive Card. The first line is the summary, such as the check name and the word down or up. The second line is the target URL. A recovery is a second message. Teams does not close the first message. If you need one ticket that opens and closes, use ticket email as well and keep Teams for the people who live in the channel.
A test sends the same card and says it is a test. It can post into the real channel. Pick a channel that can stand a test, or delete the test message after you see it.
A different channel per client
The account URL is the default channel for clients that inherit the account set. On the client, choose Use a set on this client and check the Teams destination that posts to that client's channel. If you need a second URL, add another Teams destination and check only that one on the client.
You can also assign one Teams destination to selected clients. Clients that inherit the account set and are not selected will not get that destination. Clients that already have their own set are unchanged until you edit the set.
If the card never appears
Confirm the host is logic.azure.com. Confirm the flow is turned on. Microsoft Learn notes that a workflow owned by a person can stop when that person leaves. Give the flow a second owner, or a service account your tenant already uses for workflows, if your admin allows it. This guide does not name a license. Microsoft's retirement notes discuss Power Automate plans. Check the tenant if the flow says the account cannot save it.
A 429 or a 500 from the flow is retried. A 400 is not. The timeouts and the retry gaps are the same as for a signed webhook: 8 seconds to answer, then 60 seconds, 5 minutes, 15 minutes, and 60 minutes.
Name the flow after the channel, not after the person who clicked Save. When that person changes teams, the flow should still post. If your tenant requires a premium connector for the template you picked, that requirement is Microsoft's, and this guide does not restate a price. Pick the template Learn documents for a webhook request if the first template asks for a connector you do not have.
Keep Teams beside the ticket, not instead of it, when the contract says every client incident has a ticket number. The channel is where a person sees the words. The ticket is where the clock runs. A recovery in the channel does not close the ticket unless the PSA rule does that from the recovery mail.
If the card shows the target and not the client name you expected, the check name is what the summary uses. Rename the check if the channel should say the client first. The workflow does not look up your client list. It posts the body it was given. A private channel works only if the flow can post there. Microsoft has said private-channel support moved into Workflows. If your tenant cannot pick that channel, use a standard channel until it can.
How The Watchbill helps
On Pro and Business, a Teams Workflows URL receives a message when a confirmed outage opens and another when it closes. Connector URLs on the old Office 365 hosts are rejected. A client can use a different channel. The checking test and the first confirmed up do not post to Teams.
Sources
- Microsoft, retirement of Office 365 connectors in Teams. Accessed October 10, 2026.
- Microsoft Learn, create an incoming webhook. Accessed October 10, 2026.