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
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:
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.
The migration deadline is extended to March 31, 2026. Feature parity improvements
Office 365 Connectors will be available bypermanently disabled on the following schedule:
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:
messageCarduse Adaptive Cards instead of MessageCards. MessageCard-formatted payloads If you are currently using Office 365 Connectors in Microsoft Teams:
No compliance considerations identified, review as appropriate for your organization.
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:messageCard formatted payloads (no need to reformat to Adaptive Cards).No compliance considerations identified, review as appropriate for your organization.