AzureDataExplorerHook

Microsoft Azure

Interacts with Azure Data Explorer (Kusto).

View Source

Last Updated: Apr. 16, 2021

Access Instructions

Install the Microsoft Azure provider package into your Airflow environment.

Import the module into your DAG file and instantiate it with your desired params.

Parameters

azure_data_explorer_conn_idstrReference to the Azure Data Explorer connection.

Documentation

Interacts with Azure Data Explorer (Kusto).

Extra JSON field contains the following parameters:

{ "tenant": "<Tenant ID>", "auth_method": "<Authentication method>", "certificate": "<Application PEM certificate>", "thumbprint": "<Application certificate thumbprint>" }

Cluster:

Azure Data Explorer cluster is specified by a URL, for example: “https://help.kusto.windows.net”. The parameter must be provided through Host connection detail.

Tenant ID:

To learn about tenants refer to: https://docs.microsoft.com/en-us/onedrive/find-your-office-365-tenant-id

Authentication methods:

Authentication method must be provided through “auth_method” extra parameter. Available authentication methods are:

  • AAD_APPAuthentication with AAD application certificate. Extra parameters:

    “tenant” is required when using this method. Provide application ID and application key through username and password parameters.

  • AAD_APP_CERT: Authentication with AAD application certificate. Extra parameters:

    “tenant”, “certificate” and “thumbprint” are required when using this method.

  • AAD_CREDSAuthentication with AAD username and password. Extra parameters:

    “tenant” is required when using this method. Username and password parameters are used for authentication with AAD.

  • AAD_DEVICEAuthenticate with AAD device code. Please note that if you choose

    this option, you’ll need to authenticate for every new instance that is initialized. It is highly recommended to create one instance and use it for all queries.

Example DAGs

Improve this module by creating an example DAG.

View Source
  1. Add an `example_dags` directory to the top-level source of the provider package with an empty `__init__.py` file.
  2. Add your DAG to this directory. Be sure to include a well-written and descriptive docstring
  3. Create a pull request against the source code. Once the package gets released, your DAG will show up on the Registry.

Was this page helpful?