Migrate Slack Enterprise from Classic to Next Generation API Data Protection
Migrate Slack Enterprise from Classic to Next Generation API Data Protection
The article provides guidance for customers currently using the Classic API Data Protection for Slack Enterprise. It outlines a clear process for migrating to the enhanced Next Generation API Data Protection, which offers improved performance and functionality. The migration involves key steps, including preparation, configuration updates, and verification, ensuring a smooth transition to the more advanced platform.
Migration Steps
Here are the broad steps to migrate your classic Slack Enterprise instance to Next Generation.
-
Set up the new Slack Enterprise instance on the Next Generation platform.
-
Configure the policies and profiles but do not active them yet.
-
Disable the classic Slack Enterprise instance to prevent further upstream API calls without removing the instance. This allows you to continue to view relevant alerts and quarantine files.
In order to disable the classic Slack Enterprise instance, you should to delete all the instance-related policies & profiles, and then edit the instance to uncheck the CASB API checkbox.
The CASB API checkbox may remain disabled. To enable it, you should first remove the policies and profiles related to the instance. -
Activate the policies and profiles you created in step 2.
-
Ensure that the Next Generation Slack Enterprise instance is functioning correctly. Then, begin preparation to remove the classic Slack Enterprise instance.
Running classic and Next Generation instances simultaneously may lead to unexpected behavior, especially if both platforms have legal hold or quarantine policies in place. Additionally, this dual operation poses the risk of exceeding upstream API rate limits, which can result in throttling and disrupt all protection mechanisms. Therefore, Netskope strongly advises against running classic and Next Generation instances at the same time to avoid these potential issues.