Connectors and Connections > Data Ingestion and Replication connection properties > Microsoft Fabric OneLake connection properties
  

Microsoft Fabric OneLake connection properties

Create a Microsoft Fabric OneLake connection to securely read from or write to Microsoft Fabric OneLake.

Prerequisites

Before you configure the connection properties, make sure to complete the following prerequisites:
  1. 1Power BI prerequisites:
    1. aCreate a workspace, if it does not already exist.
    2. bCreate a lakehouse in the workspace. Make sure you have the required admin privileges to create a lakehouse.
    For more information about creating a workspace and lakehouse, see Creating a workspace and lakehouse.
  2. 2Microsoft Azure portal prerequisites:
    1. aRegister your application in Microsoft Entra ID and generate client ID, tenant ID, and client secret.
    2. The connector does not require any API permissions assigned to your application. Additionally, you can remove any API permissions that are assigned to the application.
    3. bCreate a security group with assigned owners or members in Microsoft Entra ID.
    4. For more information about creating a security group, see Creating a security group.
  3. 3To allow Microsoft Entra app to use the Power BI APIs, enable the Power BI service admin settings, and then add the Microsoft Entra app to the workspace in Power BI.
  4. Note:
    The Manage access pane in the Microsoft Entra app allows you to add roles based on the required capabilities. The pane displays admin, member, contributor, and viewer roles. The maximum number of capabilities are associated with the admin role. However, to access Microsoft Fabric OneLake and perform read and write operations, you need at least the Contributor role.
    For more information about enabling access in the Power BI admin portal and adding the Microsoft Entra app to the workspace, see Enabling access in the Power BI portal.

Connect to Microsoft Fabric OneLake

Let's configure the Microsoft Fabric OneLake connection properties to connect to Microsoft Fabric OneLake.

Before you begin

Before you get started, you'll need to keep the workspace name, lakehouse path, client ID, client secret, and tenant ID details handy.
Check out Prerequisites to make sure that the setup is complete and all the prerequisites are in place before you configure a connection.

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.
Use Secret Vault
Stores sensitive credentials for this connection in the secrets manager that is configured for your organization.
This property appears only if secrets manager is set up for your organization.
This property is not supported by Data Ingestion and Replication and the Data Access Management services.
When you enable the secret vault in the connection, you can select the credentials that the Secure Agent retrieves from the secrets manager. If you don't enable this option, the credentials are stored in the repository or on a local Secure Agent, depending on how your organization is configured.
Note:
If you’re using this connection to apply data access policies through pushdown or proxy services, you cannot use the Secret Vault configuration option.
For information about how to configure and use a secrets manager, see "Secrets manager configuration" in the Administrator help.
Runtime Environment
The name of the runtime environment where you want to run the tasks.
For application ingestion and replication tasks and database ingestion and replication tasks, you can use the Secure Agent or serverless runtime environment. The tasks must have a source type supported for serverless use. For file ingestion and replication tasks, you can use only the Secure Agent. You cannot run tasks on a Hosted Agent or elastic runtime environment.
For more information about runtime environments, see Runtime Environments in the Administrator help.
Workspace Name
Name of the workspace in Microsoft Fabric OneLake.
Workspace name cannot contain special characters or spaces.
Lakehouse Path
Path or name of the lakehouse present in the workspace.
You can specify the path in one of the following ways:
  • - root directory (/) to access the files in the workspace.
  • - lakehouse name/Files to access the files present in the lakehouse.
Authentication Type
Authentication type to access Microsoft Fabric OneLake.
Service Principal Authentication uses the client ID, client secret, and tenant ID to connect to Microsoft Fabric OneLake.
Client ID
The application ID or client ID of your application registered in the Azure Active Directory.
Client Secret
The client secret of your application registered in the Azure Active Directory.
Tenant ID
The ID of the Azure Active Directory instance in which you created the application.
Microsoft Fabric OneLake Endpoint
The type of Microsoft Fabric OneLake endpoint that you want to connect to.
Default is fabric.microsoft.com.
Note:
You can access Microsoft Fabric OneLake using Azure Private Link endpoints for connections used in file ingestion and replication tasks.

Proxy Server Settings

If your organization uses an outgoing proxy server to connect to the Internet, the Secure Agent connects to Informatica® Intelligent Data Management Cloud™ (IDMC) through the proxy server.
You can configure the Secure Agent to use the proxy server on Windows and Linux. You can use the unauthenticated or authenticated proxy server.
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
  3. 2Specify the following command in the proxy.ini file:
  4. InfaAgent.NonProxyHost=localhost|{*}onelake.blob.fabric.microsoft.com|onelake.dfs.fabric.microsoft.com |127.|[\:\:1]*
  5. 3Restart the Secure Agent.