from azure.kusto.data import KustoClient, KustoConnectionStringBuilder
cluster = "<insert here your cluster name>"
client_id = "<insert here your AAD application id>"
client_secret = "<insert here your AAD application key>"
authority_id = "<insert here your AAD tenant id>"
kcsb = KustoConnectionStringBuilder.with_aad_application_key_authentication(cluster, client_id, client_secret, authority_id)
# It is a good practice to re-use the KustoClient instance, as it maintains a pool of connections to the Kusto service.
# This sample shows how to create a client and close it in the same scope, for demonstration purposes.
with KustoClient(kcsb) as client:
db = "Samples"
query = "StormEvents | take 10"
response = client.execute(db, query)
for row in response.primary_results[0]:
print(row[0], " ", row["EventType"])Kusto Python Client Library provides the capability to query Kusto clusters using Python. It is Python 3.x compatible and supports all data types through familiar Python DB API interface.
It’s possible to use the library, for instance, from Jupyter Notebooks. which are attached to Spark clusters, including, but not exclusively, Azure Databricks. instances.
Async Client
Kusto now provides an asynchronous client for queries.
To use the client, first install the package with the “aio” extra:
pip install azure-kusto-data[aio]The async client uses exact same interface as the regular client, except that it lives in the azure.kusto.data.aio namespace, and it returns Futures you will need to await its
from azure.kusto.data import KustoConnectionStringBuilder
from azure.kusto.data.aio import KustoClient
cluster = "<insert here your cluster name>"
client_id = "<insert here your AAD application id>"
client_secret = "<insert here your AAD application key>"
authority_id = "<insert here your AAD tenant id>"
async def sample():
kcsb = KustoConnectionStringBuilder.with_aad_application_key_authentication(cluster, client_id, client_secret, authority_id)
async with KustoClient(kcsb) as client:
db = "Samples"
query = "StormEvents | take 10"
response = await client.execute(db, query)
for row in response.primary_results[0]:
print(row[0], " ", row["EventType"])Links
4 maintainers
Release files for azure-kusto-data 6.0.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| azure_kusto_data-6.0.4.tar.gz | 39.7 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| azure_kusto_data-6.0.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size:91.3 kB
Release files / azure_kusto_data-6.0.4.tar.gz
| Download URL | azure_kusto_data-6.0.4.tar.gz |
|---|---|
| Size | 39.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
409e2e14aec6dfbedc9d5bb03e1440dabbc252b10fd03437bc523f29dbda4710
|
|
BLAKE2b-256 checksum How to use checksums |
778bfea5daa608c7995ec662473ab76306965cc01c68dd3a958e779dd270d523
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.8
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 6, 2026.
Transparency logRelease files / azure_kusto_data-6.0.4-py3-none-any.whl
| Download URL | azure_kusto_data-6.0.4-py3-none-any.whl |
|---|---|
| Size | 51.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7dad0628ccd47e5dd0692b41ebaaa878db28f9711435063d7c51cec7e3857307
|
|
BLAKE2b-256 checksum How to use checksums |
a804096484b34efd3738938db75b38e0055675453b1e0d47a11c27c1446a3b10
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.8
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 6, 2026.
Transparency log
