module01.md

Module 01 - Create an Azure Purview Account

< Previous Module - Home - Next Module >

📢 Introduction

Azure Purview is a unified data governance solution that helps you manage and govern your data at large. It combines many different services for scanning, collecting, organizing and sharing metadata. It uses a catalogue for discoverability, but also offers other features, such as automatic classification, sharing, access management and so on.

When planning your Azure Purview deployment, you first need to provision an Azure Purview account. Next, you need to define your collections for managing and grouping data assets together. A collection is a logical container in which your metadata, such as data sources, will be managed. When creating collections and placing them in a hierarchy, you need to make different considerations, such as your security requirements, governance structure and democratization needs. For example, a more centralized-alined style of data management leads to different collection structure then a more domain-oriented style of data management. Depending on your needs, different topologies can be used for managing your data. Best practices for this can be found on this website.

🤔 Prerequisites

• An Azure account with an active subscription.
• Your must have permissions to create resources in your Azure subscription.
• Your subscription must have the following resource providers registered: Microsoft.Purview, Microsoft.Storage, and Microsoft.EventHub. Instructions on how to register a resource provider via the Azure Portal can be found here.

🎯 Objectives

• Create an Azure Purview account using the Azure portal.
• Provide additional users access to Azure Purview's data plane.

📑 Table of Contents

#	Section	Role
1	Create an Azure Purview Account	Azure Administrator
2	Grant Access to Azure Purview's Data Plane	Collection Administrator

↥ back to top

1. Create an Azure Purview Account

1. Sign in to the Azure portal, navigate to the Home screen, click Create a resource.

   

2. Search the Marketplace for "Azure Purview" and click Create.

   

3. Provide the necessary inputs on the Basics tab.

   Note: The table below provides example values for illustrative purposes only, ensure to specify values that make sense for your deployment. If you have pre-deployed other Azure resources using the lab template, they would have been created with a randomId, it is recommended to use the same randomId for the Azure Purview account name as per the example below.

   Parameter	Example Value
   Subscription	YOUR_AZURE_SUBSCRIPTION
   Resource group	pvlab-rg
   Purview account name	pvlab-{randomId}-pv
   Location	YOUR_LOCATION
   Managed Resource Group Name	pvlab-rg-managed

   Note: The

   

   💡 Did you know?

   Capacity Units determine the size of the platform and is a provisioned (always on) set of resources that is needed to keep the Azure Purview platform up and running. 1 Capacity Unit is able to support approximately 25 data map operations per second and includes up to 10GB of metadata storage about data assets.

   Capacity Units are required regardless of whether you plan to invoke the Azure Purview API endpoints directly (i.e. ISV scenario) or indirectly via Purview Studio (GUI).

   Note: With the introduction of the Elastic Data Map, you no longer need to specify how many Capacity Units that you need. Azure Purview will scale capacity elastically based on the request load.

   vCore Hours on the other hand, is the unit of measure for serverless compute that is needed to run a scan. You only pay per vCore Hour of scanning that you consume (rounded up to the nearest minute).

   For more information, check out the Azure Purview Pricing page.

4. On the Networking tab, select All networks.

   

5. On the Review + Create tab, once the message in the ribbon returns "Validation passed", verify your selections and click Create.

   

6. Wait several minutes while your deployment is in progress. Once complete, click Go to resource.

   

↥ back to top

2. Grant Access to Azure Purview's Data Plane

By default, the identity used to create the Azure Purview account resource will have full access to Purview Studio. The following instructions detail how to provide access to additional users within your Azure Active Directory.

1. Navigate to your Azure Purview account and click Open within the Open Purview Studio tile.

   

2. On the left-hand side, navigate to Data map.

   

3. Select Collections.

   

4. Select Role assignments.

   

5. On the right-hand side of Data curators, click the Add icon.

   

6. Search for another user within your Azure Active Directory, select their account, click OK.

   

   💡 Did you know?

   Azure Purview has a set of predefined data plane roles that can be used to control who can access what.

   For more information, check out Access control in Azure Purview.

   Role	Collections	Catalog	Sources/Scans	Description
   Collection Admin	Read/Write			Manage collections and role assignments.
   Data Reader		Read		Access to catalog (read only).
   Data Curator		Read/Write		Access to catalog (read & write).
   Data Source Admin			Read/Write	Manage data sources and data scans.

↥ back to top

🎓 Knowledge Check

http://aka.ms/purviewlab/q01

1. Which of the following Azure Purview pricing meters is fluid, with consumption varying based on usage?

   A ) Capacity Units
   B ) vCore Hours
   C ) Neither

2. Which of the following Azure Purview pricing meters is always on, with consumption based on quantity provisioned?

   A ) Capacity Units
   B ) vCore Hours
   C ) Neither

3. Which Azure Purview module provides the base functionality (i.e. source registration, automated scanning and classification, data discovery)?

   A ) C0
   B ) C1
   C ) D0

4. Which predefined Azure Purview role provides access to manage data sources?

   A ) Purview Data Reader
   B ) Purview Data Curator
   C ) Purview Data Source Administrator

↥ back to top

🎉 Summary

This module provided an overview of how to provision an Azure Purview account using the Azure Portal and how to grant the appropriate level of access to Azure Purview's data plane.

Continue >