| sidebar | sidebar |
|---|---|
| permalink | reference-limitations.html |
| keywords | limitations, data sense, classification, scan shares |
| summary | Known limitations identify functions that are not supported by this release of the product or that do not interoperate correctly with it. Review these limitations carefully. |
Known limitations identify functions that are not supported or do not interoperate correctly in this release. Review these limitations carefully.
The December 2023 (version 1.26.6) release removed the following options:
-
The option to activate audit log collection has been disabled.
-
During the Directories investigation, the option to calculate the number of personally identifiable information (PII) data by Directories is not available.
-
The option to integrate data using Azure Information Protection (AIP) labels has been disabled.
The following limitations occur with Data Classification scans.
If you have multiple file shares under a single volume, Data Classification scans the share with the highest hierarchy. For example, if you have shares like the following:
-
/A
-
/A/B
-
/C
-
/D/E
In this configuration, only the data in /A is scanned. The data in /C and /D is not scanned.
There is a workaround to make sure you are scanning data from all the shares in your volume. Follow these steps:
-
In the system, add the volume to be scanned.
-
After Data Classification has completed scanning the volume, go to the Data Investigation page and create a filter to see which share is being scanned:
Filter the data by "system Name" and "Directory Type = Share" to see which share is being scanned.
-
Get the complete list of shares that exist in the volume so you can see which shares are not being scanned.
-
Add the remaining shares to a share group.
Add all the shares individually, for example:
/C /D
-
Perform these steps for each volume in the system that has multiple shares.