Microsoft Fabric Lakehouse

Overview

Solid connects to Fabric Lakehouses through the SQL analytics endpoint — a read-only TDS endpoint that Fabric exposes automatically for every Lakehouse. Authentication uses an Entra ID (Azure AD) service principal, so no per-user credentials are needed and access is managed at the application level.

Before you start, you will need:

A Fabric Lakehouse with the SQL analytics endpoint enabled (enabled by default)
Permission to create or use an Entra ID service principal in your Azure tenant
Permission to add the service principal as a Fabric workspace member

Step 1: Create an Entra ID service principal

If you already have a service principal for Solid, skip to Step 2.

In the Azure portal, navigate to Microsoft Entra ID → App registrations → New registration
Give it a name (e.g. solid-lakehouse)
Leave the redirect URI blank and click Register
On the app's Overview page, copy the Application (client) ID and Directory (tenant) ID — you'll need these in Step 4
Navigate to Certificates & secrets → Client secrets → New client secret
Set an expiration and click Add
Copy the Value immediately — it won't be shown again

Step 2: Grant the service principal access to your Fabric workspace

The service principal must be a member of the Fabric workspace that contains your Lakehouse. Solid only needs read access.

In Microsoft Fabric, open the workspace that contains your Lakehouse
Click Manage access in the top-right corner
Click Add people or groups
Search for your service principal by name (e.g. solid-lakehouse) and select it
Set the role to Viewer and click Add

Note: The service principal must be a workspace member, not just a direct Lakehouse permission — the SQL analytics endpoint checks workspace membership.

Step 3: Find your connection details

You'll need four values from Fabric before filling in the Solid form:

Host (SQL analytics endpoint)

Open your Lakehouse in Fabric
Click the SQL analytics endpoint view (toggle in the top-right)
Go to Settings (gear icon)

Under SQL connection string, copy the server name — it looks like:

xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx.datawarehouse.fabric.microsoft.com

Paste this value as-is, without https:// or a trailing slash

Workspace name or ID

The workspace name is shown in the Fabric breadcrumb. The ID is in the URL when you're inside the workspace:

https://app.fabric.microsoft.com/groups/<workspace-id>/...

Either value works in the Solid form.

Lakehouse name

The name of your Lakehouse as it appears in the Fabric workspace (not the SQL endpoint database name, though they are typically the same).

Step 4: Connect in Solid

In Solid, go to Settings → Integrations → Connect a data source
Select Microsoft Fabric Lakehouse
Fill in the connection form:

Field	What to enter
Host	SQL analytics endpoint, e.g. `xxxxxxxx.datawarehouse.fabric.microsoft.com` — no `https://` or trailing slash
Port	Leave as `1433` unless your network routes TDS traffic on a different port
Workspace	Your Fabric workspace name or workspace ID
Lakehouse	Your Lakehouse name
Tenant ID	The Entra ID directory (tenant) ID from Step 1
Client ID	The Entra ID application (client) ID from Step 1
Client Secret	The client secret value from Step 1
Query Timeout (seconds)	Leave as `300` unless queries consistently time out — increase only if needed

Click Test Connection to verify Solid can reach the endpoint
Select which schemas you want Solid to monitor and click Save

Permissions summary

What Solid needs	How to grant it
Read access to Lakehouse tables	Add the service principal as a Viewer in the Fabric workspace
Execute queries via the SQL endpoint	Included with the Viewer workspace role

The Viewer role is read-only — the service principal cannot write to or modify your Lakehouse data.

Troubleshooting

Test connection fails: "Login failed"

Verify the Tenant ID, Client ID, and Client Secret are all from the same app registration
Confirm the client secret has not expired (check under Certificates & secrets in the Azure portal)
Confirm the service principal is listed as a workspace member in Fabric (Step 2)

Test connection fails: "Cannot open server"

Check that the Host field contains only the hostname with no https://, no trailing slash, and no path
Confirm the SQL analytics endpoint is enabled on the Lakehouse (go to the Lakehouse in Fabric and check whether the SQL analytics endpoint view is available)
Ensure Solid's static IP addresses are permitted through your network firewall on port 1433

No schemas appear after connecting

The Lakehouse must contain Delta tables that have been loaded into the SQL analytics endpoint — tables appear there only after at least one table load or shortcut is set up
Confirm the tables are visible under the SQL analytics endpoint view in Fabric before connecting Solid

Query timeout errors

Increase Query Timeout (seconds) if Solid's queries are timing out on large tables
Consider filtering which schemas Solid monitors to reduce query scope