---
title: azure_table_storage
page-cloud: true
latest-operator-version: v26.2.6
latest-console-tag: v3.14.0
latest-connect-version: 4.118.0
latest-redpanda-tag: v26.2.7
docname: connect/components/outputs/azure_table_storage
page-component-name: cloud-data-platform
page-version: master
page-component-version: master
page-component-title: Cloud
page-relative-src-path: connect/components/outputs/azure_table_storage.adoc
page-edit-url: https://github.com/redpanda-data/cloud-docs/edit/main/modules/develop/pages/connect/components/outputs/azure_table_storage.adoc
description: Stores messages in an Azure Table Storage table.
page-context-switcher:
  - name: Output
    to: /cloud-data-platform/develop/connect/components/outputs/azure_table_storage/
  - name: Input
    to: /cloud-data-platform/develop/connect/components/inputs/azure_table_storage/
page-self-managed-available: "true"
page-self-managed-available-url: https://docs.redpanda.com/connect/components/outputs/azure_table_storage/
page-git-created-date: "2024-09-09"
page-git-modified-date: "2026-10-19"
page-generated-sources:
  - include: connect:components:partial$descriptions/outputs/azure_table_storage.adoc
    generator: null
    version: null
    source: the component specs in https://github.com/redpanda-data/connect
page-generated-content: partial
---

# azure_table_storage

