Are the Azure DevOps extension for Slack affected by changing the slack workspace url?

0
votes

In the company, we will change the slack workspace URL from https://oldname.slack.com to https://newname.slack.com. We have a lot of connections from Azure DevOps online service to Slack using two approaches. Older links via service hooks in Azure Devops, new links are via slack applications Azure Repos and Azure Pipelines.

Thanks to Slack support, I know that Slack hooks are not affected if they were created after 2015. Which is the way Azure Devops uses for Service Hooks to Slack.

But I don't know if the Azure Repos and Azure Pipelines configurations will not be affected. E.g. Azure Repos is set up in Slack via /azrepos subscribe [dev.azure.com/projecturl] and this step automatically set the address to azdevchatops.azure.com in Azure Devops Service hooks settings. If Azure Repos is working somewhere with a Slack workspace URL, so I need to set up Azure Repos and Azure Pipelines in Slack again after changing the slack workspace url, that's what I don't know and what I'm asking.

1
azure-devopsazure-pipelinesslackazure-devops-extensionsazure-repos
Does this answer your question? Do I need to reconfigure the Slack Apps for Azure Repos/Pipelines after changing the Azure DevOps workspace url? – Krzysztof Madej
Please close one of the question you made. It looks like you did double click :) – Krzysztof Madej
No, we need to make change on both side (change url on Slack and Azure DevOps). One question is about changes to made when we change slack url, one question is about changes to made when Azure DevOps url will change. Theare are different scopes. These URL changes will happen in different times, so questions are different and answers will be too. – adpro

1 Answers

0
votes

We do not need to reconfigure notification in the slack workspace.

As test result, I create notifications via /azpipelines subscribe [dev.azure.com/projecturl] to check the pipeline status, I can successfully receive the notification in the slack.

Then I changed the workspace name and workspace URL to the new ones, and re-run the pipeline. I can still receive notifications, you could check the pic below.

enter image description here