Migration update for Office 365 connectors retirement in Teams – webhook URL support
Microsoft 365 Message Center Archive by Merill Fernando · Microsoft may not have sent this notice to your tenant.Action date
Schedule dates changed in the text
Date phrases in schedule sentences differ between the versions this installation saw- Seen 15 Apr 2026
April 30, 2026→ April 2026, April 20, 2026, May 18, 2026, May 22, 2026 - Seen 12 Feb 2026
March 31, 2026, December 2025→ April 30, 2026
Read from date phrases in Microsoft's text, not from notice metadata. A changed phrase can be a moved rollout, a new milestone or just rewording; "What changed" below shows which.
What the notice says
Microsoft’s text, with source markup removedWhat changed
Between archive captures, newest firstUpdated
February 12,April 15, 2026: We have updated thetimelinetimeline, added known limitations, andcontent.confirmed private channel support. Thank you for your patience.Introduction We’ve extended the migration deadline to give organizations more time to … 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:The migration deadlineOffice 365 Connectors will be permanently disabled on the following schedule: Deprecation rollout starts: May 18, 2026 Deprecation rollout completes: May 22, 2026 This isextendedthe final deprecation timeline. All connector-based webhooks must be migrated toApril 30, 2026 (previously March 31).Workflows before May 18, 2026. How this affects yourorganization:Whoorganization: Who is affected: Organizations using Office 365 Connectors in Microsoft TeamsWhat’s Coming Next: Additional detailsKnown 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 andenhancements — including supportdisplay names are not supported for Adaptive Card payloads. Interactive cards are not supported forprivate channels —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 willbe later this month.not support button rendering or other interactive components. What you can do to prepare: If you are currently using Office … usage. Begin migrating to Workflows webhooks as soon as possible. Complete migrationby April 30,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. Compliance considerations: No compliance considerations identified, review as appropriate for your organization.- Act by
30 Mar 2026→ 30 Apr 2026
Introduction Update 10/28/2025: New information related to Office 365 Connectors Retirement in Teams – Webhook URL Migration (MC808160).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.We’re also making progress on feature parityThe 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 forWorkflows webhooks.customers currently using Office 365 Connectors. When this will happen: The migration deadline is extended toMarch 31, 2026. Feature parity improvements will be available by December 2025.April 30, 2026 (previously March 31). How this affects your organization:Who is affected: Organizations using Office 365 Connectors in MicrosoftTeams. What will happen:Migration deadline extended to March 31, 2026. By December 2025, Workflows webhooksTeams What’s Coming Next: Additional details and enhancements — including support for private channels — willsupport:Posting messageCard formatted payloads (no need to reformatbe later this month. What you can do toAdaptive Cards). Posting messages and Adaptive Cards to shared or private channels. What you can do to prepare:Plan to transition from Office 365 Connectorsprepare: If you are currently using Office 365 Connectors in Microsoft Teams: Review your existing Office 365 Connector usage. Begin migrating to Workflows webhooksby March 31, 2026. Prepare to use new webhook capabilities starting December 2025.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.- Act by
- · first version seen
Linked documentation
Microsoft pages the notice links toThe notice links to no Microsoft Learn or Support page that this installation reads.
Related public evidence
No related evidence found in this installation's recent collection. This does not establish that no announcement exists.
Not confirmed here
What this page cannot tell you- Whether your tenant is affected: this is Microsoft's notice, not a check of your settings.