This page outlines how to connect an external catalog on the Immuta app settings page. For details on prerequisites and external catalogs with Immuta, see the External catalog pre-configuration checklist.

Link an Alation catalog

1. Navigate to the App Settings page.

2. Scroll to 2 External Catalogs, and click Add Catalog.

3. Enter a Display Name and select Alation from the dropdown menu.

4. Complete the URL and API key fields. In order to generate an API access token for your Alation instance, follow the Alation documentation.

5. Configure whether or not Alation tags and custom fields are imported as Immuta tags:

   • Link Alation tags: When selected, Immuta imports Alation tags as Immuta tags.

   • Link Alation Custom Fields: When selected, Immuta imports Alation custom fields as Immuta tags.

6. Opt to select Upload Certificates.

   1. Upload the Certificate Authority, Certificate File, and Key File.

   2. Opt to enable Strict SSL by selecting the checkbox.

7. Click the Test Connection button.

8. Once the connection is successful, click Save.

Link a Collibra catalog

1. Navigate to the App Settings page.

2. Scroll to 2 External Catalogs, and click Add Catalog.

3. Enter the Display Name and select Collibra from the dropdown menu.

4. Enter the HTTP endpoint of the catalog in the URL field.

5. Complete the Username and Password fields. Note: This is the username and the password that Immuta can use to connect to the external catalog.

6. Opt to Require the data source name in Collibra to contain both the schema and table name by selecting the checkbox.

7. Complete the Asset Mappings modal to set which asset types in Collibra should align to Immuta's data sources and columns.

8. Complete the Attributes as Tags modal to specify which Collibra attributes you would like to pull in as tags in Immuta.

9. Opt to select Upload Certificates.

   1. Upload the Certificate Authority, Certificate File, and Key File.

   2. Opt to enable Strict SSL by selecting the checkbox.

10. Click the Test Connection button.

11. Once the connection is successful, click Save.

Link a Microsoft Purview external catalog

Prerequisite

Register an app in the Azure portal with the with the following settings:

• Supported account type: "Accounts in this organizational directory only"

• Microsoft-Graph: User.Read API permission

• A client secret

Using that registered app, navigate to Immuta and complete the following:

1. Navigate to the App Settings page.

2. Scroll to 2 External Catalogs, and click Add Catalog.

3. Enter the Display Name and select Microsoft Purview from the dropdown menu.

4. Complete the following fields:

   1. Enter the Microsoft Purview endpoint URL including the Azure Account Name, like https://<ACCOUNTNAME>.purview.azure.com, in the Purview Endpoint URL field.

   2. Complete the Microsoft Entra Directory (tenant) ID and Microsoft Entra (client) ID fields.

   3. Enter the Microsoft Entra Application Client Secret ID for Immuta to authenticate and connect to the Purview API. The secret cannot be expired.

5. Click the Test Connection button.

6. Once the test is successful, click Save.

Link a custom REST catalog

Integrating a custom REST catalog service with Immuta requires implementing a REST interface. For details about the necessary endpoints that must be serviced, see the Custom REST catalog interface endpoints page.

1. Navigate to the App Settings page.

2. Scroll to 2 External Catalogs, and click Add Catalog.

3. Enter the Display Name and select Rest from the dropdown menu.

4. Select the Internal Plugin checkbox if the catalog has been uploaded to Immuta as a custom server plugin.

5. Complete the following fields:

   1. Enter the HTTP endpoint of the catalog in the URL field.

   2. Complete the Username and Password fields.

   3. Enter the path of the Tags Endpoint.

   4. Enter the path of the Data Source Endpoint.

   5. Enter the path to the information page for a data source in the Data Source Link Template field.

6. Opt to enter the path to the information page for a column in the Column Link Template field.

7. Opt to upload a Catalog Image.

8. Opt to select Upload Certificates.

   1. Upload the Certificate Authority, Certificate File, and Key File.

   2. Opt to enable Strict SSL by selecting the checkbox.

9. Click the Test Connection button.

10. Click the Test Data Source Link.

11. Once both tests are successful, click Save.

Enable Snowflake tag ingestion

See the Configure a Snowflake integration page for guidance on configuring tag ingestion.

If Snowflake data sources existed before configuring tag ingestion, Immuta will automatically sync those data sources to the catalog and apply tags to them. Immuta will automatically check the external catalog for changes and sync data sources to the catalog every 24 hours.

Enable Databricks Unity Catalog tag ingestion

See the Configure a Databricks Unity Catalog integration page for guidance on configuring tag ingestion.

If Databricks Unity Catalog data sources existed before configuring tag ingestion, Immuta will automatically sync those data sources to the catalog and apply tags to them. Immuta will automatically check the external catalog for changes and sync data sources to the catalog every 24 hours.

Manually link catalogs to data sources

You can manually link and remove external catalogs from data sources on the data source overview tab.

1. Navigate to your data source.

2. In the connection information section, click the Link Catalog icon (or Unlink Catalog to remove an external catalog from a data source).

3. Select your external catalog from the dropdown menu.

4. Click Link to confirm.

Manually sync external catalog tags

1. Navigate to your data source and click the data source Health dropdown menu.

2. Click Re-run in the External Catalog section.

Users who want to use tagging capabilities outside of Immuta and pull tags from external table schemas can connect Alation, Collibra, or Microsoft Purview as an external catalog. If users have an unsupported catalog, or have customized their integration, they can connect through the REST Catalog using the Immuta API. Users can also connect to and ingest tags from Snowflake and Databricks Unity Catalog onto Snowflake and Databricks Unity Catalog data sources.

Once they have been connected, Immuta will ingest a data dictionary from the catalog that will apply data source and column tags directly onto data sources. These tags can then be used to drive governance policies or classification frameworks. Using existing metadata from external catalogs can allow users to scale policy creation quickly.

Supported external catalogs

Immuta supports the following external catalogs:

• Alation

• Collibra

• Microsoft Purview

• Custom REST catalog

• Databricks Unity Catalog tag ingestion

• Snowflake tag ingestion

Microsoft Purview catalog

The Microsoft Purview catalog integration with Immuta currently supports tag ingestion for Databricks Unity Catalog and Azure Synapse Analytics data sources.

In addition to tags, the following Purview objects will also be pulled in and applied to data sources as either column or data source tags in Immuta:

• System classifications

• Custom classifications

• Managed attributes

Managed attributes limitations

Managed attributes are supported, but have the following limitations: