> ## Documentation Index
> Fetch the complete documentation index at: https://docs.isotopes.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Microsoft Fabric Connector

Connect Microsoft Fabric to aidnn to analyze data in a Fabric Warehouse or Lakehouse SQL analytics endpoint. The connector uses an Azure application (service principal) with read-only data access. You can optionally specify a database to limit which database aidnn ingests and queries.

> [!TIP]
>
> **Use Fabric as a governed, audited read point.** Fabric can provide an intermediate location for data from SharePoint folders, on-premises SQL Server or Oracle databases connected through gateways, and CRM tools such as ServiceNow or Salesforce (for example, customer support tickets). In these cases, Fabric is not the original source of the data; it is the governed and audited location aidnn reads from. See Microsoft's [Fabric Data Factory connector overview](https://learn.microsoft.com/en-us/fabric/data-factory/connector-overview).

## Prerequisites

Before adding the connector, ask your Microsoft Fabric or Azure administrator to:

* Create or identify an Azure application registration for the connector, and provide its **Client ID**, **Client Secret**, and **Tenant ID**.
* Grant the application's service principal access to the Fabric workspace and the Warehouse or Lakehouse SQL analytics endpoint you want aidnn to query. Give it read-only permissions to the data it needs to analyze, such as `SELECT`, and do not grant write or administrative permissions.
* Confirm the SQL endpoint host and port. Fabric SQL endpoints commonly use port `1433`.

The application must be enabled for service principal access in your organization's Fabric tenant settings. Your Fabric administrator can confirm the relevant tenant setting and workspace permissions.

### Read-only access best practices

* Use a dedicated service principal for aidnn rather than a personal account or an application shared with other workloads.
* For connectors used by dashboards with multiple users, choose **Public** visibility so the connector is available across your organization. Choose **Private** only when access should be limited to you.
* Grant access only to the Fabric workspace and Warehouse or Lakehouse that aidnn needs. In the SQL endpoint, grant read-only access to the required data (for example, `SELECT` on approved schemas or tables); do not grant write, ownership, or administrative permissions.
* If you enter a database in the **Database** field, also scope the service principal's SQL permissions to the required data in that database. The field limits the connector's target; it does not replace Fabric and SQL permissions.
* Store the client secret in your organization's approved secrets manager. Set an expiration, rotate it before it expires, and update the connector when you rotate it. Never put secrets in documentation, notebooks, or source control.
* Review the service principal's access periodically and remove permissions that are no longer needed.

## Add the Microsoft Fabric connector in aidnn

### Open the Connectors page

From the aidnn home screen, click **Connectors** in the left sidebar.

### Start a new connector

Click **Add New Connector** in the top-right corner. Find **Microsoft Fabric** and select it to open the **Add New Microsoft Fabric Service** form.

![Add New Microsoft Fabric Service form](https://mintcdn.com/isotopesai-e9db0a5b/4tJm68TWRy_IRrbi/data-sources/assets/microsoft-fabric-connector-form.png?fit=max\&auto=format\&n=4tJm68TWRy_IRrbi\&q=85\&s=cf1bd102ed206e2a0ce3873b2ff7c26a)

## Fill in the connector details

### General fields

* **Name** - A descriptive name for this connection, such as “Fabric Sales Warehouse.”
* **Description** - Optional context to help people identify the data source.
* **Visibility** - Choose **Public** for dashboards used by multiple people so the connector is available to your organization. Choose **Private** when only you should have access.

### Connection details

* **Host and Port** - The SQL endpoint host and port for your Fabric Warehouse or Lakehouse. Enter them in the format shown by the placeholder, such as `your-workspace.datawarehouse.fabric.microsoft.com:1433`. Get the endpoint from Fabric's SQL connection details.
* **Client ID** - The Azure application (service principal) client ID.
* **Client Secret** - The client secret for that application.
* **Tenant ID** - The Microsoft Entra tenant ID that contains the application.
* **Database** - Optional. Enter a Warehouse or Lakehouse database name to limit the connector's ingestion and queries to that database. The service principal should still have read-only permissions to the database.

Keep the client secret private. If you don't have the application credentials or endpoint details, ask your Azure or Fabric administrator.

## Test and create the connector

Click **Test Connection** to check that aidnn can reach the endpoint and authenticate with the service principal. If the test fails, confirm the host and port, the tenant and application IDs, the client secret, and the service principal's Fabric workspace and data permissions.

When the test succeeds, click **Create**. The connector is saved and appears on the Connectors page. If you need to adjust optional settings, expand **Advanced Configuration** before testing or creating the connector.

## Support

For help with Azure application credentials or Fabric access, contact your Microsoft Entra or Fabric administrator. For help with aidnn, email [support@isotopes.ai](mailto:support@isotopes.ai).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.