> For the complete documentation index, see [llms.txt](https://docs.telm.ai/telmai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.telm.ai/telmai/integrations/catalog-integration/microsoft-fabric-onelake.md).

# Microsoft Fabric OneLake

Read Microsoft Fabric OneLake workspace metadata into Telmai and connect its warehouses and lakehouses automatically

Telmai reads metadata from a [Microsoft Fabric](https://learn.microsoft.com/en-us/fabric/) workspace for dataset discovery and one-click monitoring of the workspace's warehouses and lakehouses.

**One integration represents one Fabric workspace.** On each sync, Telmai discovers the warehouses and lakehouse schemas in that workspace and can create, test, and link a Telmai [Microsoft Fabric connection](/telmai/connect-to-data/data-connections/microsoft-fabric.md) for each of them automatically.

{% hint style="info" %}
This integration applies to Telmai **Microsoft Fabric** data connections. To bring catalog metadata to assets from other connection types, use the [Actian Data Intelligence](/telmai/integrations/catalog-integration/zeenea.md) integration.
{% endhint %}

***

## Step 1: Prepare a service principal

Telmai authenticates to Fabric with a Microsoft Entra service principal (client ID and secret). You can reuse the same app registration as your Microsoft Fabric data connections.

1. Register an application in Microsoft Entra by following Microsoft's [Register an application](https://learn.microsoft.com/en-us/entra/identity-platform/quickstart-register-app) guide, and create a client secret for it.
2. Collect the **Directory (tenant) ID**, the **Application (client) ID**, and the **client secret**.
3. Grant the service principal access to the Fabric workspace you want Telmai to read.

{% hint style="warning" %}
Your Fabric tenant administrator must enable **"Service principals can use Fabric APIs"**. Without it, the Fabric API answers `401`/`403` and the connection test fails.
{% endhint %}

### Find the workspace ID

Open the workspace in the Fabric portal and read the GUID from the address bar: `.../groups/<workspaceId>/...`

***

## Step 2: Connect to Microsoft Fabric OneLake

In Telmai, go to **Administration** and, under **Catalogs**, select **Microsoft Fabric OneLake**.

| Field                     | Description                                                                                                 |
| ------------------------- | ----------------------------------------------------------------------------------------------------------- |
| Microsoft Entra Tenant ID | Directory (tenant) ID of the Microsoft Entra app registration                                               |
| Client ID                 | Application (client) ID of the service principal                                                            |
| Client secret             | Client secret of the service principal. Leave blank when updating other fields to keep existing credentials |
| Workspace ID              | The workspace GUID from the Fabric portal URL (`/groups/<workspace id>/`)                                   |
| Sync Interval (hours)     | How often Telmai syncs metadata. Accepts values between 1 and 168 hours                                     |

### Automatic connections

| Option                             | Description                                                                                                                                                 |
| ---------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Connect data sources automatically | On each sync, create, test, and link a Telmai connection for every warehouse and lakehouse schema in the workspace                                          |
| Target project                     | The project that automatically created connections are added to. Required while **Connect data sources automatically** is on                                |
| Map existing connections           | Reuse an existing Telmai connection that already points at the same warehouse or lakehouse schema, instead of creating a second one for it                  |
| Connection scope                   | Where the sync looks for an existing connection to reuse: **All** connections in the tenant, the global connections only, or a single project's connections |

Select **Connect**. Connecting runs a connection test and triggers an immediate first sync. **Sync now** triggers a sync at any time thereafter.

{% hint style="warning" %}
Only one catalog can be connected at a time. **Disconnect** the current catalog before connecting a different one.
{% endhint %}

### Advanced settings

Advanced settings are optional provider-specific key/value settings passed straight to the catalog. Leave them empty to use the defaults. Use **Add setting** to add one.

***

## Step 3: Link sources and start monitoring

Open **Connections** from the side menu and choose the **Catalog** tab. It lists the warehouses and lakehouse schemas discovered from the Fabric workspace, and their tables. See [The Catalog tab](/telmai/integrations/catalog-integration.md#the-catalog-tab) for everything on the tab.

When **Connect data sources automatically** is on, each sync creates and links the connections for you. When it is off, click **Create connection** on a source to create its Microsoft Fabric connection, or **Link** to use an existing one.

See [Monitor Recommendations](/telmai/monitoring-data/monitors-management/monitor-recommendations.md) for how recommended rules are reviewed and added.

## Related pages

* [Catalog Integration](/telmai/integrations/catalog-integration.md)
* [Microsoft Fabric connector](/telmai/connect-to-data/data-connections/microsoft-fabric.md)
* [Databricks Unity Catalog](/telmai/integrations/catalog-integration/databricks-unity-catalog.md)
* [Monitor Recommendations](/telmai/monitoring-data/monitors-management/monitor-recommendations.md)
