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

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. 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 supportedWe’re also making progress on feature parity 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.webhooks.

Office 365 ConnectorsThe migration deadline is extended to March 31, 2026. Feature parity improvements will be permanently disabled on the following schedule: 

• Deprecation rollout starts:available by 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, 2026December 2025.

How this affects your organization:

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

  Teams.

• Known Limitations:What will happen:

  When using

  • Migration deadline extended to March 31, 2026.
  • By December 2025, Workflows webhooks, please be aware of the following limitations:
    webhooks will support:
    • Bot iconPosting messageCard formatted payloads (no need to reformat to Adaptive Cards).
    • Posting messages 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 buttonsto shared 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.private channels.

If you are currently using

• Plan to transition from Office 365 Connectors in Microsoft Teams:
  • Review your existing Office 365 Connector usage.
  • Begin migrating to Workflows webhooks as soon as possible.by March 31, 2026.
  • Complete migration before May 18, 2026 to avoid service disruption.
  • If your workflows rely on interactive card elements, update your payloadsPrepare to use Adaptive Cards.
  • Test your migrated workflows to ensure they function as expected.new webhook capabilities starting December 2025.
  Compliance considerations:

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