How to post website enquiries to a Microsoft Teams channel

This guide covers Microsoft Teams in depth. For a side-by-side look at Slack and Teams, see Send website form submissions to Slack or Microsoft Teams.

What happened to incoming webhooks in Microsoft Teams?

Microsoft has retired Office 365 connectors, including the Incoming Webhook connector that most form tools used to post into Teams, and replaced them with Workflows. The final switch-off ran from 18 May to 22 May 2026. After that, Microsoft says connectors no longer function, so a webhook URL created the old way stops posting.

Microsoft first announced the retirement on 3 July 2024 with an October 2024 end date, then extended it several times after feedback: to the end of 2025, to 31 March 2026, then to 30 April 2026, before publishing the final May schedule on 14 April 2026. If your enquiries stopped appearing in a channel around May 2026 and you set them up with a connector, this is the likely reason.

The replacement is the Workflows app inside Teams, which runs on Power Automate. A workflow gives you a new URL to post to, and then puts the message in the channel you chose.

Who can set up a Teams webhook with Workflows?

Any Teams user can create one from the Workflows app, and Microsoft says the webhook templates and the Teams webhook trigger don't need a premium licence. Power Automate's general-purpose HTTP trigger is treated differently, so if you build a flow from scratch with a trigger other than "When a Teams webhook request is received", check the licence first [CHECK]. Your organisation's admin can also restrict apps, so if Workflows is missing from the channel menu, ask them.

Before you start, note how these workflows behave:

• Messages are posted by the Flow bot, not by you, and you can't give webhook posts a custom name or icon.

• A workflow belongs to the person who created it, not to the team or channel. If that person leaves and nobody else owns the flow, it can stop, so add a colleague as co-owner.

• Anyone who has the URL can post to the channel. Keep it out of your website's public code and out of shared documents.

Microsoft added posting to shared channels in February 2026 and was rolling out private channel support in the Workflows app by 20 April 2026; its developer page still listed private channels as a known issue later [CHECK], so test with the channel you actually plan to use.

How to create the workflow in a Teams channel

You create it from the channel itself, using a ready-made template. Microsoft currently calls the template "Send webhook alerts to a channel"; older guides, and some tools' set-up screens, call it "Post to a channel when a webhook request is received".

1. 1

   Open the channel's menu

   In Microsoft Teams, go to the team and channel that should get enquiries, then select More options (...) next to the channel name.

2. 2

   Choose Workflows

   Select Workflows, then search for the "Send webhook alerts to a channel" template.

3. 3

   Confirm the team and channel

   Check the template has picked the right team and channel, and sign in to any connection it asks for.

4. 4

   Save and copy the URL

   Select Save. When the workflow is created, copy the webhook link it shows. This is the URL your form tool or code will post to.

5. 5

   Add a co-owner

   Open the Workflows app, find the flow under Your workflows and add a colleague as co-owner, so it keeps running if you leave.

You can turn the workflow off or delete it later from the Workflows app: scroll to Your workflows, select More actions (…) next to it, then Turn off or Delete.

If posts stop arriving later, check three things in this order. Is the workflow still on in Your workflows? Does its owner still work for you, with an active account? And has someone made a new workflow, which gives a new URL, without updating the form tool? Power Automate keeps a run history for each flow, which shows whether requests reached it and failed, or never arrived at all.

What does a website form need to send to a Workflows URL?

It needs to send an HTTP POST with a JSON body, and the clearest format is an Adaptive Card. Microsoft says Workflows accepts both Adaptive Cards and the older Message Card format, but buttons in Message Cards don't work. A minimal card with a heading and one line of text looks like this:

{
  "type": "message",
  "attachments": [
    {
      "contentType": "application/vnd.microsoft.card.adaptive",
      "content": {
        "$schema": "http://adaptivecards.io/schemas/adaptive-card.json",
        "type": "AdaptiveCard",
        "version": "1.2",
        "body": [
          { "type": "TextBlock", "text": "New enquiry from the website", "weight": "Bolder" },
          { "type": "TextBlock", "text": "Jane Smith, 07700 900123: Can you quote for a boiler service?", "wrap": true }
        ]
      }
    }
  ]
}

Microsoft's limits are generous for a contact form: a message can be up to 28 KB, and more than four requests in a second are throttled. In practice, the post has to come from a server, not from the visitor's browser, or the URL ends up in your page source for anyone to use. And because text a visitor typed goes into the card, it should be escaped or kept to plain text rather than trusted as formatting.

Which way of posting website enquiries to Teams suits you?

The right route depends on where the form lives and whether you want to write code. Power Automate's own form trigger only works with Microsoft Forms, so a form on your website needs one of the other three.

If your enquiry form already is a Microsoft Form, linked from your site, Power Automate can handle it: Microsoft's documentation shows flows that start with "When a new response is submitted" and read the answers with "Get response details", and you can add a Teams post as the next step. Microsoft Forms can also email the form's owners about each response from its own settings, with no flow at all.

Zapier lists Microsoft Teams actions including Send Channel Message and Send Message with Card, and some of its Teams features need the Zapier app installed from the Teams store. At the time of writing its Free plan allows 100 tasks a month and two-step Zaps [CHECK], and every submission uses a task.

Whichever you choose, spam goes to the channel too. How to stop contact form spam covers the filters worth turning on first.

How does a form alert service post to Teams?

A form alert service reads each submission on your site and posts it to the Workflows URL you give it, so you only build the workflow in Teams. What is a form notification service? explains the idea in more detail.

With Formcrier, go to Alert destinations → Add destination → Microsoft Teams, which lists the steps for adding the workflow. Paste the workflow's HTTP POST URL into "Workflows URL" and press Post a code to the channel. A six-digit code appears in the channel; type it into Formcrier to finish. The code works for 24 hours, which proves the URL really posts where you think it does. Each Teams message counts as one alert, and the Free plan includes 10 a month. The Microsoft Teams alerts page has more.