Forum Discussion
New Blog Post | March ahead with Azure Purview: Setting up scans
March ahead with Azure Purview: Setting up scans - Microsoft Tech Community
Welcome to the "March Ahead with Azure Purview" blog series that helps you to maximize your Azure Purview trial/pilot/PoC with best practices, tips and tricks from product experts. In the previous blog post, we covered setting up the appropriate control plane and data plane roles to manage Azure Purview. In this post, we’ll roll up the sleeves and walk through the process of scanning data.
1 Reply
In your post you distinguished between meta-data scanning vs data scanning according to classification rules - e.g. PowerBI data set is currently only metadata scanning.
Due to our regulatory requirements to retain data in Australia regions only, including during scanning, and the fact that Purview is currently only available outside Australia, we are limited to storing only metadata in Purview (not actual data). Does Purview's architecture suit this requirement ? Does this mean:
A. We can scan only PowerBI data sets (meta-data scanning only) ?
B. We can use our Microsoft Integration Runtime in Australia to perform scans and the metadata results can be uploaded to Purview outside Australia ?
C. We can scan our Azure resources e.g. Azure SQL database in Australia East and Purview will automatically use the AustraliaEast scanners (https://docs.microsoft.com/en-us/azure/purview/sources-and-scans#purview-scanner-regions ) ?
As scanning for classification rules involves reading and parsing the actual data, we need to perfom this in AustraliaEast and retain all copies of data in AustraliaEast.
Secondly, Does Purview ever show examples of data, alongside the metadata?
