Retirement of Office 365 connectors within Microsoft Teams

Connor Rodewald

Trent Hazy

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.


Leave a comment

  • Junge, Andreas 25

    Currently we are using the “Incoming webhook” connector for notifcations about pipeline execution results from our On-Premise Azure DevOps Server. Using the explanations and examples in this post, I have not been able to create a working workflow. The messages generated by the Azure DevOps Server don’t seem to be compatible with the format expected by the workflow (or I don’t understand what I have to do…)

    And even if I knew how to do it, I don’t really have time to create dozens of workflows and change the URL in hundreds of service hook substricptions just to get an already existing functionality.

  • Konrad Haenel 5

    Hilarious: I went to the trouble of setting up a Workflow for my Azure DevOps Notifications – as recommended – but now I can’t unconnect the old connector. And no, I can’t switch to “old” Teams to do it. Guess I’ll have to wait till October to not get twice the notifications every time.

    • Trent HazyMicrosoft employee 0

      Office 365 Connectors can be found under “manage channel” in New Teams! You should be able to turn off the connector from there if you are the owner.

      • David Grain 4

        But only if you are the OWNER of the team (not the connector). Previously, you did not need to be the owner of the team to create a connector. Therefore only option is to revert to ‘old’ teams, delete, then switch back. This ‘change’ has been mismanaged from start to finish.

  • Sven GES. Gehring 17

    Unless I’m misunderstanding, this means we can pay an additional $20’000/y and spend dozens of hours re-deploying webhook configurations and payload formattings only to get half the functionality because it cannot post to private channels and we don’t need the Power Automate subscription for anything else? Excuse me what?!

  • Mark Emerson 4

    We started to receive the deprecation notifications in our teams channels today.
    How can we determine if we are using connectors and not workflows?
    Do we have to reconfigure every channel to use workflows?
    Will our production alerts stop if we dont update to use workflows?

    Note: workflows is the only option in the teams channel (more) menu – nothing regarding connectors.

    • Trent HazyMicrosoft employee 0

      If the deprecation notice is appended to the message, that is an Office connector posting (and won’t work beyond Oct 1).
      To find connectors from the channel menu go to “Manage channel” > Edit connectors

      • David Adams 1

        Why aren’t you responding to questions about the severe timeline, the need to upgrade to a premium level, the poor documentation, the lack of migration tools, and the missing functionality?

      • Kristian Holst 2

        Hello @Trent and @Connor
        (I replied in this thread because you actually wrote a comment here, Trent)

        Based on the feedback in these comments, I hope that you will reconsider the decision to retire Office 365 connectors in Teams. This is a major inconvenience for many of us, and I believe what you are reading here is just the tip of the iceberg in terms of how many are negatively affected by this change. If you cannot influence this decision, I hope that you take this up with your superiors.

      • Sven Indiesson 0

        But why, why implement the new way of doing this Trent, in such a bad way? I can’t get rid of the footer, and the webhook will always post as my user.

        Not to mention I have about 70 webhooks to create – and you don’t even provide such a basic thing as a guide. And – the new webhook doesn’t accept the same message that I send to the existing.

        We’re talking about basic functionality that you will find in all of your rivals applications – a frickin incoming webhook. Just leave it, it works perfectly fine the way it is. Looking at all the replies, its pretty clear that I’m far from the only one. Please, listen to your customer base.

  • Tonny Roger Holm 25

    Thank you for impacting our summer plans :-\

    Incoming Webhooks has been a crucial and efficient function in Microsoft Teams, extensively used in our company for various integrations, including custom ones. It has allowed us to move away from alternatives like Slack. I’m concerned this change will force us to reconsider such solutions, leading to increased complexity in knowledge, responsibility, billing, and licensing with Power Platform.

    I see no benefits to this decision and fear it could undermine Microsoft’s reliability as a vendor both now and in the future.

    Tonny Roger Holm
    Eika Gruppen

    • Steven Slezak 0

      Honest question – You moved away from slack for this? Why?

      • Tonny Roger Holm 0

        Because it was simple with the Webhook in Teams (its a while ago). Now on the other hand…..

  • Alexey “ALERT” Rubasheff 6

    I have been using Python 2 module ‘pymsteams’, that, as I tested, is not compatible with the new Power Automate system. How can I use the MSTeams webhooks using Python 2 after PowerAutomate takes over the Connectors? Thank you.

    • Josh S 1

      I’m in the same, sinking boat

  • Matt Rydzik 12

    What is the replacement for sending incoming webhooks to private channels? Power automate is not able to do that.

  • Олег 16

    let’s remove the only working well feature from Teams – what a stupid decision

  • Nicolas GERARD 12

    Everyone here seems happy Microsoft, good work again from you, keep it up (I hate you with all my soul)

  • Kristian Holst 18

    What are you doing? This is a major change for us, coming in the middle of the summer vacation. You should show more respect and not make such changes during the vacation when most people are away from work. Very disappointing!

Feedback usabilla icon