Configuring an ADF Linked Service Connection for KQL Database (Fabric)
For information on how to enable a connection for use with linked services, see Configuring a Linked Service Connection.
Field labels in this walkthrough follow the underlying Azure Data Factory property names, with the connection column that carries each value named alongside. The exact labels shown in the BimlFlex Connection Editor may differ.
In a project configured for Microsoft Fabric, a connection enabled for linked services with the System Type KQL Database (Fabric) builds a KQL database linked service for the KQL database item, together with its table datasets, its copy sources and, at the landing stages, its copy sink.
The KQL Database (Fabric) System Type belongs to the Microsoft Fabric Connection Type.
The linked service takes its name from the connection's Catalog.
A KQL Database (Fabric) connection follows the Fabric build described in the Microsoft Fabric Configuration Overview. An Azure Data Factory project builds no linked service and no dataset for the connection.
After selecting KQL Database (Fabric) from the Linked Service Type dropdown, the form required for creating a KQL Database (Fabric) Linked Service will appear.
The option is offered on connections that use the KQL Database (Fabric) System Type.
Below the Connect via Integration Runtime control, the form shows a single Endpoint input and no sign in, credential, workspace or database fields.
Datasets, Sources and Sinks
A KQL Database (Fabric) connection serves the source system, the landing area and the persistent landing area stages.
As a source, the connection builds one KQL database table dataset for each source object. The dataset carries the source object's table.
The copy source reads the table whole. BimlFlex authors no source query for it.
The copy lands the data through the column mapping on the sink of the landing connection, a Lakehouse, Warehouse or KQL database sink.
As a landing area or persistent landing area, the connection is the target of the copy. BimlFlex builds one KQL database table dataset for the connection. The dataset carries no schema, and the Kusto table is named by the target object.
The copy sink writes to that table. It carries no pre copy script, since a KQL database has no truncate, so the copy appends to the table.
Complete Example
| Field | Example Value |
|---|---|
| Connect via Integration Runtime | AutoResolveIntegrationRuntime |
| External Reference | {KQL Database Item Id} |
| Endpoint | {KQL Database Query URI} |
Required Fields
The required fields for a KQL Database (Fabric) Linked Service connection are:
- Connect via Integration Runtime
- External Reference
- Endpoint (or the Query URI in the Connection String)
The Workspace Id comes from the FabricWorkspaceId setting rather than from a connection field.
Connect via Integration Runtime
Connect via Integration Runtime names the integration runtime for a KQL Database (Fabric) Linked Service connection.
The default value is AutoResolveIntegrationRuntime.
To use another runtime, select it from the dropdown or choose + New to add one.
When a custom value is saved in the linked service form, it will be added to the custom integration runtimes.
The custom values that appear in this dropdown can be maintained in Settings under Azure - AzureIntegrationRuntime.
Workspace Id
The Workspace Id identifies the Microsoft Fabric workspace that holds the KQL database.
It comes from the FabricWorkspaceId setting and maps to the Data Factory workspaceId property.
The connection carries no separate workspace field.
External Reference
The External Reference identifies the KQL database item within the workspace and holds the item id of the KQL database.
It is the connection's External Reference field, entered as described in External Reference, and maps to the Data Factory database property.
An External Reference is required on a connection that uses the KQL Database (Fabric) System Type.
Endpoint
The Endpoint is the Query URI of the KQL database and maps to the Data Factory endpoint property.
It is stored in the connection's LS_Endpoint column.
The field shows the sample https://<clusterId>.<zone>.kusto.fabric.microsoft.com.
When the Endpoint field is empty, BimlFlex takes the Query URI from the Data Source of the connection's Connection String.
Azure Data Factory Linked Service Additional Information
For additional information on the KQL Database connector and its connection requirements see the Microsoft Fabric KQL Database Connector documentation.