Skip to main content
Technical Preview

Overview

A client-mode connector for a curated slice of the Kusto REST API used by Azure Data Explorer and Microsoft Fabric Eventhouse: Default BASE_ADDRESS is https://YOUR_CLUSTER.YOUR_REGION.kusto.windows.net (no trailing slash). For Fabric, use the Eventhouse Query URI. Topics use data/azure-data-explorer/<verb>. See the base guide: REST API Connectors.
Auth: Authorization: Bearer &lt;entra_access_token&gt;. Prefer Hub secrets (GET SECRET "ADX_ACCESS_TOKEN" or "KUSTO_ACCESS_TOKEN"). Token resource is typically https://api.kusto.windows.net or the cluster URI.
Streaming vs queued ingest: /v1/rest/ingest/... streaming ingest uses the engine host (same as query). The portal Data ingestion URI (ingest-*) is for queued/bulk pipelines and is not the BASE_ADDRESS for this template.
Factory live smoke is blocked until an Entra Bearer token + cluster/Eventhouse URI are available. Public help.kusto.windows.net returns 401 without auth (host reachable).

Basic Syntax

Full template (query v2, GET query, client-request-id headers): see the package AzureDataExplorerRestApi.lot under the broker templates tree after you push feat/rest-api-route-azure-data-explorer-and-fabric-eventhouse.

Auth and placeholders

Template reference

Generated from the shipped broker template azure-data-explorer-and-fabric-eventhouse (-routeCode AZURE_DATA_EXPLORER_AND_FABRIC_EVENTHOUSE). It lists every event the template defines.

Auth

Authorization: Bearer {value.json.access_token} (Microsoft Entra ID OAuth 2.0). Prefer GET SECRET ADX_ACCESS_TOKEN or KUSTO_ACCESS_TOKEN. Token resource typically https://api.kusto.windows.net or the cluster URI. Never commit real credentials. Auth headers used by the template: Authorization: Bearer {value.json.access_token}.

Template parameters

BASE_ADDRESS default: https://YOUR_CLUSTER.YOUR_REGION.kusto.windows.net.

Events

Deploy

Get the template card (JSON with template and metadata) from the broker, then deploy the connector:
The deployable connector from the REST API app, with BASE_ADDRESS already filled in:
Deploy it with -addRoute (do not include ADD METADATA).

Usage example

Call PostQuery by publishing a JSON payload to its request topic, and read the reply on the response topic:
Last modified on October 21, 2026