Businesses collect, store, and analyze a constantly rising quantity of data, and so, tools for helping them discover, catalog, track and manage how that data is shared are also growing in importance. With Azure Purview, Microsoft has launched a new data governance service into public preview that combines these capabilities in a fresh data catalog including discovery and data governance features.
Azure Purview is a unified data governance solution that allows you to manage as well as govern your on-premises, multi-cloud, and software-as-a-service (SaaS) data. It creates a detailed and proper map of your data and also performs the classification of end-to-end lineage of your data. It enables data consumers to find trustworthy data and is created on Apache Atlas which is an open-source project for metadata management and governance for data assets.
In my blog, I am going to shed some light on the key features and functionality of this solution, and also take you through the process of setting it up.
For starters, take a look at some characteristics of Azure Purview I have outlined below:
Now that you are acquainted with the nature of this solution, let’s dive into its major components!
Here are the three components that describe the functionality of Azure Purview:
1. Data Map:
The Azure Purview Data Map provides you the facility to register your data source which you want to scan under the Root collection you selected. It makes your data informative by mapping your data assets and their relationships across your data estate. Data map automatically scan your data, classifies your data and also lineage your data.
2. Data Catalog:
The Data Catalog is a search bar of your purview account in which you can search assets of your registered sources and get detailed information about your searched asset. You can also view a business glossary, lineage visualization, catalog insights as well as sensitive data identification insights.
3. Data Insights:
With the help of Data Insights, you can watch the data briefly, understand what data is actively scanned, where sensitive data is, and how it moves.
Before I reveal the problem statement and solution approach that I have focused my blog on, I’d like to give you an idea about certain concepts related to Azure Purview.
A collection is a group of related data sources. It is a root of structural hierarchy of Azure Purview. A collection can have zero or more sources. Ex. A company name can be a collection and the department of that company like IT, HR can be its sources.
A source is the next object in the hierarchy of Azure Purview data mapping. Basically, the source means from where your data is coming. (Ex. Azure Data Lake Storage, Azure SQL Database, Storage account etc.)
A Source can have:
An asset is an instance of an asset type. It can be found in the Azure Purview window by using the Azure Purview search bar after the metadata has been indexed. Ex. If a source of Azure SQL Database has three tables, then generally there are three assets.
An asset has one source and can have:
Scanning is a process wherein the catalog links directly to a data source on a schedule defined by the user. Azure Purview scans your data on the basis of three levels – Basic, Schema and Classification. On the basic level, it scans file name, file size, fully qualified name, etc. and on the schema level, it scans database tables and structured file types, etc. In classification, a scan is based on classification rules.
A scan has:
The purpose of this blog is to maintain the data catalog, lineage and data governance of the data platform which has various components such as Sources, ETL process, Data warehouse and Reporting layers.
Now, read on to discover the process of setting up Azure Purview.
Step 1: Open a window and register the source
This is the first window when we open the account and go to the root collection window.
In this window, we must register our source which we want to scan. For that, follow these steps:
Step 2: Click the Register icon to register the source
Here, select your source which you want to scan. Enter your source details and then it will add your source under the root collection. (Shown in the next step)
Step 3: It will add under Root collection
Step 4: Create a scan for your source
Now create a scan for your source to scan it and get various kinds of details about your source assets like its schema, its lineage, classifications of your columns, etc.
Step 5: Review your scan
Now just review your scan and check all the information in the ‘Review your Scan’ window. Then click on the ‘Save and Run’ option and the scanning of your source will start.
Step 6: Add your Data factories or other things to get Lineage view
Now select your data engineering service which you used to transform your data (I used Data Factory) from the management icon on the bottom left side and select the ‘Data Factory’ option under Lineage connection.
Step 7: See your scanning details
To check the status of your scanning (whether it is completed or in progress), follow these steps:
Step 8: Search for your Assets using a Data Catalog
The ‘Data Catalog’ is a search bar of your Purview account in which you can search for the assets of your registered sources and get detailed information about your searched asset.
It also contains three important sections:
1. Browse Assets:
Here you can browse your assets on the basis of your source type or on the basis of your collection.
2. Manage Glossary:
You can manage your glossaries in this section. You can create or add glossaries as well.
3. Knowledge Center:
The knowledge center helps you with learning materials and tutorials.
Step 9: Set a connection to Power BI from Azure Purview by creating a security group in the Azure Active Directory
If you want to register Power BI under the root collection and scan it, then follow these steps:
Step 10: Power BI setting for Azure Purview
Step 11: See lineage of your data
And there you have it! This is how Azure Purview helps you to get the fundamental structural metadata and lineage of the registered sources. With its help, you can get a great bird’s eye view of your data flow and data transformation from source end to destination end!
Feel free to write to us at Nitor Infotech with any comments and suggestions you may have. Also, while navigating the Azure universe, you will find this blog useful if you would like to learn how you can deploy an existing Azure Data Factory branch on a new ADF environment via Git configuration.
Subscribe to our monthly newsletter!