Let's review some of the major topics from our United Data Governance with Microsoft Purview Course. In the first lecture group, we reviewed how to provision and set up Microsoft Purview in our Azure tenant. We stepped through a number of roles that are available for Purview users and talked through how data sources are registered and added to collections in the program. Once added, we demonstrated how to ingest target metadata into the platform by scanning the sources. 

We also reviewed how the business glossary is populated with various terms from all aspects of the organization. We ended the first section by reviewing the different pathways to search or browse the Purview data catalog. In the second lecture group, we reviewed how to enrich metadata with classifications, glossary terms, and custom fields. These help extend the ability of users to search and find relevant data elements. Lineage providers can support showing an end-to-end journey of data as it moves through our data estate. We also reviewed the 200+ classifications that are available in Purview as well as the manner to create custom classifications. 

Purview data estate insights helps provide a summary view of our data map and management controls offer a granular way of administering various aspects of the program. In the last lecture group, we reviewed various deployment considerations when releasing Purview. For security conscious organizations, we can use private endpoints and private networks to connect to our Purview catalog. This ensures that only allowable network traffic is able to reach these resources. Furthermore, we explored how Purview scanning can be extended to other cloud providers like Amazon Web Services and Snowflake. Finally, we reviewed the phased approach that Purview should be released in. This ensures that the right stakeholders are participating in the process each step along the way.