Type to search.

Azure Blob Storage connector

Serverless Preview

Elastic Cloud Serverless projects are autoscaled environments, fully managed by Elastic and available on Elastic Cloud.

Availability

  • Preview

    This functionality is in technical preview and is ready for evaluation. Use with caution in production; it is not recommended for mission-critical workloads. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features. Specific Support terms apply.

Serverless interfaces and procedures might differ from classic Elastic Stack deployments.

Stack Preview 9.4+

The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats.

Availability

  • Preview since 9.4

    This functionality is in technical preview and is ready for evaluation. Use with caution in production; it is not recommended for mission-critical workloads. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features. Specific Support terms apply.

Unless stated otherwise on the page, this functionality is available when your Elastic Stack is deployed on Elastic Cloud Hosted, Elastic Cloud Enterprise, Elastic Cloud on Kubernetes, and self-managed environments.

This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.

The Azure Blob Storage connector integrates with Azure Blob Storage using the Blob Service REST API. It supports listing containers, listing blobs, retrieving blob content, and getting blob properties. Use it as a data source for federated search.

You can use this connector in Agent Builder and Workflows.

You can create connectors in Stack Management > Connectors.

Azure Blob Storage connectors have the following configuration properties:

Storage account URL
The blob service endpoint for your storage account (for example, https://myaccount.blob.core.windows.net). Find this in the Azure Portal under your storage account Endpoints.
Storage account name and key (Shared Key)
The connector uses Shared Key authentication. Provide your storage account name and one of its account keys (from Azure Portal → Storage account → Access keys). The connector signs each request with HMAC-SHA256 per the Azure REST API. When creating a connector via the data source API, credentials must be in the form accountName:accountKey (one line, first colon separates name from key; the key is base64 and must not contain colons). See Get API credentials.

You can test connectors as you're creating or editing the connector in Kibana. The test verifies connectivity by calling the List Containers API with maxresults=1.

The Azure Blob Storage connector has the following actions:

List containers

List containers in the storage account.

  • prefix (optional): Filter containers by name prefix.
  • maxresults (optional): Maximum number of containers to return.
  • marker (optional): Continuation token for pagination.
List blobs

List blobs in a container.

  • container (required): Container name.
  • prefix (optional): Filter blobs by name prefix.
  • maxresults (optional): Maximum number of blobs to return.
  • marker (optional): Continuation token for pagination.
Get blob

Download blob content and metadata. Returns base64-encoded content plus content-type and content-length.

  • container (required): Container name.
  • blobName (required): Blob name (path).
Get blob properties

Return blob system properties (content-type, content-length, last-modified, etag) without downloading the blob body.

  • container (required): Container name.
  • blobName (required): Blob name (path).

The connector uses Shared Key (storage account key) authentication.

  1. In the Azure Portal, open your storage account.
  2. Go to Security + networking → Access keys (or Storage account → Access keys).
  3. Copy the Storage account name (for example, myaccount) and one of the Key values (key1 or key2). The key is a base64-encoded string.
  4. When creating the connector from the UI, enter the account name and key in the configured fields. When using the data source creation API, pass credentials as a single string in the form accountName:accountKey (for example, myaccount:base64key...); the first colon separates the name from the key, so the key itself must not contain colons.

For details, see Authorize with Shared Key.