This article provides an overview of the available blocks in the Azure Purview connector in Qlik Application Automation.
Azure Purview is a cloud-based data governance service that helps you catalogue, manage, and govern your on-premises, multi-cloud, and software-as-a-service (SaaS) data. You can create a holistic, up-to-date map of your data landscape and prepare this with automated data discovery, sensitive data classification, and end-to-end data lineage.
Authentication to Azure Purview happens through OAuth 2.0 Authentication. To use this connector, you need to provide the client Id, client secret, tenant Id and account name of your Azure Purview account.
For a REST API client to access the catalog, the client must have a service principal (application), and an identity that the catalog recognizes and is configured to trust. When you make REST API calls to the catalog, they use the service principal's identity.
Please follow the steps here to create a service principle.
When you connect to Azure Purview in Qlik Application Automation you will be presented with the following screen:
The following blocks are available in Azure Purview Connector:
- list collection
- get collection
- create collection
- move entity to collection
- delete collection
- find entities
- list entities by entity type
- list new entities incrementally
- list new entities incrementally by entity type
- list updated entities incrementally
- list updated entities incrementally by entity type
- create entity
- get entity by guid
- update entity by guid
- get entity by unique attribute
- get entity by qualified name
Type Definitions Endpoints
- get type definition by name
- list type definition headers
- create type definitions
- update type definitions
- list type definitions
- delete type definitions by name
- create relationships
- delete relationship
- get relationship by guid
- get relationship definition
The information in this article is provided as-is and will be used at your discretion. Depending on the tool(s) used, customization(s), and other factors ongoing support on the solution below may not be provided by Qlik Support.