← Back
(Updated) Migration update for Office 365 connectors retirement in Teams – webhook URL support
MC1181996 · build prod-20251231-200323
Category
planForChange
Severity
normal
Major change
False
Last modified
2026-04-15 18:51:40
Summary source
Azure OpenAI (gpt-4.1)
Action by (Graph)
2026-04-30 07:00:00
Action by (AI)
Services
Microsoft Teams
Tags
Updated message, User impact, Admin impact, Retirement
Master tags
Admin
Roadmap IDs

One-line summary

Office 365 Connectors in Teams will be disabled starting May 18, 2026; migrate to Workflows webhooks before then, now supporting private channels and MessageCard payloads.

Similar updates

More like this
MC1121517 (Updated) Introducing the New Workflows Experience in Microsoft Teams
(Updated) Introducing the New Workflows Experience in Microsoft Teams A new, streamlined Workflows experience in Teams and SharePoint launches Feb 2026, featuring improved UI, easier automation, and natural language capabilities; existing workflows remain unaffected. Updated January 30, 2026: We have updated the timeline. Introduction We’re.
MC1138798 (Updated) Build SharePoint automations with Workflows—now aligned with the Teams experience
(Updated) Build SharePoint automations with Workflows—now aligned with the Teams experience SharePoint introduces new Workflows powered by Power Automate, offering a unified, streamlined automation experience across SharePoint, Teams, and Microsoft 365, starting April 2026. Updated March 17, 2026: We have updated the timeline. Introduction We’re.
MC1166868 (Updated) Microsoft Teams: Retirement of UKG and Blue Yonder managed connectors for Shifts
(Updated) Microsoft Teams: Retirement of UKG and Blue Yonder managed connectors for Shifts Microsoft is retiring UKG and Blue Yonder managed connectors in Teams Shifts on December 7, 2025; organizations must transition to partner apps or custom APIs. Updated November 21, 2025: We have updated the timeline. To streamline integration options and.
MC693865 (Updated) SharePoint Add-In retirement in Microsoft 365
(Updated) SharePoint Add-In retirement in Microsoft 365 SharePoint Add-Ins will retire and stop working after April 2, 2026; admins must migrate to SharePoint Framework (SPFx) as Add-Ins will become unusable. Updated March 2, 2026: This update serves as a f... Since the release of SharePoint Add-Ins in 2013, Microsoft has evolved SharePoint.
MC929014 (Updated) Microsoft Loop – Departed User Content Workflows for User-Owned Loop workspaces
(Updated) Microsoft Loop – Departed User Content Workflows for User-Owned Loop workspaces Admins can manage retention and deletion workflows for user-owned Loop workspaces, including Copilot Pages, when users leave; rollout begins mid-April 2026. ...2026:This message is associated with Microsoft 365 Roadmap ID 421612 [When this will happen:].
MC1068905 Microsoft Project for the web and Project in Teams will retire and redirect to Planner for the web and Planner in Teams
Microsoft Project for the web and Project in Teams will retire and redirect to Planner for the web and Planner in Teams Project for the web retires in early August 2025; users will be redirected to the new Microsoft Planner for the web and Teams, with seamless migration and some feature changes. The new Microsoft Planner for the web (.

Details

Summary
Office 365 Connectors in Teams will be disabled May 18–22, 2026. Migration to Workflows webhooks is required, supporting MessageCard payloads and private channels. Limitations include no bot icon customization and no interactive buttons for MessageCards. Begin migration early and test workflows before the deadline.

Body (from Message Center)

Updated April 15, 2026: We have updated the timeline, added known limitations, and confirmed private channel support. Thank you for your patience.

[Introduction]

We’ve extended the migration deadline to give organizations more time to transition. The following capabilities are now supported with Workflows webhooks:

  1. Posting messages using MessageCard‑formatted payloads (no reformatting required; however, button rendering will not be supported)
  2. Posting messages to shared channels

These updates significantly reduce migration friction for customers currently using Office 365 Connectors.

New — April 2026: Private channels are now supported for Workflows webhooks through the Power Automate portal. Selection of private channels directly within the Workflows app in Teams is rolling out fully by April 20, 2026.

[When this will happen:]

Office 365 Connectors will be permanently disabled on the following schedule: 

  • Deprecation rollout starts: May 18, 2026
  • Deprecation rollout completes: May 22, 2026

This is the final deprecation timeline. All connector-based webhooks must be migrated to Workflows before May 18, 2026.

[How this affects your organization:]

Who is affected: Organizations using Office 365 Connectors in Microsoft Teams

[Known Limitations:]

When using Workflows webhooks, please be aware of the following limitations:

  • Bot icon and name customization is not available when posting Adaptive Cards via webhook. Messages will display with the default Workflows bot (Flow bot) identity. Custom icons and display names are not supported for Adaptive Card payloads.
  • Interactive cards are not supported for MessageCard-formatted payloads. If your scenario requires interactive elements such as actionable buttons or input fields, you will need to use Adaptive Cards instead of MessageCards. MessageCard-formatted payloads will render content but will not support button rendering or other interactive components.
[What you can do to prepare:]

If you are currently using Office 365 Connectors in Microsoft Teams:

  • Review your existing Office 365 Connector usage.
  • Begin migrating to Workflows webhooks as soon as possible.
  • Complete migration before May 18, 2026 to avoid service disruption.
  • If your workflows rely on interactive card elements, update your payloads to use Adaptive Cards.
  • Test your migrated workflows to ensure they function as expected.
[Compliance considerations:]

No compliance considerations identified, review as appropriate for your organization.

Raw JSON (for debugging)

Expand/collapse the full payload below.
Show/hide raw
{
  "snapshot_item": {
    "action_required_by": "2026-04-30T07:00:00Z",
    "ai_action_required_by": null,
    "ai_actions": [
      "Review Office 365 Connector usage",
      "Migrate to Workflows webhooks",
      "Test migrated workflows",
      "Update payloads if interactive card elements are used"
    ],
    "ai_master_tags": [
      "Admin"
    ],
    "ai_model": "gpt-4.1",
    "ai_summary": "Office 365 Connectors in Teams will be disabled starting May 18, 2026; migrate to Workflows webhooks before then, now supporting private channels and MessageCard payloads.",
    "ai_topics": [
      "Teams",
      "Power Platform"
    ],
    "category": "planForChange",
    "details_map": {
      "Summary": "Office 365 Connectors in Teams will be disabled May 18\u201322, 2026. Migration to Workflows webhooks is required, supporting MessageCard payloads and private channels. Limitations include no bot icon customization and no interactive buttons for MessageCards. Begin migration early and test workflows before the deadline."
    },
    "id": "MC1181996",
    "importance": 5,
    "is_major_change": false,
    "last_modified": "2026-04-15T18:51:40Z",
    "ms_products": [
      "Teams"
    ],
    "platforms": null,
    "roadmap_ids": [],
    "services": [
      "Microsoft Teams"
    ],
    "severity": "normal",
    "tags": [
      "Updated message",
      "User impact",
      "Admin impact",
      "Retirement"
    ],
    "title": "(Updated) Migration update for Office 365 connectors retirement in Teams \u2013 webhook URL support"
  }
}