---
schema_version: "1"
id: 1f1b16065fef347fbdf79c3405c9a6a390505cd7c7867686c966d57072a16e11
title: Azure Data Lake Storage Connector
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/azure-data-lake-storage-connector/latest/index.md
canonical_url: https://docs.mulesoft.com/azure-data-lake-storage-connector/latest/
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 615333e9daea091eb7814ae9b781a0a9ae6a377a65e945480d0c7a162a8d2229
description: MuleSoft Documentation Site
release: "1.0"
latest: true
---
---
product: Azure Data Lake Storage Connector
version: 1.0
is-latest-version: true
---

# Azure Data Lake Storage Connector

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

Anypoint Connector for Azure Data Lake Storage Gen 2 (Azure Data Lake Storage Connector) provides
access to standard Azure Data Lake Storage Gen 2 operations using Anypoint Platform.

Azure Data Lake Storage Gen2 is a scalable data storage service built by Microsoft Azure and
designed for big data analytics. Azure Data Lake Storage Gen2 is built on top of Azure Blob Storage
and provides the data organization and security semantics of Azure Data Lake Gen1 along with the
cost and reliability benefits of Azure Blob Storage.

For information about compatibility and fixed issues, see the Azure Data Lake Storage Connector
Release Notes.

## Before You Begin

To use this connector, you must be familiar with:

- Azure Data Lake Storage Gen2 API

- Anypoint Connectors

- Mule runtime engine (Mule)

- Elements and global elements in a Mule flow

- How to create a Mule app using Anypoint Studio

Before creating an app, you must have access to:

- The Azure Data Lake Storage target resource

- Anypoint Platform

- Anypoint Studio version 7.1 or later

## Common Use Cases for the Connector

Common use cases for Azure Data Lake Storage Connector include the following:

- Create, read, update, and delete files in an existing Azure Data Lake Storage file system.

- Create, rename, and delete directories from the Azure Data Lake Storage file system.

- Rename existing files.

- Append the contents of a file and flush the file’s contents.

- Obtain properties and status for a file or directory.

- Obtain the ACL (access control list) of a file or directory.

- Get a list of all the available paths in the Azure Data Lake Storage file system.

For examples of some of these common use cases, see [Examples](https://docs.mulesoft.com/azure-data-lake-storage-connector/latest/azure-data-lake-connector-examples).

## Audience

- New users, read:

  - [Studio Configuration](https://docs.mulesoft.com/azure-data-lake-storage-connector/latest/azure-data-lake-connector-studio)

  - [Examples](https://docs.mulesoft.com/azure-data-lake-storage-connector/latest/azure-data-lake-connector-examples), with use case information for the connector

- Advanced users, read:

  - [XML and Maven Support](https://docs.mulesoft.com/azure-data-lake-storage-connector/latest/azure-data-lake-connector-xml-maven)

  - [Examples](https://docs.mulesoft.com/azure-data-lake-storage-connector/latest/azure-data-lake-connector-examples), with use case information for the connector

## Connection Types

Azure Data Lake Storage Connector connections use the following authentication types:

- Azure Active Directory OAuth 2.0  
  Delegates user authentication to the service hosting the user account

- Shared Access Signature  
  Uses information contained in the SAS token to authorize the client request

- Shared Key Connection  
  Uses a shared access key that is generated by Azure and used for the storage account

## Japanese Character Support

Azure Data Lake Storage Connector supports Japanese characters for path names. If you use Japanese
characters in path names, you must encode the Japanese characters into valid UTF-8 encoded and
escaped URI characters. DataWeave 2.0 provides a function to encode Japanese characters. See
[encodeURI(String)](https://docs.mulesoft.com/dataweave/latest/dataweave-formats-urlencoded)

File content operation payloads, such as adding content to a file, also support Japanese characters,
and do not require any encoding.

This connector does not support Japanese for Azure Data Lake Storage file system names, as this is
not supported by Azure Data Lake Storage itself.

## Next Step

After you complete the prerequisites, you are ready to create an app and configure the connector
using [Anypoint Studio](https://docs.mulesoft.com/azure-data-lake-storage-connector/latest/azure-data-lake-connector-studio).

## See Also

- [Introduction to Anypoint Connectors](https://docs.mulesoft.com/connectors/introduction/introduction-to-anypoint-connectors)

- [Use Exchange to Discover Connectors, Templates, and Examples](https://docs.mulesoft.com/connectors/introduction/intro-use-exchange)

- [Azure Data Lake Storage Connector Reference](https://docs.mulesoft.com/azure-data-lake-storage-connector/latest/azure-data-lake-connector-reference)

- [Salesforce Help](https://help.salesforce.com)