Microsoft Teams integration
Microsoft Teams is on the map, not in the product yet.
Pipeline events posted to your Teams channel through the Workflows path Microsoft actually supports.
How it works
The Teams integration uses a Teams Workflows webhook, the one supported path in 2026. In Teams, you create a Workflows flow from the template that posts to a channel when a webhook request is received, and paste the resulting URL into SearchHandled. From then on, draft-ready reviews, publish confirmations, indexing verification, and ranking wins post to your chosen channel as formatted cards, and since the December 2025 update Workflows webhooks reach private and shared channels too.
We built on Workflows deliberately: Microsoft disabled classic Office 365 connectors and their incoming webhooks in May 2026, with the migration cutoff having passed in March. We never accept a legacy connector URL, because a connection built on one would already be dead. In the loop, Teams plays the same role Slack does for other stacks, keeping the pipeline visible where your team already works, with each message linking back to the item it concerns.
Best forTeams-based organizations who want the content pipeline reporting into their channels instead of waiting to be checked.
Setup, step by step
- In Teams, open Workflows and create a flow from the template named 'Post to a channel when a webhook request is received'.
- Choose the team and channel the flow should post to.
- Copy the webhook URL the flow generates.
- Paste the URL into SearchHandled's Teams connector and pick which event types you want.
- Send the test notification to confirm the card lands in the channel.
Best practices
Use the Workflows template, not a legacy connector
Classic Office 365 connector webhooks were disabled in May 2026 and their URLs are dead. The Workflows template takes about a minute to set up and is the path Microsoft supports going forward.
Create the flow with a durable account
The flow lives under the account that creates it, and it stops if that account is disabled. Create it with an account that will stay, or recreate the flow and update the URL when people move on.
Route by channel with multiple flows
One webhook posts to one channel. If editors want review notices and a wider channel wants wins, create a flow per channel and split event types across the connections.
Expect the Flow bot as the sender
Workflows webhook messages post under the default Flow bot identity. The card content and links are ours; the sender name and icon are Microsoft's, and no webhook configuration changes that.
Known issues
What practitioners actually report, from official docs, issue trackers, and community forums.
Classic connector webhooks are dead in 2026
Office 365 connectors were disabled in May 2026 after a March 31 migration cutoff, so any legacy incoming-webhook URL no longer accepts posts.
How we handle itThe connector only accepts Teams Workflows webhook URLs and rejects legacy connector URLs at setup with an explanation, so a connection can never be built on the retired path.
devblogs.microsoft.com
Messages post as the Flow bot
Notifications appear under the default Flow bot name and icon rather than a custom SearchHandled identity, which can look generic in a busy channel.
How we handle itOur cards carry clear SearchHandled branding and event context in the body, so messages are unmistakable at a glance even though the sender identity belongs to the platform.
learn.microsoft.com
The flow depends on its owning account
A Workflows flow created by an account that is later disabled stops running, and notifications quietly stop with it.
How we handle itWe detect delivery failures and flag the connection as unhealthy in your dashboard, and recreating the flow under an active account and pasting the new URL restores notifications in minutes.
learn.microsoft.com
Questions teams ask
- We have an old incoming webhook URL from a Teams connector. Can we use it?
No. Microsoft disabled classic Office 365 connector webhooks in May 2026, so those URLs are dead. The Workflows template replaces them and takes about a minute to set up.
- Can notifications go to a private channel?
Yes. Since Microsoft's December 2025 update, Workflows webhooks support posting to private and shared channels, and the flow's channel picker includes them.
- Why do messages come from 'Flow bot' instead of SearchHandled?
Workflows webhook messages post under the default Flow bot identity, and Microsoft does not offer a custom name or icon on this path. The card content itself is clearly branded and links back to SearchHandled.
Not connectable yet
Start with the plan, not the connector.
Build a Growth Map from your site to see the work itself. Approved pages can leave through the export or the webhook today, and telling us Microsoft Teams matters moves it up the rollout.