> 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/azure-sql-managed-db.md).

# Azure SQL (Managed DB)

Allows you to configure a writeback destination in Azure SQL Database that **exists inside & owned by Inforiver tenant**. Recommended for POC purposes only. Users who have difficulties in setting up a database within their tenant are welcome to use this feature to understand Inforiver's writeback functionalities and perform test writebacks for POC purposes.

<figure><img src="/files/G5DWDG2IGwU3EeLZB1gV" alt=""><figcaption><p>Terms of service while using Managed DB</p></figcaption></figure>

After navigating to the writeback destination, enter a name for the writeback table.&#x20;

<figure><img src="/files/5UCJRLsrRxFNg7WG82sr" alt=""><figcaption><p>Configuration for Inforiver managed Azure SQL</p></figcaption></figure>

After saving the destination, the credentials to access this database will appear on the screen.&#x20;

The user can use this information to access the database using SSMS, Azure Data Studio, or other similar applications. Please note, each table that is configured will have its unique login credentials.&#x20;


---

# 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/azure-sql-managed-db.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.