💡 Our Technical Review in summary
Microsoft has announced an updated timeline and technical enhancements for the retirement of legacy Office 365 Connectors in Microsoft Teams. To facilitate a smoother transition to Workflows webhooks, the retirement deadline has been extended to **April 30, 2026**. Additionally, Microsoft has introduced key technical updates to Workflows webhooks—including backward compatibility for legacy message formats—to reduce the migration effort for IT teams and developers.
#### Impact
- Extended Timeline: The previous retirement date of March 31 has been pushed to April 30, 2026, providing an additional month for organizations to finalize their migration.
- MessageCard Compatibility: Workflows webhooks now support the `MessageCard` payload format. This is a significant update, as it allows existing integrations to function without requiring a complete rewrite of the JSON payload to the Adaptive Card format. However, interactive buttons within these legacy cards will not render.
- Shared Channel Support: Workflows webhooks can now be used to post messages in shared channels, addressing a previous feature gap.
- Pending Private Channel Support: While not yet available, Microsoft has confirmed that support for posting to private channels via Workflows is expected to be released later in February 2026.
- Service Continuity: Any legacy Office 365 Connectors that are not migrated to the Workflows-based solution by the deadline will cease to function.
#### Action Required
- Inventory Existing Connectors: Review your Microsoft Teams environment to identify all active Office 365 Connectors currently in use.
- Update Webhook URLs: Create new Workflows webhooks to replace existing legacy URLs. Use the Power Automate-based “Workflows” app in Teams to generate these new endpoints.
- Test Payload Rendering: Even though `MessageCard` formats are now supported, verify how your current notifications appear in Teams. If your workflow relies on buttons, you may need to transition to Adaptive Cards to maintain functionality.
- Prepare for Private Channels: If you have connectors in private channels, wait for the upcoming update later this month before attempting to migrate those specific instances.
- Migration Completion: Ensure all integrations are transitioned to Workflows webhooks before the April 30, 2026, deadline to avoid service disruption.
Microsoft Official Update
Service: N/A
Category: planForChange
Severity: normal
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.
[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.
