← Al Davies, 250 High Street

Teams webhook stopped working? Replace it with a Workflows webhook

Short answer: if a form, printer, site monitor or script used to post alerts into a Teams channel and now posts nothing, the old Office 365 connector webhook was retired. Microsoft switched those connectors off in Teams between May 18 and May 22, 2026. Build a new webhook in the Workflows app in Teams, copy its URL, and paste that URL into the sender in place of the old one.

Microsoft's post "Retirement of Office 365 connectors within Microsoft Teams" moved the date several times. Its final update, from April 14, 2026, set the shutdown to begin May 18, 2026 and finish May 22, 2026, and said: "After these dates, Office 365 Connectors will no longer function."

How to tell this is your problem

The old webhook URL still looks fine. The sender may even report success. The channel just stays empty. So check where the URL came from. If someone made it through a channel's Connectors menu (an "Incoming Webhook" connector), it is an old connector webhook. A webhook made in the Workflows app is the replacement and is not affected by this retirement notice.

Microsoft's post told every owner to move each connector-based webhook to a Power Automate-based workflow before the shutdown began.

Before you start

  1. Find every sender that posts to Teams. Write down each one and the channel it posts to.
  2. Pick one person to own the new workflow. Our advice, not a Microsoft rule: use a shared service account, not a personal login. Microsoft's page explains why: "Workflows are linked only to specific users (referred to as owners of the workflow) and not to a Teams team or channel." If that person leaves and no co-owner exists, the workflow can become an orphan flow.
  3. Check the Workflows app is allowed in your tenant. Microsoft's connector reference says actions that post cards "require Workflows (formerly Power Automate) app availability and setting to the app to the 'allow' state in the Teams admin center." If it is blocked, ask your Teams admin.

Build the replacement

Exact names may differ on your screen.

  1. In Microsoft Teams, open the team and the channel that should get the alerts.
  2. Select More options (...) next to the channel name.
  3. Select Workflows.
  4. Search for the template "Send webhook alerts to a channel" and select it. Microsoft's support page also lists "Send webhook alerts from specific people to a channel" and "Send webhook alerts from people in an org to a channel", and warns: "Each template has a different authentication type."
  5. Choose the Team and the Channel. Configure the other parameters the screen asks for.
  6. Select Save.
  7. On the workflow details page, use the copy option to copy the webhook URL.

You can also start from scratch in Power Automate with the trigger "When a Teams webhook request is received". Microsoft's reference says that trigger lets you "specify whether anyone, any user in the tenant, or only a specific subset of users in the tenant are allowed to call the trigger."

Swap the URL in the sender

  1. Open the settings of the form, printer, monitor or script that sends the alerts.
  2. Find the field that holds the old webhook address.
  3. Paste the new URL from the Workflows app in its place. Save.
  4. Trigger a test alert.

Microsoft's example of a test request is a POST with a JSON body such as {"text": "Hello from a webhook workflow!"}. If your sender can send a test message, use it. The workflow then posts to the channel.

What changes from the old connector

Microsoft's post lists these limits for the new route:

Limits to know about

If the new webhook does nothing

When to get help

You can build all of this yourself in Microsoft 365. If you would rather have it built and tested for your team, I do that. A tracker like this is a fixed price: $5,000 for one, built in 2 weeks. See "What a SharePoint tracker costs to build". Bring one example of the problem to a free call.

Tell me what's still manual

I am Al Davies. I run 250 High Street LLC and build SharePoint trackers and Power Automate flows for operations teams. I work remotely. The first call is free, and I will not try to sell you anything.

See trackers I built: Tools I built

FAQ

Why did my Teams webhook stop working?

The Office 365 connector behind it was retired. Microsoft switched those connectors off between May 18 and May 22, 2026, and named Power Automate-based workflows as the replacement.

Is there a new Teams incoming webhook?

Yes. Use the Workflows app and the template "Send webhook alerts to a channel", or the trigger "When a Teams webhook request is received".

Can I keep my old webhook URL?

Plan on a new one. The Workflows app gives you a new URL to copy after you save the workflow, and the sender needs that URL.

Does a Workflows webhook still support buttons on cards?

Microsoft says interactive cards are not supported for MessageCard payloads. For buttons or input fields it says to use Adaptive Cards.

Who should own the new workflow?

Our advice, not a Microsoft rule: a shared service account with a co-owner. Microsoft says a workflow without an owner or co-owner can become an orphan flow.

Sources