Our old Teams webhook URL stopped working. Why?

If it is on webhook.office.com, it was an Office 365 connector, and Microsoft finished retiring those in May 2026. Create a Workflows webhook from the channel (More options → Workflows → Send webhook alerts to a channel) and paste the new link. FishOut refuses the old URL shape so the mistake shows at setup.

Do I need a Power Automate premium licence?

No. Microsoft says the Teams webhook templates and the Teams webhook trigger do not require a premium licence. The FishOut side is on every plan, Free included.

Can a FishOut alert @mention someone in Teams?

No, by design. Teams only notifies people who are listed as mention entities in the card, and FishOut never sends any — so a post titled “@everyone” cannot page your company.

Alerts stopped after a colleague left. What happened?

The workflow belonged to them. Workflows are owned by people rather than by the channel, and a flow with no co-owner can be orphaned and fail. An admin can add a co-owner and turn it back on; delivery history in FishOut shows teams_workflow_disabled or teams_unauthorized until then.

Can it post into a private channel?

Not today. Microsoft documents that the Teams webhook trigger cannot post to private channels yet, so point it at a standard channel with the right membership.

IntegrationsWorkplace chat

Brand mentions in a Teams channel

Teams is where a PR or IT team already lives, so a mention that lands there gets read by someone who can act on it. The catch is that Microsoft moved incoming webhooks from Office 365 connectors to Workflows, and most of the guides you will find describe the URL that no longer works.

Start free Read the alerts docs

Every alert channel is on every plan, including Free. The Teams webhook templates need no premium Power Automate licence.

[01] WHAT LANDS THERE/ A CHANNEL

A mention, as it arrives in Microsoft Teams

Rendered by the code that sends it, from a sample Google News post. Never the post body.

Comms · #press-and-brand

Workflowsnow

Relevant mention on Google News

AcmeMail outage leaves small businesses without support email for six hours

: Relevance 91
: Brand
: Negative
Labels: Has a problem

Open in FishOutView on Google News

[02] CONNECT IT/ SETUP

Point FishOut at a channel

4 steps, a few minutes end to end.

1
Open Workflows from the channel
In Teams, go to the channel, choose More options (…) next to its name, then Workflows. Search for the template Send webhook alerts to a channel and select it. Microsoft says these templates and the Teams webhook trigger need no premium licence.
2
Save it and copy the link
Confirm the team and channel, select Save, and copy the webhook link it shows. It is a long Power Automate URL with a signature in its query string. Treat it as a password: anyone holding it can post to the channel.
workflows url
```
https://prod-00.westus.logic.azure.com/workflows/<id>/triggers/manual/paths/invoke?api-version=2016-06-01&sp=…&sv=1.0&sig=…
```
3
Paste it into FishOut
Under Settings → Notifications, add a Microsoft Teams channel and paste the link. FishOut accepts Workflows URLs on logic.azure.com and environment.api.powerplatform.com, and refuses the retired webhook.office.com connector URLs outright, so a stale URL fails at setup rather than silently.
4
Set the floor, then add a co-owner
Pick mention.scored, set a relevance floor, and leave batching on. Then, in the Workflows app, add a co-owner to the flow: a workflow belongs to the person who created it, not to the channel.

Then set the floor

A Teams channel is shared with people who did not ask for alerts, so a low floor costs you goodwill as well as attention: the first week of irrelevant cards is when someone mutes the channel for everyone. Start at 75 for a comms channel, and route anything with negative sentiment about the brand to a second, smaller channel at 85 rather than lowering the first.

Settings · Notifications

Microsoft Teams

https://prod-00.westus.logic.azure.com/…

Healthy

Relevance floor75

Eventsmention.scored

Batch bursts5 min

[03] WHAT IS IN IT/ FIELDS

What Microsoft Teams receives, field by field

Built from the event’s envelope and nothing else, so a retry renders exactly the message the first attempt would have.

Field		How
Headline	Shown	The card’s bold first TextBlock. Google News has no Reply call, so it reads “Relevant mention”.
Post title	Clipped	Plain text, clipped at 200 characters; the link lives on the button.
Relevance, subject, sentiment, author	Shown	Rows of a FactSet, so they line up.
Reply hint and labels	Shown	Titled FactSet rows.
Open in FishOut · View on Google News	Shown	Two Action.OpenUrl buttons.
@mentions	Never	Teams only mentions people listed as entities, and FishOut never sends any.
Post body	Never	Never sent: the envelope does not carry it.

[04] TEN PINGS OR ONE/ DIGEST

A burst arrives as one message

Microsoft Teams batches by default. Here 9 posts were held after the first; they arrive together when the window closes, best first.

Comms · #press-and-brand · 5-min digest

Workflows+5m

Spike: “notchmail” — 21 posts today, usually 3 · 9 new mentions for AcmeMail

• Notchmail agrees to be acquired by a helpdesk suite (Google News · 93)
• What the Notchmail deal means for small support teams (Google News · 89)
• The shared-inbox market after this week (Google News · 80)
• AcmeMail says it will keep a free plan (Google News · 78)
• Analyst note: consolidation in support software (Google News · 70)
and 4 more

Open in FishOut

[05] WHAT WILL BITE YOU/ LIMITS

Microsoft’s limits, not ours

These are Microsoft’s constraints, checked against Microsoft Learn and Support. Failures are tracked per channel, so one broken destination never stops the others.

Office 365 connectors in Teams, the old webhook.office.com URLs, stopped working when Microsoft’s retirement rolled out between 18 and 22 May 2026. Any guide that tells you to “add the Incoming Webhook connector” is describing that. [source]

A message is capped at 28 KB, and over it Teams returns an error. A FishOut card is a fraction of that, because it carries the title and never the post body. [source]

Sending more than four requests a second throttles the connection. A burst digest is what keeps a busy hour inside that. [source]

A workflow is owned by people, not by the team. With no co-owner it can become an orphan when its owner leaves, and flows using that person’s connections can fail. [source]

Posting into a private channel through the Teams webhook trigger is not supported yet. Use a standard channel. [source]

The webhook trigger can be restricted to anyone, anyone in the tenant, or specific users. FishOut calls it anonymously, so it needs the first. [source]

In the channel’s delivery history
You see	It means	Do this
teams_workflow_not_found	The workflow or its trigger was deleted.	Create the workflow again from the channel and paste the new link.
teams_workflow_disabled	The flow was turned off — often because its owner left.	Have a co-owner or admin turn it back on in the Workflows app.
teams_unauthorized	The flow only accepts calls from signed-in users, or the signature was regenerated.	Set the trigger to anyone, or copy the regenerated URL.
invalid_destination	The URL is an Office 365 connector (webhook.office.com).	Those stopped working in May 2026; create a Workflows webhook.