Ready to get started?

Learn more or sign up for a free trial:

CData Connect Server

Import Azure Data Lake Storage Data into Microsoft Power Query



The CData Connect Server offers standards-based Web service endpoints that allow a variety of applications to access Azure Data Lake Storage data. In this article, you will use the OData format to import Azure Data Lake Storage data into Microsoft Power Query.

The Connect Server enables you to use Web services to connect to and query Azure Data Lake Storage data. This article details how to import an OData feed of Azure Data Lake Storage data into Microsoft Power Query.

Connect to Azure Data Lake Storage from Power Query

To work with live Azure Data Lake Storage data in Microsoft Power Query, we need to connect to Azure Data Lake Storage from Connect Server, provide user access to the new virtual database, and create OData endpoints for the Azure Data Lake Storage data.

Add a Connect Server User

Create a User to connect to Azure Data Lake Storage from Microsoft Power Query through Connect Server.

  1. Click Users -> Add
  2. Configure a User
  3. Click Save Changes and make note of the Authtoken for the new user

Connect to Azure Data Lake Storage from Connect Server

CData Connect Server uses a straightforward, point-and-click interface to connect to data sources and generate APIs.

  1. Open Connect Server and click Connections
  2. Select "Azure Data Lake Storage" from Available Data Sources
  3. Enter the necessary authentication properties to connect to Azure Data Lake Storage.

    Authenticating to a Gen 1 DataLakeStore Account

    Gen 1 uses OAuth 2.0 in Azure AD for authentication.

    For this, an Active Directory web application is required. You can create one as follows:

    1. Sign in to your Azure Account through the .
    2. Select "Azure Active Directory".
    3. Select "App registrations".
    4. Select "New application registration".
    5. Provide a name and URL for the application. Select Web app for the type of application you want to create.
    6. Select "Required permissions" and change the required permissions for this app. At a minimum, "Azure Data Lake" and "Windows Azure Service Management API" are required.
    7. Select "Key" and generate a new key. Add a description, a duration, and take note of the generated key. You won't be able to see it again.

    To authenticate against a Gen 1 DataLakeStore account, the following properties are required:

    • Schema: Set this to ADLSGen1.
    • Account: Set this to the name of the account.
    • OAuthClientId: Set this to the application Id of the app you created.
    • OAuthClientSecret: Set this to the key generated for the app you created.
    • TenantId: Set this to the tenant Id. See the property for more information on how to acquire this.
    • Directory: Set this to the path which will be used to store the replicated file. If not specified, the root directory will be used.

    Authenticating to a Gen 2 DataLakeStore Account

    To authenticate against a Gen 2 DataLakeStore account, the following properties are required:

    • Schema: Set this to ADLSGen2.
    • Account: Set this to the name of the account.
    • FileSystem: Set this to the file system which will be used for this account.
    • AccessKey: Set this to the access key which will be used to authenticate the calls to the API. See the property for more information on how to acquire this.
    • Directory: Set this to the path which will be used to store the replicated file. If not specified, the root directory will be used.
  4. Click Save Changes
  5. Click Privileges -> Add and add the new user (or an existing user) with the appropriate permissions (SELECT is all that is required for Reveal).

Add Azure Data Lake Storage OData Endpoints in Connect Server

After connecting to Azure Data Lake Storage, create OData Endpoints for the desired table(s).

  1. Click OData -> Tables -> Add Tables
  2. Select the Azure Data Lake Storage database
  3. Select the table(s) you wish to work with and click Next
  4. (Optional) Edit the resource to select specific fields and more
  5. Save the settings

(Optional) Configure Cross-Origin Resource Sharing (CORS)

When accessing and connecting to multiple domains from an application such as Ajax, there is a possibility of violating the limitations of cross-site scripting. In that case, configure the CORS settings in OData -> Settings.

  • Enable cross-origin resource sharing (CORS): ON
  • Allow all domains without '*': ON
  • Access-Control-Allow-Methods: GET, PUT, POST, OPTIONS
  • Access-Control-Allow-Headers: Authorization

Save the changes to the settings.

Connect to Azure Data Lake Storage Data from Power Query

Follow the steps below to import tables that can be refreshed on demand:

  1. Configure the Connect Server to use a version of the OData protocol that is recognized by Power Query. In the Connect Server administration console, click Settings -> Server and change the value of the Default Version property to 3.0.
  2. From the ribbon in Excel, click Power Query -> From Other Data Sources -> From OData Feed, and enter the OData URL:

    https://your-server:8032/api.rsc
  3. Next, define authentication credentials and set privacy levels. Select Basic authentication and enter the credentials for a user authorized to make requests. Specify the Username field and enter the user's authtoken in the Password field.

    To change the authentication scheme that Power Query will use, click Power Query -> Data Source Settings. Select the OData feed from the list and then click "Edit Permissions..." Select the privacy level from the menu.

  4. You can now access Azure Data Lake Storage data in Power Query. In the Navigator expand the node for the OData feed, right-click a table, and click Edit to open the Query Editor. This will display the table data.

Free Trial & More Information

If you are interested in connecting to your Azure Data Lake Storage data (or data from any of our other supported data sources) from Power Query, sign up for a free trial of CData Connect Server today! For more information on Connect Server and to see what other data sources we support, refer to our CData Connect page.