July 3rd, 2024
heartmind blownlikecelebrate17 reactions

Retirement of Office 365 connectors within Microsoft Teams

Connor Rodewald Trent Hazy
Connor ,
Trent

Update 2/5/2026: New information related to Office 365 Connectors Retirement in Teams 

We have several updates to share as part of our ongoing effort to support your migration from Office 365 Connectors to Power Automate–based Workflows in Microsoft Teams.

Message Card support is now available in Workflows.

  • You can continue to use the Message Card format when migrating your existing Office 365 Connectors. For technical details and guidance, see the updated documentation on Microsoft Learn: https://learn.microsoft.com/microsoftteams/platform/webhooks-and-connectors/what-are-webhooks-and-c…

Note: message cards formatted payload with button rendering is not supported. Please leverage adaptive card for interactive cards.

In addition, we have enabled the Workflows bot (Flow bot) to post messages in shared channels. This unblocks a number of migration scenarios that rely on cross-team or cross-channel communication. Support for private channels is still in progress, and we expect to share more details in later this month.

We recognize that these capabilities took longer than expected to become available. To ensure you have sufficient time to complete your migrations, we are extending the deadline to deprecate Office 365 Connectors to April 30, 2026.

Thank you for your patience and continued feedback as we work to deliver feature parity and a smooth migration experience.

— End of update –

Update 10/28/2025: New information related to Office 365 Connectors Retirement in Teams – Webhook URL Migration

We’ve extended the migration deadline to March 31, 2026 to give organizations more time to transition. In addition, we’re making progress on feature parity for Workflows webhooks. By December 2025, you can expect support for:
  • Posting messageCard formatted payloads (no need to reformat to Adaptive Cards)
  • Posting messages and adaptive card to shared or private channels
Thank you for your patience as we work to deliver these enhancements and make migration smoother!

— End of update –

Update 09/09/2025: New information related to Office 365 Connectors Retirement in Teams – Webhook URL Migration
We’re making progress on adding webhook capabilities to the Workflow app. By early October 2025, we’ll share a clear timeline for supporting:
  • Posting messageCard formatted payloads (no need to reformat to adaptive cards)
  • Posting to shared or private channels
  • Customize Workflows bot icon and name
Thank you for your patience as we work to deliver these enhancements!

— End of update —

Update 04/11/2025: New information related to Office 365 Connectors Retirement in Teams – Webhook URL Migration

We are still developing a method for webhooks in the Workflow app to support the following scenarios and will share more details before the end of August 2025.
  • Post messageCard formatted message payloads (so you do not have to reformat the payload to adaptive card)
  • Post to private channels

— End of update —

Update 10/16/2024: New information related to Office 365 Connectors Retirement in Teams – Webhook URL Migration

As shared in the last communication, we are publishing guidance for owners of webhook-based connectors to update their URLs with a new structure. To allow ample time for replacing URLs, connector owners will have until January 31, 2025, which is an extension from our previous deadline of December 31, 2024. See below for complete guidance.

 

Webhook-based connectors within the O365 Connectors service in Teams are transitioning to a new URL structure due to the implementation of further service hardening updates. During this transition, you may receive notifications to update your configured connector to use the new URL. We strongly recommend that you update your connector immediately to prevent any disruption to connector services. URLs for all webhook-based connectors must be updated by January 31, 2025 for the connectors to continue posting messages into Teams. Keep in mind the entire O365 Connectors service in Teams will be retired at the end of 2025, so consider moving your webhooks to the Workflows app within Teams to avoid conducting another migration. Documentation: Create incoming webhooks with Workflows for Microsoft Teams – Microsoft Support
This change is needed only for webhook-based Connectors such as Incoming Webhook and third-party connectors where a URL is provided for posting messages. The change is not required for polling-based connectors such as RSS.

 

To update webhook URLs for existing O365 Connectors, follow these steps below or within this documentation: Manage Microsoft 365 connectors and custom connectors – Microsoft Teams | Microsoft Learn
  1. Go to Manage Channel in a Teams channel, select Edit under the Connectors option, and select Configured section. Review the existing connections listed on this page.
    • Screenshot showing the configured connections in a Teams channel that need attention.
  2. Do one of the following to generate a new URL:
    • For connectors that contain a webhook URL, select Manage and Update URL.
    • Screenshot showing the option to update a webhook URL.
    • For other types of connectors, remove the connector and reconfigure the connector to generate a new URL.
  3. Replace the old URL with the new URL (or the new connection in the service that triggers the post). You’ll know the new URL is ready for you to copy when the Configure page shows a message that the URL is updated (“Url is up-to-date”).
    • Screenshot showing a confirmation after URL update.
Additional documentation:
Create incoming webhooks with Workflows for Microsoft Teams – Microsoft Support
Browse and add workflows in Microsoft Teams – Microsoft Support

 

Note about parity features for the Workflows app
We are currently developing a method for webhooks in the Workflow app to support the following scenarios and will share more details before March 30, 2025.
  • Post messageCard formatted message payloads (so you do not have to reformat the payload to adaptive card)
  • Post to private channels

