Slack Integration Issue with Bitbucket Cloud After IP Allowlisting

Summary

Slack integration with Bitbucket Cloud may cease to function after enabling IP Allowlisting, an Access Control Feature, on the workspace. This issue arises when attempting specific actions in Slack related to Bitbucket Cloud.

Diagnosis

The problem manifests after enabling IP Allowlisting on a workspace. While Slack can still receive certain notifications from Bitbucket Cloud, interactions such as commenting on pull requests, approving pull requests, and creating notifications via direct message may fail. 

Cause

The root cause is the absence of Atlassian IP ranges in the workspace's allowlist, which prevents the connection from Slack to Bitbucket Cloud.

Solution

To resolve this issue, follow these steps:

1. Allowlist all the IPs mentioned on the official IP ranges page. As Bitbucket internal system is regularly updated, on each update, it is likely to get a new internet address (IP) from a pool of many possible addresses. If you've only allowed its current address to communicate with your system, you might face issues when the address changes after an update. To avoid this, it's a good idea to allow all potential addresses it might use. Here is a list of all the addresses you should allow: 

   • https://ip-ranges.atlassian.com/

2. The workspace administrator can perform this action by referring to the steps outlined in the Access Control documentation.

   • The IPs can be added in the Workspace settings > access control > add or remove IP addresses.