> For the complete documentation index, see [llms.txt](https://docs.inforiver.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.inforiver.com/working-with-inforiver/12.-data-writeback/destinations/fabric-warehouse.md).

# Fabric Warehouse

After navigating to the add destination page, the following details are required to add **Fabric Warehouse** as a writeback destination:

* SQL connection string
* Database name
* Schema name
* Client ID
* Client secret
* Table name

<figure><img src="/files/HPra3iudiJTMAvG5qojP" alt=""><figcaption><p>Fabric warehouse</p></figcaption></figure>

#### Fetching the DB name and connection string

<figure><img src="/files/V1FuY9q30IccHoyI8UDf" alt=""><figcaption><p>DB name and connection string</p></figcaption></figure>

#### Fetching the Service Principal Client ID and Service Principal Client Secret

Refer to the highlighted fields in the screenshot below to get the Service Principal Client ID. Client Secret is obtained while creating the Service Principal Account.

{% hint style="info" %}
Ensure that this Service principal client ID has **Contributor** access to the workspace that is added.
{% endhint %}

<figure><img src="/files/ytnrH3N8tbICsVOqWzpN" alt=""><figcaption><p>Fetching the service principal client ID</p></figcaption></figure>

#### Additional configuration for optimised insert

To perform bulk insert when there is large data, ensure these items are configured:

1\. Create a **"Workspace Identity"** and then add the **"Service Principal"** as an **"Authorized User"**.

<figure><img src="/files/23j2qoNvZjEESQM42XpF" alt=""><figcaption></figcaption></figure>

2\. Ensure that the **"Workspace Identity"** is whitelisted in the **"Resource Instance Rules"** of th&#x65;**"Storage Account"**.

<figure><img src="/files/qugD8zUxLkdbO7OAsmSA" alt=""><figcaption></figcaption></figure>


---

# 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.inforiver.com/working-with-inforiver/12.-data-writeback/destinations/fabric-warehouse.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.