— End of update —

Update 07/23/2024: We understand and appreciate the feedback that customers have shared with us regarding the timeline provided for the migration from Office 365 connectors. We have extended the retirement timeline through December 2025 to provide ample time to migrate to another solution such as Power Automate, an app within Microsoft Teams, or Microsoft Graph.

— End of update —

Office connectors in Microsoft Teams deliver content and service updates directly from third-party services into a Teams channel. By using Office connectors, users can receive updates from popular services such as Azure DevOps Services, Trello, Wunderlist, GitHub, and more. Office connectors post these updates directly into the chat stream. This functionality makes it easy for all team members to stay in sync and informed on relevant information.

Image 01

Why are we retiring Office 365 connectors?

Starting August 15th, 2024 we will be retiring the Office 365 connectors feature from Microsoft Teams. We recommend Power Automate workflows as the solution to relay information into and out of Teams in a scalable, flexible, and secure way.

Power Automate workflows not only offer a much deeper catalog of Office connectors (see all connectors) but also ensure that your integrations are built on an architecture that can grow with your business needs and provide maximum security of your information. These changes are aligned to the Microsoft Secure Future Initiative, and our company-wide priority to safeguard our customers from cyber threats. Users currently utilizing Office 365 connectors should transition to Power Automate to maintain smooth operation of their services.

We will gradually roll out this change in waves:

  • Wave 1 – effective August 15th, 2024: All new Connector creation will be blocked within all clouds
  • Wave 2 – effective October 1st, 2024: All connectors within all clouds will stop working

What’s the new experience within Microsoft Teams?

The Workflows app in Microsoft Teams has received dozens of updates in the last year to more deeply integrate into your stream of work. For newcomers who aren’t yet familiar, workflows save time, reduce mistakes, and boost productivity across various activities. They facilitate approval processes, project updates, and any routine operation, offering notifications on task changes, quick actions from chats, improved meeting management, and the ability to swiftly customize workflows.

Learn more about the Workflows app here.

Image 02

How do I transition from Office 365 connectors to Workflows?

If you are currently using Office 365 connectors in Microsoft Teams, you will need to migrate your existing Office connectors to Workflows before the relevant retirement dates above. To do so, follow these steps:

1. Go to the Workflows app in Teams and click on the “Create” tab. Choose the type of workflow you want from a template, or from scratch:

  1. If you choose to create from a template, you can browse or search for workflow templates that match your Office connectors’ functionality. For example, if you use the Trello connector, you can find templates for creating cards, updating lists, or posting messages based on Trello actions.
  2. If you choose to create from scratch, you can select the trigger and action for your workflow. You can use many of the same services that you used with your Office 365 connectors or explore new ones from the hundreds of Office connectors available in Power Automate. Once you have created your workflow, you will name it and add a description. You can also test it, share it, or edit it anytime from the “My flows” tab.

2. Open the Workflows app within the chat or channel by right-clicking on the conversation, or by clicking on More options (…). From there you can also browse a list of templates that are specific to the chat or channel context that match your current Office connectors’ functionality.

Image 03

    1. For example, if you use the Webhook or RSS connector, you can find similar workflow templates within this list.
    2. Explore these popular templates:

To learn more about creating workflows in Teams, check out these support articles:

Follow us on X (Twitter) / @Microsoft365Dev and subscribe to our YouTube channel to stay up to date on the latest developer news and announcements.

Category
Microsoft Teams
Topics
Office connectors

Author

Connor Rodewald
Connor Rodewald
Senior Product Manager
All comments
Single comment
  • Emma Degerman

    Honestly this comes across as a greedy cash grab, forcing us to replace integrations that we have been relying on for years as part of our M365 licenses with ones requiring yet another premium license. Can we at least assume that incoming emails will stay the same, given that it has its own setup from the channel menu (even though it is called Email Connector in the activity history)?

    Making such a major change with a short timeline over the summer months shows a complete lack of understanding of European customers.

    And FYI, the template links all point to your...

    Read more
    • Connor RodewaldMicrosoft employee Author

      We understand and appreciate the feedback that you all have shared with us regarding the timeline provided for the migration from Office 365 connectors! Please see the recent update at the top of the blog post about the extension for the retirement timeline.

      • MagicHappenZ

        You clearly do not! You simply took the part of the feedback that is the least change on your plans, the unrealistic timeline that some people mentioned. However, you just keep ignoring the not working suggested usage of Power Automate and the worsening of security, flexibility and scalability. See feedback here: https://feedbackportal.microsoft.com/feedback/idea/80ed6877-b642-ef11-b4ad-000d3a7aba8b. If Microsoft has a slight idea of customer focus you would simply stop this mess and apologize for the ignorance.

    • Alexander (from ESP) 
      a complete lack of understanding of European customers.

      Ironically, it sounds like this may be a downstream consequence of the EU antitrust case against Microsoft’s Teams-365 bundling.

      • DM

        It’s more like the opposite, because now you need even more M$ products.

    • El Johnson

      …not just European markets; human markets. And instructions are, as usual, unintelligible.

Read next