Jira Server Microsoft Teams Connector EOL

[#1]

Connectors in Microsoft Teams deliver content and service updates directly from third-party services into a Teams channel.
The purpose of Jira Server Connector in Microsoft Teams is to send updates about Jira Server/Jira Data Center issues directly to Teams channel as detailed card. 

We are sad to inform you that the Jira Server Connector will stop working by December 31, 2024. Additionally, you will not be able to create new connectors after August 15th, 2024. This change is due to the deprecation of all all Microsoft365 connectors (please find more information here).

What is next?

We understand that the Jira Server Connector is very important for you to receive updates on your tickets in Teams. Therefore, we propose an alternative option based on Microsoft Teams Workflows.

Please check the guide we have prepared for you to get notifications in Channels with just a few simple steps.

Additionally, our team is considering the option to extend the functionality of our Jira Server/Jira DC app to receive issue notifications from within the app.

Cheers,
Product Integrations Team

[Sean Lively]

@Volodymyr Batrukh The new Jira Cloud connector for Teams doesn't display webhooks from Transitions, something the Jira Server connector did well. Any chance someone can fix that?

[Volodymyr Batrukh]

Hi @Sean Lively 

Jira Cloud Connector was developed and supported by Microsoft. So unfortunately we are not able to change functionality of existing connector. 

Please note that all connectors will be retired till the end of January and you will not be able to use any of the connectors after that date:

Regards,
Volodymyr B.

[Sean Lively]

@Volodymyr Batrukh Thanks for the reply- Microsoft has pushed back the retirement of O365 connectors to the end of 2025, and has given users to the end of January to update the webhook URLs to the new format.

The new Workflows option doesn't work for us, because we want notifications in private channels. Microsoft has only committed to an update by March 30th on this issue: https://devblogs.microsoft.com/microsoft365dev/retirement-of-office-365-connectors-within-microsoft-teams/ so I don't expect that to be resolved any time soon.