Connectors and Connections > Data Ingestion and Replication connection properties > Microsoft Azure Data Lake Storage Gen2 connection properties
  

Microsoft Azure Data Lake Storage Gen2 connection properties

Create a Microsoft Azure Data Lake Storage Gen2 connection to securely read data from or write to Microsoft Azure Data Lake Storage Gen2.

Prepare for authentication

You can configure Shared Key, Managed Identity, and Service Principal authentication types to access Microsoft Azure Data Lake Storage Gen2. Before you configure the authentication, you need to set up your environment and keep the authentication details handy.

Create storage account and configure access

To access Microsoft Azure Data Lake Storage Gen2, follow these steps to set up your environment:
  1. 1Set up a storage account to use with Microsoft Azure Data Lake Storage Gen2 and create a blob container in the storage account. You can use role-based access control or access control lists to authorize users to access the resources in the storage account.
  2. 2Register the application in Azure Active Directory to authenticate users to access the Microsoft Azure Data Lake Storage Gen2 account. You can use role-based access control or access control lists to authorize the application.
  3. 3Create an Azure Active Directory web application for service-to-service authentication with Microsoft Azure Data Lake Storage Gen2. Ensure that you have superuser privileges to access the folders or files created in the application.
    4. For more information about these prerequisite tasks, see the Informatica How-To Library article, Prerequisites to create a Microsoft Azure Data Lake Storage Gen2 connection.

Get authentication details

Ensure you get all the required authentication details based on the authentication method you want to use in the connection:
Service principal authentication
You need the client ID, client secret, and tenant ID for your application registered in the Azure Active Directory.
Shared key authentication
You need the account key for the Microsoft Azure Data Lake Storage Gen2 account.
Managed identity authentication
You need the client ID or application ID for your application registered in the Azure Active Directory. Before you get the client ID or application ID, be sure to complete certain prerequisites.

Managed identity authentication

Managed Identity authentication uses managed identities in Azure Active Directory to authenticate and authorize access to Azure resources securely.
Before you use managed identity authentication to connect to Microsoft Azure Data Lake Storage Gen2, be sure to complete certain prerequisites.
  1. 1Create an Azure virtual machine.
    2. To configure managed identity authentication in a Microsoft Azure Data Lake Storage Gen2 connection, select the Azure virtual machine on which you have installed the Secure Agent.
  2. 2Install the Secure Agent on the Azure virtual machine.
  3. 3Enable system assigned identity or user assigned identity for the Azure virtual machine.
    4. If you enable system assigned identity, assign the required role or permissions to the Azure virtual machine to run mappings and tasks. If you enable user assigned identity, assign the required role or permissions to the user assigned identity. For example, if you use role-based access control, assign the Storage Blob Data Contributor role and if you use access control lists, assign the read, write, and execute permissions. If you enable both and do not specify the client ID, the system assigned identity is used for authentication.
  4. 4After you add or remove a managed identity, restart the Azure virtual machine.

Connect to Microsoft Azure Data Lake Storage Gen2

Let's configure the Microsoft Azure Data Lake Storage Gen2 connection properties to connect to Microsoft Azure Data Lake Storage Gen2.

Before you begin

Before you get started, you'll need to get information from your Microsoft Azure Data Lake Storage Gen2 account based on the authentication type that you want to configure.
Check out Prepare for authentication to learn more about the authentication prerequisites.

Connection details

The following table describes the basic connection properties:
Property
Description
Connection Name
Name of the connection.
Each connection name must be unique within the organization. Connection names can contain alphanumeric characters, spaces, and the following special characters: _ . + -,
Maximum length is 255 characters.
Description
Description of the connection. Maximum length is 4000 characters.
Type
Microsoft Azure Data Lake Storage Gen2
Runtime Environment
The name of the runtime environment where you want to run tasks.
You cannot run an application ingestion and replication task, database ingestion and replication task or streaming ingestion and replication task on a Hosted Agent or serverless runtime environment.
Account Name
Microsoft Azure Data Lake Storage Gen2 account name or the service name.
File System Name
The name of the file system in the Microsoft Azure Data Lake Storage Gen2 account.
Directory Path
The path of a directory without the file system name.
You can select from the following directory structures:
  • - / for root directory
  • - /dir1
  • - dir1/dir2
Default is /.

Authentication types

You can select service principal authentication, shared key authentication, and managed identity authentication to access the Microsoft Azure Data Lake Storage Gen2 account.
Note: Data Ingestion and Replication supports managed identity authentication. However, Streaming Ingestion and Replication does not support shared key authentication or managed identity authentication.
Select your preferred authentication type and then configure the authentication-specific parameters.

Proxy Server Settings

If your organization uses an outgoing proxy server to connect to the Internet, the Secure Agent connects to Informatica Intelligent Cloud Services through the proxy server.
Note: You cannot use a proxy server with managed identity authentication.
You can use one of the following types of proxy servers:
To configure proxy settings for the Secure Agent, use one of the following methods:

Bypass the proxy server

You can bypass the proxy server settings configured for the Secure Agent.
Perform the following steps to bypass the proxy server:
  1. 1Navigate to the following directory:
    2. <Secure Agent installation directory>/apps/agentcore
  2. 2Enter the following command in the proxy.ini file:
    3. InfaAgent.NonProxyHost=localhost|{*}core.windows.net|127.|[\:\:1]*
    For example, InfaAgent.NonProxyHost=localhost|127.*|[\:\:1]|<accountname>.blob.core.windows.net|<accountname>.dfs.core.windows.net|<accountname>.blob.core.windows.net|login.microsoftonline.com|169.254.169.254
  3. 3Restart the Secure Agent.