Hello -
If Purview is not classifying Social Security Numbers (SSNs) in your Snowflake data source, there could be several reasons for this. Here are some factors to consider and steps you can take to troubleshoot the issue:
Scan rule set configuration: Ensure that the scan rule set applied during the scanning process includes the "Social Security Number" classification or a custom classification designed to match SSN patterns.
Data pattern recognition: Verify that the actual data stored in the Snowflake columns contains valid SSN patterns. Purview uses pattern matching to classify data, so if the data deviates from expected patterns, it may not be classified correctly.
Column naming convention: Make sure that the column names containing SSNs are consistent with naming conventions typically associated with Social Security Numbers. Although Purview primarily relies on data patterns, the naming of columns can help improve classification accuracy.
Rescan the data source: After adjusting any configurations or correcting any discrepancies, you might need to rescan the Snowflake data source to see if the classifications are now applied correctly.
Adjust classification rules: If necessary, you can create custom classification rules tailored to your specific data patterns or requirements.
Keep in mind that automatic classification can be influenced by multiple factors, including data quality, scan rule set configuration, and data source characteristics. Double-checking these aspects will help ensure accurate classification within your Snowflake data source.
Also, the scan agents could be sampling rows of your dummy data, so it is better to ensure to insert quite a few number of records in your database before your test run.
If you still have issues with SSN classification after considering these factors, I would recommend you to open a support ticket with Microsoft as this may need a deeper investigation.