Skip to main content

Hello everyone,

Some of you have already seen the information and have already passed it on to us (thanks again for your vigilance and your feedback). Microsoft made this announcement at the beginning of July:

Starting August 15th, 2024 we will be removing 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.


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

 

How will it work on the Centreon side?


We have started to address this change and hope to quickly have an updated notification script in beta for users who would be interested in helping us validate it. The Centreon release of the Teams connector update is currently scheduled for the August 2024 release which will take place before August 15 and will allow you to make the transition before Microsoft retires O365 connectors.


If you have already developed notifications through Power Automate workflows, please reach out to me through a private message and we'll see how you could contribute!


Source Github issue for testing interest

Hi @ldubrunfaut,

I understand that the development of the new Teams workflow is complete.

Would it be possible to create a tutorial similar to the previous one for the webhook? It would be greatly appreciated.

Thank you!


Hello :)

The Teams connector was updated in the August release. The information you need to know should be on this doc page. If you have any feedback, please let us know.

Best regards.


Hello,

It seem teams-workflow  replace teams-webhook in the script centreon_notification_teams.pl ?

If yes, the clapi part of https://docs.centreon.com/docs/23.10/alerts-notifications/notif-config-for-teams/ should be updated.

Regards


Hello :)

Thanks for your feedback, the fix in this section has been applied and published this morning.

Best regards.


Reply