<!-- Azure Data Lake -->
<!-- canonical: https://yres.eu/en/wiki/integraties/bronnen/azure-data-lake -->
# Azure Data Lake

**Category:** Azure · File

Azure Data Lake Storage Gen2 is an Azure Storage account with **hierarchical namespace** enabled. Within Yres, the Data Lake mainly serves as **storage for (raw) data**: alongside the database, Yres can optionally also land loaded data as **Parquet** in the Data Lake — since v1.56 as an append-only [change feed](https://yres.eu/en/wiki/concepten/lake-feed), holding only the mutated rows per run plus the framework columns `KeyHash`, `RowHash`, `YresAction` and `YresDateStart`. That enables a medallion architecture (bronze/silver/gold), including incremental updates of Delta tables.

:::note Connect via Azure Blob Storage
There is no separate **Azure Data Lake** choice in the "Add source" wizard (source picker `SourceField.tsx`). To **ingest data from a Data Lake (Gen2)**, add it as an **[Azure Blob Storage](https://yres.eu/en/wiki/integraties/bronnen/azure-blob-storage)** source. That creates an **`AzureBlobStorage`** linked service (SAS on the blob endpoint) — **not** `AzureBlobFS`; that type is reserved for the internal Data Lake datasets and SAP_BDC. In addition, Yres uses a fixed Data Lake linked service (`AzureDataLakeStorage.json`) internally as its **own staging/output storage** — the destination where Yres optionally writes Parquet.
:::

## Expected input

When the Data Lake is addressed as storage (internally, or via the SAP_BDC form), Yres uses an **`AzureBlobFS`** linked service with a **SAS URI** on the `dfs.core.windows.net` endpoint. If you connect a Data Lake as a **source** via Azure Blob Storage, an **`AzureBlobStorage`** linked service on the blob endpoint is created instead.

**Connection fields** (analogous to the SAS-based storage sources):

- **Storage account name** — the Azure Storage account with hierarchical namespace enabled.
- **Container / filesystem** — in ADLS Gen2 a container is also called a *filesystem*. You supply its name.
- **SAS token** — the token that grants access to the Data Lake.

**Authentication:** **SAS token** (no username/password). The full SAS URI is stored in **Azure Key Vault** and referenced by the linked service; the frontend never holds secrets.

**Integration runtime:** **cloud** — the default `AutoResolveIntegrationRuntime`. The `AzureBlobFS` template does not set `connectVia` and therefore runs on the cloud IR (just like Azure Blob Storage and SAP_BDC).

**Requirements:**

- An Azure Storage account with **hierarchical namespace** enabled (otherwise it is a regular Blob account, not Data Lake Gen2).
- A **SAS token** with at least read/list permissions on the container/filesystem.
- A Key Vault secret following the Yres naming convention `adf-{sourcename}-{suffix}` (the SAS URI comes from Key Vault at provisioning time, not from the frontend).

> Note: the values in the bundled `AzureDataLakeStorage.json` (account, host) are **example/seed data** for the dev factory, not customer-specific configuration. The *shape* of the linked service is what matters, not the hostnames.

## Where to find these

You retrieve the connection details from the same place as for Azure Blob Storage:

- **Storage account name** — in the [Azure Portal](https://portal.azure.com) → **Storage accounts** → the account with hierarchical namespace (visible under **Settings → Configuration → Hierarchical namespace: Enabled**).
- **Container / filesystem** — open the account → **Containers** blade; in ADLS Gen2 a container is also called a *filesystem*. Its name is what you supply.
- **SAS token** — create one via **Security + networking → Shared access signature** (Blob service + required permissions + expiry → **Generate SAS**). Save the token immediately: it is shown only once.

> Official documentation: [Introduction to Azure Data Lake Storage](https://learn.microsoft.com/en-us/azure/storage/blobs/data-lake-storage-introduction)

---

**See also:** [Azure Blob Storage](https://yres.eu/en/wiki/integraties/bronnen/azure-blob-storage) · [Integration catalog](https://yres.eu/en/wiki/integraties/catalogus) · [All data source requirements](https://yres.eu/en/wiki/referentie/databron-vereisten) · [Integrations — overview](https://yres.eu/en/wiki/integraties/overzicht)