Back to latest version
You're viewing a historical snapshot from Oct 31, 2025. This is not the latest version.

Metadata at Oct 31, 2025

Published

Oct 31, 2025

Service

Microsoft Teams

Tag

Updated message
User impact
Admin impact
Retirement

Act by

Mar 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 April 15, 2026: We have updated the timeline, added known limitations, and confirmed private channel support. Thank you for your patience.

Introduction

Update 10/28/2025: New information related to Office 365 Connectors Retirement in Teams – Webhook URL Migration (MC808160). We’ve extended the migration deadline to give organizations more time to transition. We’re also making progress on feature parityThe 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.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 is extended to March 31, 2026. Feature parity improvements

Office 365 Connectors will be available bypermanently disabled on the following schedule: 

  • Deprecation rollout starts: December 2025May 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.

  • Teams

    Known Limitations:

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

    • WhatBot icon and name customization is not available when posting Adaptive Cards via webhook. Messages will happen:
        display with the default Workflows bot (Flow bot) identity. Custom icons and display names are not supported for Adaptive Card payloads.
      • Migration deadline extendedInteractive 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 March 31, 2026.
      • By December 2025, Workflows webhooks will support:
        • Posting messageCarduse Adaptive Cards instead of MessageCards. MessageCard-formatted payloads (no need to reformat to Adaptive Cards).
        • Posting messages and Adaptive Cards to sharedwill render content but will not support button rendering or private channels.
      other interactive components.
    What you can do to prepare:
    • Plan to transition from

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

      • Review your existing Office 365 Connector usage.
      • Begin migrating to Workflows webhooks by March 31, 2026.as soon as possible.
      • PrepareComplete migration before May 18, 2026 to avoid service disruption.
      • If your workflows rely on interactive card elements, update your payloads to use new webhook capabilities starting December 2025.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 Oct 31, 2025

Introduction

Update 10/28/2025: New information related to Office 365 Connectors Retirement in Teams – Webhook URL Migration (MC808160). We’ve extended the migration deadline to give organizations more time to transition. We’re also making progress on feature parity for Workflows webhooks.

When this will happen:

The migration deadline is extended to March 31, 2026. Feature parity improvements will be available by December 2025.

How this affects your organization:
  • Who is affected: Organizations using Office 365 Connectors in Microsoft Teams.
  • What will happen:
    • Migration deadline extended to March 31, 2026.
    • By December 2025, Workflows webhooks will support:
      • Posting messageCard formatted payloads (no need to reformat to Adaptive Cards).
      • Posting messages and Adaptive Cards to shared or private channels.
What you can do to prepare:
  • Plan to transition from Office 365 Connectors to Workflows webhooks by March 31, 2026.
  • Prepare to use new webhook capabilities starting December 2025.
Compliance considerations:

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