Sybase: Create an Azure Data Lake Storage connection

Do you use a vault?

You can use a vault to add your data source information to your Edge site connection. Check the connection property table below to see which information is available for your vault. Vaults are not available for Collibra Cloud site sites.	No vault AWS Secrets Manager Azure Key Vault CyberArk Vault Google Secret Manager HashiCorp Vault
	Select another vault I don't use a vault AWS Secrets Manager Azure Key Vault CyberArk Vault Google Secret Manager HashiCorp Vault
How to use your vault... To use your vault, do the following: In the Value Type field, select Vault Key. Enter the query value to identify the secret in your vault. Example  Note The Query must be a string containing the properties required to identify the secret. Each property must be separated by a semicolon (;). For example: Safe=<SafeName>;Folder=<FolderName>;Object=<ObjectName> If a property is a folder with sub-folders, use a backslash (\) to define the folder path. For example: Folder=Root\Top Secrets\More Secrets For more information about query formats and supported properties, go to the CyberArk Credential Provider documentation. To use your vault, do the following: In the Value Type field, select Vault Key. Enter the required information: Secret Engine Type Select one of the following: Key Value Database Engine Path The engine path to your vault where the value is stored. Secret Path The secret path to your vault where the value is stored. Field If your Secret Engine Type is Key Value, enter the name of the field to your vault where the value is stored. Role If your Secret Engine Type is Database, enter the role specified in the Database engine. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the required information: Vault Name The name of your Azure Key Vault in your Azure Key Vault service where the value is stored. Secret Name The name of the secret in your vault where the value is stored. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the required information: Secret Name The name of the secret in your vault where the value is stored. Field If the secret stored in your AWS Secrets Manager is a JSON value, for example {"pass1": "my-password", "pass2": "my-password2"}, then you need to specify the Field to point to the exact JSON value that should be used. For example, Secret Name: edge-db-customer; Field: pass. Note If the secret stored in your AWS Secrets Manager is a plain string value, for example my-password, then you do not need to specify the Field. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the name of the secret in your vault where the value is stored. Example

Prerequisites

In your Collibra environment

• In Azure:
  • To integrate ADLS folders, you need an Azure Service Principal user that is defined in Azure and that has permissions to list the files that need to be integrated into Collibra. The Azure Service Principal user must have the "Reader" and "Storage Blob Data Reader" roles for the storage locations of your data. For information, go to the Azure documentation.
    
  • If you use Microsoft Purview:
    • The Azure Service Principal user must have the "Data reader" role to fetch entities/assets from the Microsoft Purview Rest API. For information, go to the Microsoft Purview documentation.
    • If your ADLS storage is private, ensure that the Allow Azure services on the trusted services list to access this storage account checkbox in the Networking → Firewalls and virtual networks is selected.
• You created and installed an Edge site. If you have defined an outbound (forward) proxy on your Edge site, the integration considers that configuration when connecting to the data source.
You have added a vault to your Edge site.
If your data source connection requires a file from your vault, the file must be encoded into Base64 and stored as a regular secret in your vault.
• If you have configured a forward proxy for your Edge site and want the integration API calls to bypass this proxy, update the Edge nonProxy property:
  • Adding login.microsoftonline.com allows the API calls that get access tokens to bypass the proxy. If you are using a government cloud host, add login.microsoftonline.us instead.
  • Adding dfs.core.windows.net or blob.core.windows.net allows the ADLS API calls to bypass the proxy.
  • Adding purview.azure.com allows the Purview APIs to bypass the proxy.
• You have a global role that has the Manage connections and capabilities global permission, for example, Edge integration engineer.

In your Azure environment

• To integrate ADLS folders, you need an Azure service principal user that is defined in Azure and has permissions to list the files to be integrated into Collibra. The Azure service principal user must have the following roles for the storage locations of your data:
  • Reader
  • Storage Blob Data Reader
  For more information, go to the Azure documentation.
• If you also use Microsoft Purview:
  • The Azure service principal user must have the Data reader role to fetch entities/assets from the Microsoft Purview Rest API. For more information, go to the Microsoft Purview documentation.
  • If your ADLS storage is private, ensure that the Allow Azure services on the trusted services list to access this storage account checkbox in the Networking → Firewalls and virtual networks is selected.

Steps

1. Open a site.
   1. On the main toolbar, click → Settings.
      The Settings page opens.
   2. In the tab pane, click Edge.
      The Sites tab opens and shows a table with an overview of your sites.
   3. In the table, click the name of the site whose status is Healthy.
      The site page opens.
2. In the Connections section, click Create connection.
   The Create connection page appears.
3. Select the Azure connection to connect to Azure Data Lake Storage.
4. Enter the required information.

   Field	Description	Required	Available for vaults?
   Name	The name of the Edge site connection for Azure Data Lake Storage.	Yes	No
   Description	The description of the connection.	No	No
   Azure US Government Cloud Host	Option to indicate that the authentication must go through the government-specific Microsoft Entra authentication endpoint instead of the global Azure endpoint. Select this option if you are using a government cloud host. For information about cloud hosts, go to the Azure documentation.	No	No
   Vault	The vault where you store your data source values.	No	No
   Service Principal ID	The Application account ID to connect to the Azure. For information on the Azure Service Principal user and the Application ID, go to the Azure documentation.	Yes	Yes
   Service Principal Secret	The application secret for the Service Principal. For information on the application secret value, go to the Azure documentation.	Yes	Yes
   Tenant ID	The Tenant ID of your Azure Active Directory. For information on the Directory (tenant) ID, go to the Azure documentation.	Yes	Yes

5. Click Create.
   The connection is added to the Edge site.