communication api_deprecation ai_generated partial

Microsoft Teams incoming webhook connector returns 404 or stops working after connector deprecation

ID: communication/teams-webhook-connector-deprecation

Also available as: JSON · Markdown
72%Fix Rate
80%Confidence
3Evidence
2023-01-01First Seen

Version Compatibility

VersionStatusIntroducedDeprecatedNotes
any active — — —

Root Cause

Microsoft deprecated Office 365 Connectors for Teams webhooks in 2024, moving to Workflows (Power Automate) instead. Existing webhooks may stop working. The new Workflows-based webhooks have a different URL format and payload structure.

generic

Workarounds

  1. 90% success Migrate to Workflows (Power Automate) based webhooks 
    Teams -> channel -> Workflows -> 'Post to a channel when a webhook request is received'. Use the new URL with Adaptive Card format.
  2. 88% success Use Adaptive Card JSON format for new webhook payloads 
    {"type": "message", "attachments": [{"contentType": "application/vnd.microsoft.card.adaptive", "content": {"type": "AdaptiveCard", "$schema": "http://adaptivecards.io/schemas/adaptive-card.json", "version": "1.4", "body": [{"type": "TextBlock", "text": "Hello"}]}}]}
  3. 82% success Use Microsoft Graph API for more reliable Teams integration 
    Graph API: POST /teams/{team-id}/channels/{channel-id}/messages for programmatic message posting

Dead Ends

Common approaches that don't work:

  1. Continue using existing O365 Connector webhook URLs indefinitely 85% fail

    Microsoft is deprecating O365 Connectors. Existing URLs will stop working after the retirement date. New connectors can no longer be created in many tenants.

  2. Use the same payload format with new Workflows webhook URL 82% fail

    Workflows webhooks expect Adaptive Card JSON format, not the old MessageCard format used by O365 Connectors. Payload format is completely different.