Our Snippets Of Knowledge Weekly Blog Series
The original Microsoft data cataloguing tool has had a bumpy and confusing past. Originally Data Catalogue v1 and v2, then Azure Purview, now Microsoft Purview. With each update the tool has grown from simple data catalogue use cases to a full security, governance and compliance platform.
The confusion also continues because for IT teams dealing with compliance and uses cases such as data loss prevention, they also use ‘Microsoft Purview’. Which is different to the common data platform uses cases a data engineer might consider, also named and delivered using a different ‘Microsoft Purview’ product. In most pragmatic conversations, the old name, Azure Purview must be used to understand what we need to implement for data governance work.
Once naming has been sorted, data cataloguing, classification, sensitivity labelling, and lineage can be delivered for a given data platform. With support and access to the underlying Apache Atlas API’s when functionality isn’t available via the Purview user interface.
See MS Learn for more information on this Resource here.
We hope you found this knowledge snippet helpful.
Check out all our posts in this series here.