Summary
Details
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:
- Posting messages using MessageCard‑formatted payloads (no reformatting required; however, button rendering will not be supported)
- 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.
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.
No compliance considerations identified, review as appropriate for your organization.
Change History
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:
- Posting messages using MessageCard‑formatted payloads (no reformatting required; however, button rendering will not be supported)
- 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.
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.
No compliance considerations identified, review as appropriate for your organization.
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:
- Posting messages using MessageCard‑formatted payloads (no reformatting required; however, button rendering will not be supported)
- 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.
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.
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:]- 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
messageCardformatted payloads (no need to reformat to Adaptive Cards). - Posting messages and Adaptive Cards to shared or private channels.
- Posting
- Plan to transition from Office 365 Connectors to Workflows webhooks by March 31, 2026.
- Prepare to use new webhook capabilities starting December 2025.
No compliance considerations identified, review as appropriate for your organization.
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:
- Posting messages using MessageCard‑formatted payloads (no reformatting required; however, button rendering will not be supported)
- 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.
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.
No compliance considerations identified, review as appropriate for your organization.
Never Miss a Microsoft 365 Update
Join thousands of IT professionals who rely on DeltaPulse for real-time Microsoft 365 change intelligence, automated notifications, and community insights.