> 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-lakehouse.md).
# Fabric Lakehouse
To add a Fabric Lakehouse destination, you need to sign in with Microsoft Office 365 credentials first. After signing in, you will be able to see the list of workspaces and lakehouses that you have access to.
Add Fabric Lakehouse destination
1. Select the required workspace and the Lakehouse.
2. Enter the table name.
3. When writeback is initiated, the delta CSV file is uploaded and the writeback table is created automatically at the specified destination.
Data writeback completed in lakehouse destination
{% hint style="info" %}
The Lakehouse.ReadWrite.All permission needs to be provided to configure lakehouse destinations.
{% endhint %}
To connect to Fabric Lakehouse, perform the following steps:
1. Please ensure that an active Azure subscription is available to connect to Fabric Lakehouse.
2. Please ensure that the Azure subscription is active and associated with the same Entra ID tenant.
3. Please ensure that the **'Microsoft.DataLakeStore'** and **'Microsoft.Storage'** Resource providers are registered in the Azure subscription.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.inforiver.com/working-with-inforiver/12.-data-writeback/destinations/fabric-lakehouse.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
