> For the complete documentation index, see [llms.txt](https://docs.ovaledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ovaledge.com/release7.2/connectors/connector-repositories/rdbms/microsoft-sql-server/fabric-warehouse-lakehouse-integration.md).

# Fabric Warehouse / Lakehouse Integration

Microsoft Fabric Warehouse / Lakehouse can be integrated with OvalEdge through the SQL Analytics Endpoint. Azure Active Directory authentication provides secure access to the Fabric Warehouse / Lakehouse and supports metadata extraction, profiling, and lineage.

This article describes the required access configuration and the steps to establish the integration using the Microsoft SQL Server connector.

### Supported Authentication Methods

* Managed Identity (User Assigned)
* Service Principal

{% hint style="warning" %}
Select the authentication method based on the deployment model and security policies.
{% endhint %}

### Prerequisites

Ensure the following conditions are met before proceeding:

#### 1. Fabric Environment Setup

* An active Fabric workspace is available
* The target Warehouse / Lakehouse is created and accessible.

#### 2. Identity Requirements

* A User Assigned Managed Identity (UAMI) or Service Principal (SP) is created
* The identity is associated with the Bridge Client VM (if applicable).

#### 3. Access Permissions

The user performing this configuration must have:

* Workspace Admin, Owner, or equivalent role
* Permission to manage access (**roleAssignments/write**).

{% hint style="warning" %}
If sufficient privileges are not available, the Manage Permissions option will not be accessible.
{% endhint %}

### Fabric Warehouse / Lakehouse Access Configuration

Viewer-level access is required for the identity used to connect to the Fabric Warehouse / Lakehouse. This access uses the **Read all data using SQL (ReadData)** permission.

Viewer access enables the connector to:

* Execute read-only SQL queries.
* Access schema and metadata.
* Perform metadata crawling and profiling.

### Steps to Configure Viewer Access

Follow the steps below to configure read-only access:

#### Step 1: Access Fabric Portal

* Log in to the **Microsoft Fabric Portal**
* Use an account with **Admin** or **Owner privileges**

#### Step 2: Navigate to Workspace

* Open the required Fabric Workspace
* Locate the target Warehouse / Lakehouse

#### Step 3: Open Manage Permissions

* Click on the **three-dot menu (⋯)** for the Warehouse / Lakehouse<br>

  <figure><img src="https://1813356899-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhTnkoJQml0pok9awFDhx%2Fuploads%2FgtCsOSElMeGpxIYThtyF%2Fimage.png?alt=media&amp;token=a4396863-f5f2-4321-a894-40f16cf4a48b" alt=""><figcaption></figcaption></figure>
* Select **Manage Permissions**

#### Step 4: Add Identity

* Click **+ Add user**
* Select the required identity:
  * User Assigned Managed Identity (UAMI)
  * Service Principal (SP)

<figure><img src="https://1813356899-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhTnkoJQml0pok9awFDhx%2Fuploads%2FlhaqajdEHi0KdbExjxyL%2Fimage.png?alt=media&amp;token=fad237bd-ad7e-4ad3-9bc0-ab4b430fe6f2" alt=""><figcaption></figcaption></figure>

#### Step 5: Assign Viewer Permission

* **Select the permission:** Read all data using SQL (ReadData)

This enables:

* Read-only SQL query execution
* Metadata and schema visibility
* Secure access without modification capability

<figure><img src="https://1813356899-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhTnkoJQml0pok9awFDhx%2Fuploads%2FBM4lkZPjMHnWeajfsk6K%2Fimage.png?alt=media&amp;token=1a6bc80c-5a4e-498a-88a2-3c474c567d00" alt=""><figcaption></figcaption></figure>

#### Step 6: Validate Configuration

* Confirm that the identity appears in the permissions list
* Verify that the assigned permission reflects **ReadData (Viewer-level access)**

{% hint style="info" %}
The configured access is immediately visible in the permissions panel upon successful assignment.
{% endhint %}

### Permission Summary

<table><thead><tr><th width="188.09088134765625">Permission Type</th><th width="207.18182373046875">Access Level</th><th>Description</th></tr></thead><tbody><tr><td>ReadData</td><td>Viewer</td><td>Enables read-only SQL access to data</td></tr><tr><td>Metadata Access</td><td>Included</td><td>Allows visibility of schema and objects</td></tr><tr><td>Write Access</td><td>Not Allowed</td><td>Prevents data or structural modifications</td></tr></tbody></table>

### SQL Server Connector Setup

After configuring the required Fabric Warehouse access, establish the connection using the Microsoft SQL Server connector.

To establish the Microsoft SQL Server connector, click [here](https://docs.ovaledge.com/connectors/connector-repositories/rdbms/microsoft-sql-server).

This setup includes:

* Defining connection parameters (server, database, port)
* Selecting authentication method
* Configuring Credential Manager
* Validating connectivity

<figure><img src="https://1813356899-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhTnkoJQml0pok9awFDhx%2Fuploads%2F6cXu1fiDChz1kzbJjFr5%2Funknown.png?alt=media&amp;token=1263c035-f987-445a-a70b-abd1e724c32f" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Ensure that the SQL Analytics Endpoint is reachable and properly configured before initiating connection setup.
{% endhint %}

{% hint style="warning" %}

* Viewer-level access with **ReadData** is sufficient for metadata extraction and read-only operations.
* The identity used for the connection must have the required access to the target Fabric Warehouse.
* The SQL Analytics Endpoint must be reachable from the OvalEdge environment.
  {% endhint %}

***

Copyright © 2026, OvalEdge LLC, Peachtree Corners GA USA


---

# 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.ovaledge.com/release7.2/connectors/connector-repositories/rdbms/microsoft-sql-server/fabric-warehouse-lakehouse-integration.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.