Share via

The Retirement of Office 365 Connectors.

green 76 Reputation points
2026-04-06T05:08:33.4433333+00:00

The article below states that updates on features currently under development for the Flow bot would be announced in late February.

However, despite this being a feature that many users are eagerly awaiting, no updates have been shared yet. Could you clarify why no information has been provided so far?

This is not a hobby use case for us. We expect sufficient preparation time and clear communication.

Please postpone the retirement of Office 365 Connectors until the alternative functionality is fully implemented and available.

https://devblogs.microsoft.com/microsoft365dev/retirement-of-office-365-connectors-within-microsoft-teams/

Microsoft Teams | Development
Microsoft Teams | Development

Building, integrating, or customizing apps and workflows within Microsoft Teams using developer tools and APIs


1 answer

Sort by: Most helpful
  1. Steven-N 23,700 Reputation points Microsoft External Staff Moderator
    2026-04-06T05:55:33.7666667+00:00

    Dear green

    Thank you for reaching out to Microsoft Q&A forum and apologize for the inconvenience

    First of all, I genuinely understand how disruptive and stressful this is when your organization relies on these notifications for real operational work. I’m sorry for the uncertainty and the planning burden this creates. However, as a forum moderator, I don’t have the ability to change Microsoft’s product roadmap, implementation pace, or retirement schedule, and I can’t request exceptions on behalf of customers.

    As of the latest official update, Microsoft has acknowledged delays and extended the Office 365 Connectors retirement deadline to April 30, 2026 to provide additional migration time.

    Moreover, it also confirmed that MessageCard payload support is now available in Workflows (with limitations) and that the Workflows bot (Flow bot) can post in shared channels, while Flow bot posting to private channels remains under development, so you can consider trying this as a workaround

    Link reference: https://learn.microsoft.com/en-us/microsoftteams/platform/webhooks-and-connectors/how-to/add-incoming-webhook?tabs=newteams%2Cdotnet

    Thank you for your understand and wish you have a nice day.


    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread. 


Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.