Bitbucket -> Microsoft Teams notifications - Connector Retirement

[Alan Cooper]

Hi,

Microsoft are retiring the Teams webhook connector, which was a nice, simple and reliable way to post various notifications into teams channels. 

Retirement of Office 365 connectors within Microsoft Teams

We use the Bitbucket integration with our Bitbucket & Bitbucket Pipelines extensively (so there's a easy to see trail of PRs raised, deployments going out etc.

Messages generated by the integration are being tagged with the retirement message - I appreciate everyone's been caught out by this unexpected and rather rushed development - does Atlassian have a plan for migrating to the Teams / Power Automate Workflow method proposed by Microsoft?

[Move Work Forward]

Hi @Tomáš Kuba 

We are making the changing for the app as I write.

In the next couple of days the app will be working with the Workflows URLs.

I will update you here when it is done. Pls use the old Incoming Webhook URLs for a couple of days more, sorry.

Regards,
Leo

[tgurukunta]

Thanks for the update. Do you also release the server version along with DC version. We are still in server version and have plan to migrate to cloud by the end of the year. So in the meanwhile we would like to have that compatible version with server too.

[Move Work Forward]

Hi everybody,

We have released the support for Microsoft Teams Workflows app.

Here is a quick guide how to get the Post messages URL.

Please let us know if you got any feedback.

Thanks,
Leo

[Move Work Forward]

Hi,

yes, we released the cloud apps yesterdays and this week we are releasing all DC apps that work with Microsoft Teams to support Workflows apps.

thanks,

Leo 

[tgurukunta]

@Move Work Forward Are you also planning on releasing a new version for bitbucket server  along with the cloud.

[Tomáš Kuba]

Hi, we have the same issue. It started on Monday July 7.

Plugin is https://marketplace.atlassian.com/apps/1220054/microsoft-teams-connector-for-bitbucket?hosting=datacenter&tab=overview

Microsoft decided it needs to be converted from "Connector" to "Workflow".

It looks like it is the same webhook, but app won't allow me to input new URL as it no longer has "IncomingWebhook" string in URL. New format is following:

https://prod-177.westeurope.logic.azure.com:443/workflows/[redacted]/triggers/manual/paths/invoke?api-version=2016-06-01&sp=%2Ftriggers%2Fmanual%2Frun&sv=1.0&sig=[redacted]

[Move Work Forward]

Hi,

Which app do you use for Microsoft Teams integration with Bitbucket?

Thanks,
Leo