Deprecation Notice for Classic Azure Blob Storage as a Forensic Destination

Deprecation Notice for Classic Azure Blob Storage as a Forensic Destination

This deprecation notice is for the customers who are using Classic Azure Blob Storage as a forensic destination. If you have any queries, contact your Netskope customer success manager or support@netskope.com.

Summary of Change

Starting release 117, Netskope will no longer support Classic Azure Blob Storage as a forensic destination. Due to this change, new customers cannot use Classic Azure Blob Storage as a forensic destination. Existing customers can continue to use this feature as expected, until further notice.   

Fine Prints

Netskope no longer supports the Forensic feature, when you create a new Microsoft Azure instance from Settings > Configure App Access > Classic > IaaS > Microsoft Azure. Here are the fine prints:

  • For existing customers who are using the classic Microsoft Azure Blob storage as a forensic destination, the feature will continue to work as expected.

  • For new customers, the classic instance setup UI for Microsoft Azure will no longer have the forensic checkbox. New forensic Microsoft Azure instances cannot be enabled.

  • Existing customers using classic Microsoft Azure Blob storage as a forensic destination, can disable the forensic checkbox from the UI. However, once disabled, you cannot re-enable it.

  • Existing customers who have not enabled the forensic checkbox cannot enable it going forward.

General Recommendation

As an alternative, Netskope recommends creating a new Microsoft Azure instance using the Next Gen workflow. To learn more: Set up Microsoft Azure Blob Storage Forensic Instance.

Share this Doc

Deprecation Notice for Classic Azure Blob Storage as a Forensic Destination

Or copy link

In this topic ...