Back to latest version
You're viewing a historical snapshot from Feb 12, 2026. This is not the latest version.

Metadata at Feb 12, 2026

Last Updated

Feb 12, 2026

Published Oct 31, 2025

Service

Microsoft Teams

Tag

Updated message
User impact
Admin impact
Retirement

Act by

Apr 30, 2026

MC1181996 - Migration update for Office 365 connectors retirement in Teams – webhook URL support

Message Center

What changed since this version

removed textadded text

Updated February 12,April 15, 2026: We have updated the timelinetimeline, added known limitations, and content.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:

The migration deadline

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 extendedthe final deprecation timeline. All connector-based webhooks must be migrated to Workflows before April 30,May 18, 2026 (previously March 31). 

How this affects your organization:


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

What’s Coming Next:Known Limitations:

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

  • Bot icon and enhancements — includingname 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 for private channels — will be later this month.

      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 by April 30,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.

Snapshot from Feb 12, 2026

Updated February 12, 2026: We have updated the timeline and content. 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.

When this will happen:

The migration deadline is extended to April 30, 2026 (previously March 31). 

How this affects your organization:
  • Who is affected: Organizations using Office 365 Connectors in Microsoft Teams

What’s Coming Next:

Additional details and enhancements — including support for private channels — will be later this month.

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 by April 30, 2026 to avoid service disruption.
Compliance considerations:

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