> 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-sql.md). # Fabric SQL To add a Fabric SQL destination, you will need to enter the details listed below. * Server or host name * Port * Database * Schema Refer to the fields highlighted in the screenshot to get the host, port, database name, and schema name from the connection string.

Retrieving the host, port, database and schema

* Service principal client ID {% hint style="info" %} Ensure that this Service principal client ID has **Contributor** access to the workspace that is added. {% endhint %} * Service principal client secret Refer to the fields highlighted in the screenshot to get the Service principal client ID. The Client secret can be obtained while creating the service principal account.

* Tenant ID(from Microsoft Entra ID) Refer to the screenshots to get the tenant ID.

Configuration for adding a Fabric SQL writeback destination.

--- # 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-sql.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.