> For the complete documentation index, see [llms.txt](https://docs.wobby.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wobby.ai/connections/connect-a-data-source/microsoft-fabric.md).

# Microsoft Fabric

Actian AI Analyst can connect directly to your Microsoft Fabric data warehouse using a service principal from your Microsoft Entra (Azure AD) tenant.

#### Step 1: Create an App Registration in Microsoft Entra ID

1. Go to the **Azure Portal** → **Microsoft Entra ID** → **App registrations**.
2. Click **New registration**.
   * **Name**: Can be anything (e.g., `actian-analyst-fabric-access`).
   * **Supported account types**: *Single tenant*.
   * **Redirect URI**: Leave blank.

<figure><img src="/files/YmhQIiwVOp8xsf1ZRiEb" alt="" width="375"><figcaption></figcaption></figure>

***

#### Step 2: Note Your Tenant and Client IDs

After creating the app, copy:

* **Directory (tenant) ID**
* **Application (client) ID**

You'll need these later for the Actian AI Analyst connection form.

***

**Step 3: Create a Client Secret**

1. In your app registration, go to **Certificates & secrets**.
2. Under **Client secrets**, click **New client secret**.
3. Add a description (e.g., `actian-analyst-fabric-secret`) and choose an expiry period.
4. **Important**: Copy the **Value** (not the Secret ID) immediately and store it securely.
   * You won't be able to view the value again once you leave the page.

<figure><img src="/files/Prr086GESELlXCst19Cc" alt="" width="375"><figcaption></figcaption></figure>

***

Step 4: Grant Database Access to the Service Principal

Run the following commands in your Fabric SQL database to grant read access:

```sql
CREATE USER [<service-principal-name>] FROM EXTERNAL PROVIDER;
ALTER ROLE db_datareader ADD MEMBER [<service-principal-name>];
```

* Replace `<service-principal-name>` with your app registration's display name.
* Use `db_datareader` for read-only access (recommended).
* Only use `db_owner` if the agent needs full control — generally **not** needed for Actian AI Analyst.

***

Step 5: Add the Connection in Actian AI Analyst

1. Click **Connections → Plus button → Select Microsoft Fabric**.
2. Fill in the form:

| Field             | Value                                                                  |
| ----------------- | ---------------------------------------------------------------------- |
| **Display Name**  | How you want the source to appear in Actian AI Analyst                 |
| **SQL Host**      | Your Fabric SQL host (ends with `.datawarehouse.fabric.microsoft.com`) |
| **Database**      | The Fabric database name                                               |
| **Schema**        | The schema to use (often `dbo`)                                        |
| **Tenant ID**     | From Step 2                                                            |
| **Client ID**     | Application (client) ID from Step 2                                    |
| **Client Secret** | From Step 3                                                            |

***


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.wobby.ai/connections/connect-a-data-source/microsoft-fabric.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.