Purview Scans are creating Schema Classifications but not Data Classifications

Jarrod Henningsen 0

Full scans have been run on an ADLS Gen2 storage account containing an example csv file with PII data at both the Auto and Level3 ScanLevel. Schema Classifications were found for PII related rules such as physical address, full name, etc, but no classifications were created. Scan rule set AdlsGen2 (System) was used for the scan. Why are Data Classifications not being generated.

phemanth 14,220 Reputation points Microsoft Vendor

2025-02-27T20:09:11.9366667+00:00
@Jarrod Henningsen

Welcome to the Microsoft Q&A and thank you for posting your questions here.

When using Azure Purview to scan data in an ADLS Gen2 storage account, it's important to understand the distinction between schema classifications and data classifications. Schema classifications identify the structure of the data (like the types of fields in a CSV), while data classifications focus on the actual content of the data.

Here are troubleshooting steps; please check and confirm us whether the issue gets resolved:

Ensure that the scan rule set you are using (AdlsGen2 (System)) is configured to detect and classify the specific types of data you are expecting. Sometimes, custom rule sets might be needed.

Verify that the classification rules for data classifications are correctly defined and enabled. Schema classifications might be working because they are predefined, but data classifications might need additional configuration.

Check if the data sensitivity labels are properly applied and recognized by the system. Sometimes, the absence of these labels can prevent data classifications from being generated.

Ensure that the scanning service has the necessary permissions to access and classify the data within the ADLS Gen2 storage account.

Although you mentioned using both Auto and Level3 ScanLevel, double-check if these levels are sufficient for the depth of classification you require. Sometimes, a higher scan level might be necessary for more detailed classifications.

Review the scan logs and reports for any errors or warnings that might indicate why data classifications are not being generated. These logs can provide insights into what might be going wrong.

I hope this information helps. Please do let us know if you have any further queries.

Kindly consider upvoting the comment if the information provided is helpful. This can assist other community members in resolving similar issues.
Jarrod Henningsen 0 Reputation points

2025-02-27T20:38:40.57+00:00

This is not helpful and it's actually a bit insulting. It's just the response from an LLM which has been copied and pasted.

What I want to know is why the default scan rule set (AdlsGen2 (System)) is not creating a classification even though Schema Classifications (All Full Names, Credit Card Number, Email Address, IP Address) have been found and should be triggering a classification since those rules are also in the scan rule set.

Share via

Purview Scans are creating Schema Classifications but not Data Classifications

Your answer