> For the complete documentation index, see [llms.txt](https://docs.secoda.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.secoda.co/integrations/data-lakes/azure-data-lake/adl-metadata-extracted.md).

# ADL Metadata Extracted

List of all the metadata that Secoda pulls from Azure Data Lake

### Supported file formats

Extraction of metadata is only supported for the following file formats:

```
CSV (*.csv)
TSV (*.tsv)
JSON (*.json)
JSONL (*.jsonl)
Parquet (*.parquet)
Apache Avro (*.avro)
```

### What does Secoda extract from Azure Data Lake?

Database (Storage Account containers are referred to as databases in Secoda)

* Name

Schema (Directories within a container are referred to as schemas in Secoda)

* Name

Table (Files are referred to as tables in Secoda)

* Name
* File format type (Parquet, CSV, JSON, etc.)

Columns (Fields in files are referred to as columns in Secoda)

* Name
* Data type

### Important Notes

* Secoda will extract metadata from the most recent version of files when multiple versions exist
* The integration supports up to 100,000 files per container extraction limit


---

# 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.secoda.co/integrations/data-lakes/azure-data-lake/adl-metadata-extracted.md?ask=<question>&goal=<user_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.