externaldata operator

The externaldata operator returns a table whose schema is defined in the query itself, and whose data is read from an external storage artifact, such as a blob in Azure Blob Storage or a file in Azure Data Lake Storage.


The externaldata operator supports a specific set of storage services, as listed under Storage connection strings.


The externaldata operator supports Shared Access Signature (SAS) key, Access key, and Microsoft Entra Token authentication methods. For more information, see Storage authentication methods.


Use the externaldata operator to retrieve small reference tables of up to 100 MB from an external storage artifact. The operator is not designed for large data volumes. To retrieve large volumes of external data, we recommend ingesting the external data into Log Analytics as custom logs. This operator isn't supported when the public endpoint of the storage artifact is behind a firewall.


externaldata (columnName:columnType [, ...] ) [ storageConnectionString [, ...] ] [with ( propertyName = propertyValue [, ...])]

Learn more about syntax conventions.


Name Type Required Description
columnName, columnType string ✔️ A list of column names and their types. This list defines the schema of the table.
storageConnectionString string ✔️ A storage connection string of the storage artifact to query.
propertyName, propertyValue string A list of optional supported properties that determines how to interpret the data retrieved from storage.

Supported properties

Property Type Description
format string The data format. If unspecified, an attempt is made to detect the data format from file extension. The default is CSV. All ingestion data formats are supported.
ignoreFirstRecord bool If set to true, the first record in every file is ignored. This property is useful when querying CSV files with headers.
ingestionMapping string Indicates how to map data from the source file to the actual columns in the operator result set. See data mappings.


This operator doesn't accept any pipeline input.

Standard query limits apply to external data queries as well.


The externaldata operator returns a data table of the given schema whose data was parsed from the specified storage artifact, indicated by the storage connection string.


Fetch a list of user IDs stored in Azure Blob Storage

The following example shows how to find all records in a table whose UserID column falls into a known set of IDs, held (one per line) in an external storage file. Since the data format isn't specified, the detected data format is TXT.

| where UserID in ((externaldata (UserID:string) [
      h@"?...SAS..." // Secret token needed to access the blob
| ...

Query multiple data files

The following example queries multiple data files stored in external storage.

externaldata(Timestamp:datetime, ProductId:string, ProductDescription:string)
| summarize count() by ProductId

The above example can be thought of as a quick way to query multiple data files without defining an external table.


Data partitioning isn't recognized by the externaldata operator.

Query hierarchical data formats

To query hierarchical data format, such as JSON, Parquet, Avro, or ORC, ingestionMapping must be specified in the operator properties. In this example, there's a JSON file stored in Azure Blob Storage with the following contents:

  "timestamp": "2019-01-01 10:00:00.238521",   
  "data": {    
    "tenant": "e1ef54a6-c6f2-4389-836e-d289b37bcfe0",   
    "method": "RefreshTableMetadata"   
  "timestamp": "2019-01-01 10:00:01.845423",   
  "data": {   
    "tenant": "9b49d0d7-b3e6-4467-bb35-fa420a25d324",   
    "method": "GetFileList"   

To query this file using the externaldata operator, a data mapping must be specified. The mapping dictates how to map JSON fields to the operator result set columns:

externaldata(Timestamp: datetime, TenantId: guid, MethodName: string)
with(format='multijson', ingestionMapping='[{"Column":"Timestamp","Properties":{"Path":"$.timestamp"}},{"Column":"TenantId","Properties":{"Path":"$.data.tenant"}},{"Column":"MethodName","Properties":{"Path":"$.data.method"}}]')

The MultiJSON format is used here because single JSON records are spanned into multiple lines.

For more info on mapping syntax, see data mappings.