New Blog Post | Public Preview: Separation of scan levels for Azure SQL Database

Scanning is a key function that captures metadata from data sources and brings it to Microsoft Purview. In Microsoft Purview Data Map terminology, there are three different levels of scanning based on the metadata scope and functionalities:

• L1 scan: Extracts basic information and metadata like file name, size, and fully qualified name
• L2 scan: Extracts schema for structured file types and database tables
• L3 scan: Extracts schema where applicable and subjects the sampled file to the system and custom classification rules

So far the different scan levels are integral parts of the scanning process that can’t be further separated, for example, users can’t disable the data sampling and classification on data sources that already support classification in Microsoft Purview. To support more usage scenarios and increase flexibility, we will start to add the support of separation of scan levels for different data sources and we are pleased to announce the public preview of this feature for scanning Azure SQL Database and Snowflake. Below we will use scanning Azure SQL Database as an example to introduce this new feature and show some sample scenarios.

 

Read more here: Public Preview: Separation of scan levels for Azure SQL Database and Snowflake in Microsoft Purview - Microsoft Community Hub