> 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-data-lake-storage.md).
# Azure Data Lake Storage
Allows you to configure Azure Data Lake Storage as a destination for Inforiver writeback.
After navigating to the add destination page, log-in using your O365 credentials.
After successful log-in, the following details will have to be entered,
* Storage Account
* File System
* Directory
* Partition Required (Y/N)
* Writeback File Name
* Insert Variable
The writeback creates a Parquet file in the data lake storage.
Configure Azure Data Lake Storage destinations
**Storage Account:** Enter the name of the Azure Data Lake Storage account
**Partition Required:** If the Inforiver scenario is created and included in the writeback, and the user wants to writeback base and scenarios in separate parquet files, this is recommended.
**Insert Variables:** Writeback file name can be customized using variables such as Execution ID and date time related IDs.
**Security:** Please note Inforiver leverages Azure Access Control Lists (ACLs) while configuring Azure Data Lake Storage as a writeback destination. That means the user is only shown folders and directories that they have access to as per the defined ACL rules.
### Roles
Ensure that the user has the permissions listed below.
In Inforiver managed mode:
1. Read on the storage account
2. Read and Execute on the file system
Permissions
3. Read, Write, Execute on the folder where the file should be created.
Folder permissions
---
# 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/azure-data-lake-storage.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.
