Microsoft Teams Incoming Webhooks After the 2026 Connector Retirement
Microsoft retired legacy Teams connector webhooks in May 2026. Teams Workflows webhooks still work, but old Office 365 connector URLs may stop posting.
By Blake Johnston
Legacy Microsoft Teams incoming webhooks are not the same thing as Teams Workflows webhooks.
That distinction matters now.
Microsoft retired the old Office 365 Connector path for Teams in May 2026. If an app was posting through a legacy connector URL, that URL may no longer work. If an app is posting through a Teams Workflows webhook, the pattern is still supported.
Short version: old connector webhooks are retired; Teams Workflows webhooks are the replacement.
What changed in May 2026
Microsoft's Office 365 Connectors retirement affected connector-based webhooks in Teams. Microsoft said connector-based webhooks would be progressively disabled from May 18 to May 22, 2026, and directed customers to move to Power Automate-based Workflows.
That means a Teams notification setup from 2024 or 2025 may not be trustworthy in 2026 if it was created through the old connector flow.
The practical symptom is simple: the app still thinks Teams is connected, but messages no longer appear in the channel.
What still works
Teams Workflows can still receive an HTTP request and post a message into a Teams channel or chat. Microsoft's current Teams webhook documentation points users toward Workflows for this pattern.
For simple product notifications, that is often enough. A workflow URL can receive a JSON payload from your app, then Teams posts the message where the workflow is configured to post it.
For richer cards, Microsoft supports Adaptive Card payloads through this workflow model. That matters for product notifications because a good Teams message usually needs a title, a short summary, and a button, not just plain text.
Workflows webhook vs Teams app
There are two realistic ways to post product notifications into Teams in 2026.
| Approach | Best for | Tradeoff |
|---|---|---|
| Teams Workflows webhook | Simple channel notifications, fast setup, internal teams | User-created workflow, manual URL paste, weaker lifecycle handling |
| Teams app or bot | First-class install, channel selection, tenant identity, proactive messages | More engineering, Microsoft app setup, approval and admin consent work |
The Workflows webhook path is the pragmatic option when you need to post reminders and results into one Teams channel.
The Teams app or bot path is better when the integration itself is part of the product experience. It can handle installs, uninstalls, conversation references, proactive messages, and richer setup flows in a way a pasted webhook URL cannot.
Microsoft's Teams platform docs describe this more durable route as proactive bot messaging, which is the right model when an app needs to send scheduled messages after installation.
Why old Teams webhooks break
The old connector model gave teams a webhook URL directly from the Teams channel connector experience.
That URL was convenient, but it depended on the Office 365 Connector infrastructure Microsoft has now retired for Teams. Once that infrastructure is disabled for a tenant, messages sent to the old connector URL can fail even if the app still has the URL saved.
If your Teams webhook stopped working, check where the URL came from:
- If it came from Office 365 Connectors or "Incoming Webhook" connectors, replace it.
- If it came from Teams Workflows or Power Automate, it should be the supported path.
- If you need central admin control and smoother install behavior, consider a Teams app or bot.
What this means for Halftime
Halftime for Microsoft Teams uses Teams for the nudge and the result, while the game itself runs in the browser.
That model still makes sense after the connector retirement. The important detail is the connection method: Teams notifications should use a supported Teams Workflows webhook, not an old Office 365 Connector webhook.
For a daily game ritual, that means:
- Teams carries the daily game opening.
- Teammates play in the browser.
- Results and leaderboards return to the Teams channel.
- The channel gets one useful moment, not a stream of game mechanics.
When a Teams app is worth it
A Teams Workflows webhook is enough for a lot of teams.
A first-class Teams app becomes worth it when you need more than "post this message to this channel."
Consider a Teams app or bot if you need:
- A Slack-style "Add to Teams" install flow.
- Channel discovery instead of manual channel naming.
- Tenant, team, and channel identity stored cleanly.
- Install and uninstall lifecycle events.
- Proactive bot messages.
- Centralized admin consent.
- Marketplace or enterprise distribution.
That is a real product integration project, not a quick webhook swap. For many teams, Workflows webhooks remain the right first move.
How to fix a broken Teams notification setup
If an existing Teams integration stopped posting after May 2026, recreate it through Teams Workflows.
Use this checklist:
- Open the target Teams channel.
- Go to Workflows.
- Create a workflow that receives a webhook request and posts to the channel.
- Copy the workflow webhook URL.
- Replace the old connector URL in the product that sends Teams notifications.
- Send a test message before relying on it.
If the test message works, the notification path is back on supported ground.
The simple answer
Microsoft Teams webhooks did not disappear entirely.
The old Office 365 Connector incoming webhook path was retired for Teams in May 2026. The supported lightweight replacement is Teams Workflows webhooks. For deeper product integrations, a first-class Teams app or bot is the more durable architecture.
For Halftime, that means Teams can still carry daily game reminders and results, but old connector URLs should be replaced with Teams Workflows webhook URLs.
If your team runs on Microsoft Teams, Halftime for Microsoft Teams gives the channel a daily two-minute browser game, async play, leaderboards, and Teams result moments. Start with one team.