Skip to main content
Use the @bijection/connectors/azure-table entrypoint to declare Azure Table Storage resources.

​
Availability

This page describes the pinned source package. Published availability is unestablished for this artifact. Source build and package availability.

​
Resources and modes

Declare a resource in application code, then bind deployment-specific settings and credentials. See typed resources, connections and source inspection.

​
Table

​
window: Timestamp windows walked through continuation headers

The following example matches configuration standard.

​
Configuration: standard

Case: azure-table/table/window/standard. Connection and resource configuration are declared by this exact case. Credential kind: azure-table. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: records
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

​
Provider guidance

Compiled declaration examples and configuration details are published in the connector reference. Bind the table service endpoint (url, such as https://<account>.table.core.windows.net) on the connection and the table name (table) on the resource.
  • Mechanism. GET /{table}()?$filter=...&$top=1000 with Accept: application/json;odata=fullmetadata and x-ms-version: 2019-02-02. A pass fixes one window Timestamp ge <start> and Timestamp lt <end>, where end is the instant the pass began minus settleMs (default one minute, declared as the contract’s observation lag).
  • Why a window walked to its end. The service answers a Timestamp filter in PartitionKey/RowKey order, so a page’s largest Timestamp is no continuation. The pass follows x-ms-continuation-NextPartitionKey and x-ms-continuation-NextRowKey, repeating the same filter with NextPartitionKey and NextRowKey, until a page states neither. Short and empty pages with a continuation (the five-second and partition-boundary stops) continue. Half a continuation, or one repeated unchanged, is refused. The window and both tokens are the engine-owned scan position.
  • Carried position. The page that ends the walk names end as the collection’s carried position (sync.carry). The next pass reads from it, so consecutive windows meet exactly. A pass that fails or leaves a gap hands nothing on and its window is read again.
  • Identity and version. PartitionKey plus RowKey; the entity’s odata.etag, which the service states per entity only in full metadata. Published values also carry PartitionKey, RowKey, Timestamp, _key (the JSON pair) and _etag. Int64, Guid, DateTime and Binary properties arrive as strings.
  • Credentials. azureTable.credential(name) holding an oauth_client_credentials envelope: the Microsoft Entra ID token endpoint https://login.microsoftonline.com/<tenant>/oauth2/v2.0/token, the client id and secret, scope: "https://storage.azure.com/.default" and the table endpoint origin in allowed_resource_origins. The application needs a data role such as Storage Table Data Reader. Shared Key and SAS are not supported: the native credential owner neither signs requests with an account key nor appends SAS query parameters.
  • Limits. Deletions are not observed and no coverage is claimed. A write that commits with a Timestamp older than the settle window allows is never read; the window is a declared bound, not a proof. An entity changed during a walk is read in a later window at its newer version.
Not established: no request has reached a storage account or Azurite. The continuation behaviour, the full-metadata ETag and the acceptance of the host’s form-encoded $filter are taken from documentation.

​
Provider references

Provider references and prerequisites are maintained in the connector guidance above. No separate provider-documentation review date is recorded.

​
Source and evidence

Canonical connector source, native analysis and check receipts. Connector artifact: 905888ea276a2a28e36981a79e8142b2547ea451c3e63162cb6915ad4a7d1305. The resource declaration examples above are compiled and compared with exact catalog declarations. Recorded checks apply only to their source, declaration and runtime identities. Configure a connection and inspect its status to establish deployment-specific readiness.