Ataccama ONE Agentic ONE Desktop ONE DQ&C ONE MDM ONE RDM ONE Runtime Server
Downloads

Microsoft Fabric Lakehouse Connection

This article describes how to connect Ataccama ONE to a Microsoft Fabric lakehouse through its SQL analytics endpoint.

Fabric creates the SQL analytics endpoint automatically for every lakehouse. The endpoint gives read-only SQL access to the Delta tables in the lakehouse. Files in the lakehouse Files section aren’t available through this connection.

Availability

Data processing & catalog Edge processing Lineage Exceptions

✔

✔

✗

Read-only: The SQL analytics endpoint doesn’t accept writes to tables. You can’t export data or invalid records to this connection.

SQL catalog items: A query that starts with a common table expression (WITH) can’t be combined with a table filter. To use a filter, move the query into a view and create the catalog item on the view.

Prerequisites

  • Review how sources and connections work.

  • Create a source to add this connection to.

  • Make sure you have a Microsoft Entra ID application (service principal) for ONE to sign in with.

  • Make sure your Fabric administrator has enabled the Service principals can use Fabric APIs tenant setting.

  • Make sure your workspace administrator has given the application access to the Fabric workspace that contains the lakehouse, through Manage access in the workspace. See Service principals in Fabric Data Warehouse.

  • If you process the connection on an edge instance, make sure the edge instance can reach the SQL analytics endpoint on TCP port 1433 and Microsoft Entra ID (login.microsoftonline.com) on port 443.

Add a connection

  1. Go to [your source] > Connections and select Add Connection.

  2. In Connection type, select Fabric Lakehouse SQL Endpoint.

  3. Fill in the following:

    • Name: A meaningful name for your connection. Used to indicate the location of catalog items.

    • Description (Optional): A short description of the connection.

    • Edge instance (Optional): The edge instance used to process this connection. Available only if edge processing is configured for your environment. See Edge Processing.

      • Compliance mode: Required if you select an edge instance. Controls which processing results can leave your edge environment. See Compliance mode.

    • Secret management service (Optional): The secret management service used to retrieve connection credentials at runtime. Available only if a secret management service is configured. See Secret Management Service.

    • JDBC: A JDBC connection string pointing to the SQL analytics endpoint of your lakehouse. See JDBC connection string format.

JDBC connection string format

The JDBC string has the following format:

JDBC connection string for the SQL analytics endpoint
jdbc:sqlserver://<SQL_ENDPOINT_HOST>:1433;database=<LAKEHOUSE_NAME>;encrypt=true

Replace the placeholders as follows:

  • <SQL_ENDPOINT_HOST>: The host name of the SQL analytics endpoint, shown as SQL connection string for the lakehouse in Fabric. It has the form <ENDPOINT_ID>.datawarehouse.fabric.microsoft.com.

  • <LAKEHOUSE_NAME>: The name of the lakehouse. Required; without it, the connection opens the master database, which contains no lakehouse tables.

Don’t add the authentication, user, or password keywords to the JDBC string, for example authentication=ActiveDirectoryServicePrincipal from the Microsoft examples. ONE signs in with the Entra ID credentials you add to the connection, and these keywords make the connection test fail.

Add credentials

Always use the dedicated credential fields for authentication details such as passwords, secrets, and tokens. This ensures credentials are handled with the appropriate level of protection and reliably preserved across environments.

To keep credentials in your existing infrastructure and have ONE retrieve them at runtime, configure a secret management service instead. See Secret Management Service.

One set of credentials must be defined as default for each connection. Otherwise, DQ evaluation fails and previewing data in the catalog is not possible.

This connection uses Entra ID credentials only, as Fabric doesn’t support SQL authentication.

To add the credentials:

  1. Select Add Credentials.

  2. Fill in the following:

    • Name: Provide a clear name for this set of credentials.

    • Description (Optional): Explain what the credentials are used for or provide other useful information.

    • Client ID: The application (client) ID registered in the Microsoft Entra portal.

      This appears as a GUID (for example, 4701c7e7-1178-4006-a1fc-b4c3ee5cfef7) and is found in the Entra ID portal in App registrations > [app name] > Overview.

    • Client Secret: The secret value generated for the application in the Microsoft Entra portal (App registrations > [app name] > Certificates & secrets). Client secrets expire, so renew the secret before its expiration date to avoid connection failures.

    • Tenant ID: The directory (tenant) ID of your Microsoft Entra instance.

      This appears as a GUID (for example, 12345678-1234-1234-1234-123456789012) and is found in the Entra ID portal in App registrations > [app name] > Overview.

      For details about registering an application and generating credentials, see Register an application with Microsoft Entra ID.

  3. To use this set of credentials by default when connecting to the data source, select Assign as default.

Next steps

Test and save your connection to complete setup.

Was this page useful?