.avif)
How Ridge works with Microsoft Fabric OneLake
What you can do
- Connect to a Fabric OneLake lakehouse via an Azure AD service principal
- Read Delta tables from
abfss://<workspaceId>@onelake.dfs.fabric.microsoft.com/<lakehouseId>/Tables - Work with schema-enabled lakehouses using schema/table notation
- Refresh on a schedule with standard cron expressions
What you'll need
A few connection details link Ridge to your lakehouse. Collect these before you start.
Set up the connection
1 Create a Connection
On the Data page, click New Connection and choose Microsoft Fabric OneLake as the type. Enter the credentials you gathered, then save.
- Tenant ID, Client ID, and Client Secret — your Azure AD app
- Workspace ID and Lakehouse ID — both GUIDs
2 Create a Dataset
Back on the Data page, click New, select source Connection, and pick the OneLake connection you just created. A Data Set points at a specific table and can carry its own refresh schedule.
3 Select a table
Choose the Delta table to read. Schema-enabled lakehouses need schema/table notation.
4 Schedule ingestion
Set an ingestion schedule with standard cron syntax, then save. Ridge reads the table and stores the results, ready for analysis.
Best practices
A few habits keep ingestion secure and predictable.
Supported features & limitations
- Reads OneLake Delta tables via an Azure AD service principal
- Supports schema-enabled lakehouses (requires schema/table notation)
- Validates the connection before ingestion by globbing the lakehouse
Tablesdirectory (no specific Delta table required) - Uses the DuckDB
azure,httpfs, anddeltaextensions (Azure curl transport)
- GUIDs required — workspace and lakehouse IDs must be valid GUIDs; friendly names are not supported.
Troubleshooting
Most connection issues fall into four buckets. Expand the one that matches your error.
Network unreachable
"error sending request", "could not resolve", "failed to connect", "DNS error", "timed out"
The token endpoint or OneLake is unreachable. Check egress to login.microsoftonline.com and onelake.dfs.fabric.microsoft.com.
Invalid credentials
"unauthorized", "invalid_client", "invalid tenant", "AADSTS…", "login failed"
Your tenant, client, or secret is wrong. Re-enter the Azure AD app credentials.
Insufficient permissions
"forbidden", "permission", "not authorized", "access denied"
The app lacks workspace or lakehouse access. Grant the service principal access in Fabric.
Resource not found
"not found", "does not exist", "no such", Delta "no files in log segment"
The table is wrong, or a schema-enabled lakehouse needs schema/table notation. Fix the table identifier or use schema.table.
Configuration invalid
400, "should be either valid GUIDs", "FriendlyNameSupportDisabled"
A workspace or lakehouse id isn't a GUID. Use the GUID ids, not friendly names.