> For the complete documentation index, see [llms.txt](https://docs.redpanda.com/llms.txt). Component-specific: [cloud-data-platform-full.txt](https://docs.redpanda.com/cloud-data-platform-full.txt)

<!-- Source: https://docs.redpanda.com/cloud-data-platform/develop/connect/components/outputs/azure_table_storage.md -->

Stores messages in an Azure Table Storage table.

Only one authentication method is required, `storage_connection_string` or `storage_account` and `storage_access_key`. If both are set then the `storage_connection_string` is given priority.

In order to set the `table_name`, `partition_key` and `row_key` you can use function interpolations described [here](https://docs.redpanda.com/cloud-data-platform/develop/connect/configuration/interpolation/#bloblang-queries), which are calculated per message of a batch.

If the `properties` are not set in the config, all the `json` fields are marshalled and stored in the table, which will be created if it does not exist.

The `object` and `array` fields are marshaled as strings. For example:

The JSON message:

```json
{
  "foo": 55,
  "bar": {
    "baz": "a",
    "bez": "b"
  },
  "diz": ["a", "b"]
}
```

Will store in the table the following properties:

```yml
foo: '55'
bar: '{ "baz": "a", "bez": "b" }'
diz: '["a", "b"]'
```

It’s also possible to use function interpolations to get or transform the properties values. For example:

```yml
properties:
  device: '${! json("device") }'
  timestamp: '${! json("timestamp") }'
```

## Performance

This output benefits from sending multiple messages in flight in parallel for improved performance. You can tune the max number of in flight messages (or message batches) with the field `max_in_flight`.

This output benefits from sending messages as a batch for improved performance. Batches can be formed at both the input and output level. You can find out more [in this doc](https://docs.redpanda.com/cloud-data-platform/develop/connect/configuration/batching/).

### Common

```yml
output:
  label: ""
  azure_table_storage:
    storage_account: ""
    storage_access_key: ""
    storage_connection_string: ""
    storage_sas_token: ""
    table_name: "" # No default (required)
    partition_key: ""
    row_key: ""
    properties: {}
    max_in_flight: 64
    batching:
      count: 0
      byte_size: 0
      period: ""
      check: ""
```

### Advanced

```yml
output:
  label: ""
  azure_table_storage:
    storage_account: ""
    storage_access_key: ""
    storage_connection_string: ""
    storage_sas_token: ""
    table_name: "" # No default (required)
    partition_key: ""
    row_key: ""
    properties: {}
    transaction_type: INSERT
    max_in_flight: 64
    timeout: 5s
    batching:
      count: 0
      byte_size: 0
      period: ""
      check: ""
      processors: [] # No default (optional)
```

## Fields

### `batching`

Configure a [batching policy](https://docs.redpanda.com/cloud-data-platform/develop/connect/configuration/batching/).

**Type**: `object`

```yaml
# Examples:
batching:
  byte_size: 5000
  count: 0
  period: 1s

# ---

batching:
  count: 10
  period: 1s

# ---

batching:
  check: this.contains("END BATCH")
  count: 0
  period: 1m
```

### `batching.byte_size`

The maximum total size (in bytes) that a batch can reach before it is flushed. When the combined size of all messages in the batch reaches or exceeds this limit, the batch is immediately sent to the next stage (such as a processor or output).

Set to `0` to disable size-based batching. When disabled, messages are flushed based on other conditions (such as `count` or `period`).

**Type**: `int`

**Default**: `0`

### `batching.check`

A [Bloblang query](https://docs.redpanda.com/cloud-data-platform/develop/connect/guides/bloblang/about/) that returns a boolean value indicating whether a message should end a batch.

**Type**: `string`

**Default**: `""`

```yaml
# Examples:
check: this.type == "end_of_transaction"
```

### `batching.count`

The number of messages at which the batch is flushed. Set to `0` to disable count-based batching.

**Type**: `int`

**Default**: `0`

### `batching.period`

The length of time after which an incomplete batch is flushed regardless of its size. This field accepts Go duration format strings such as `100ms`, `1s`, or `5s`. Supported time units are `ns`, `us`, `ms`, `s`, `m`, and `h`.

**Type**: `string`

**Default**: `""`

```yaml
# Examples:
period: 1s

# ---

period: 1m

# ---

period: 500ms
```

### `batching.processors[]`

A list of [processors](https://docs.redpanda.com/cloud-data-platform/develop/connect/components/processors/about/) to apply to a batch as it is flushed. This allows you to aggregate and archive the batch however you see fit. All resulting messages are flushed as a single batch, so splitting the batch into smaller batches with these processors has no effect.

**Type**: `array<processor>`

```yaml
# Examples:
processors:
  - archive:
      format: concatenate


# ---

processors:
  - archive:
      format: lines


# ---

processors:
  - archive:
      format: json_array
```

### `max_in_flight`

The maximum number of parallel message batches to have in flight at any given time.

**Type**: `int`

**Default**: `64`

### `partition_key`

The partition key.

This field supports [interpolation functions](https://docs.redpanda.com/cloud-data-platform/develop/connect/configuration/interpolation/#bloblang-queries).

**Type**: `string`

**Default**: `""`

```yaml
# Examples:
partition_key: ${! json("date") }
```

### `properties`

A map of properties to store into the table.

This field supports [interpolation functions](https://docs.redpanda.com/cloud-data-platform/develop/connect/configuration/interpolation/#bloblang-queries).

**Type**: `object<string>`

**Default**: `{}`

### `row_key`

The row key.

This field supports [interpolation functions](https://docs.redpanda.com/cloud-data-platform/develop/connect/configuration/interpolation/#bloblang-queries).

**Type**: `string`

**Default**: `""`

```yaml
# Examples:
row_key: ${! json("device")}-${!uuid_v4() }
```

### `storage_access_key`

The access key for the storage account. Use this field along with `storage_account` for authentication. This field is ignored when the `storage_connection_string` field is populated.

**Type**: `string`

**Default**: `""`

### `storage_account`

The storage account to access. This field is ignored when the `storage_connection_string` field is populated, unless the connection string does not contain the `AccountName` parameter.

**Type**: `string`

**Default**: `""`

### `storage_connection_string`

The connection string for the storage account. This field is required if `storage_account` is not set.

> 📝 **NOTE**
>
> If the `storage_connection_string` field does not contain the `AccountName` parameter value, specify it in the `storage_account` field.

**Type**: `string`

**Default**: `""`

### `storage_sas_token`

The SAS token for the storage account. Use this field along with `storage_account` for authentication. This field is ignored when either the `storage_connection_string` or `storage_access_key` fields are populated.

**Type**: `string`

**Default**: `""`

### `table_name`

The table to store messages into.

This field supports [interpolation functions](https://docs.redpanda.com/cloud-data-platform/develop/connect/configuration/interpolation/#bloblang-queries).

**Type**: `string`

```yaml
# Examples:
table_name: ${! meta("kafka_topic") }

# ---

table_name: ${! json("table") }
```

### `timeout`

This field has no effect. The output parses the value but does not apply it to write requests.

**Type**: `string`

**Default**: `5s`

### `transaction_type`

Type of transaction operation.

This field supports [interpolation functions](https://docs.redpanda.com/cloud-data-platform/develop/connect/configuration/interpolation/#bloblang-queries).

**Type**: `string`

**Default**: `INSERT`

**Options**: `INSERT`, `INSERT_MERGE`, `INSERT_REPLACE`, `UPDATE_MERGE`, `UPDATE_REPLACE`, `DELETE`

```yaml
# Examples:
transaction_type: ${! json("operation") }

# ---

transaction_type: ${! meta("operation") }

# ---

transaction_type: INSERT
```