Abort Blob Copy
Abort one known pending asynchronous copy. Azure leaves its destination as a zero-length blob, and a completed copy cannot be aborted.
Store, list, retrieve, and manage containers and blobs in an Azure Storage account using delegated Microsoft Entra authorization and Azure RBAC.
Abort one known pending asynchronous copy. Azure leaves its destination as a zero-length blob, and a completed copy cannot be aborted.
Append file or base64 content to an existing append blob with optional exact-position and maximum-final-size guards.
Ask Azure to append an independently readable HTTPS source URL or byte range to an existing append blob. Prefer a public Azure Blob URL or one with a read SAS when non-Azure presigned providers return 500; the destination remains the connected account.
Clear and deallocate one aligned range of an Azure page blob.
Create or replace a block blob by committing an ordered list of staged or existing block IDs. IDs must all have the same raw UTF-8 byte length used during staging.
Copy any Azure-fetchable HTTPS source into a blob. Use this broad tool for synchronous completion or optional destination tier; use START_ASYNC_BLOB_COPY for a dedicated pollable Azure-blob copy workflow.
Start an asynchronous incremental copy from an independently authorized Azure page blob snapshot URL.
Create or replace an empty Azure append blob for ordered append-only writes. Existing blobs are protected by default.
Create a read-only timestamped snapshot of a base Azure blob, optionally replacing metadata on the snapshot.
Create a private Azure Blob Storage container with optional user-defined metadata. This does not enable public access or alter access policies.
Create or replace an empty fixed-capacity Azure page blob for aligned random-access writes.
Delete an Azure Blob Storage base blob, one snapshot, one version, or only the base blob's snapshots. Base-blob deletion refuses associated snapshots unless delete_snapshots explicitly selects include or only.
Delete an Azure Blob Storage container and all blobs it contains asynchronously. The required confirm_delete=true explicitly confirms this destructive operation.
Delete a known Unlocked blob immutability policy, removing its write and delete protection before the former deadline, after verifying the exact deadline and ETag. Locked policies are rejected before deletion.
Download an Azure blob or byte range. Small UTF-8 textual content is returned inline; binary, non-UTF-8, and large content is returned through a temporary framework file descriptor.
Find blobs whose index tags match an Azure tag expression across the connected account and return one cursor page. This operation is not supported on hierarchical-namespace accounts. For a known single-container search, use FIND_CONTAINER_BLOBS_BY_TAGS.
Find blobs matching an Azure index-tag expression within exactly one known container and return one cursor page. This operation is not supported on hierarchical-namespace accounts. Use FIND_BLOBS_BY_TAGS instead for an account-wide search.
Read only user-defined metadata for one Azure blob, snapshot, or version without downloading content or returning unrelated system properties. Optional lease, ETag, date, and tag conditions are enforced by Azure.
Get an Azure blob's system properties, HTTP properties, and user-defined metadata without downloading its content. Use GET_BLOB_METADATA when only user-defined metadata is needed. For asynchronous copies, match copy_id to START_ASYNC_BLOB_COPY and poll copy_status until it is no longer pending.
Read Blob data-plane logging, metrics, CORS, blob retention, static website, and protocol settings without changing them. Container delete retention, versioning, change feed, restore, last-access tracking, and cross-tenant replication require Azure Resource Manager and are not returned by this action.
Read geo-replication status from the connected Azure Blob account's derived read-access secondary endpoint. The account must use RA-GRS or RA-GZRS replication.
Read index tags from an Azure base blob, snapshot, or version.
Inspect committed and/or uncommitted blocks for a block blob or snapshot, including Azure IDs and best-effort decoded UTF-8 IDs.
Read an Azure Blob container's public-access level and stored signed access policies without changing access.
Read only user-defined metadata for one Azure Blob container without listing blobs or returning unrelated system properties.
Get system properties and user-defined metadata for one Azure Blob Storage container without listing or reading its blobs. Use GET_CONTAINER_METADATA when only user-defined metadata is needed.
Return one cursor page of updated and cleared ranges since an older page blob snapshot.
Return one cursor page of allocated ranges in an Azure page blob or snapshot.
Return the connected Azure Blob account SKU, account kind, and hierarchical-namespace state.
List one page of blobs in an Azure Blob Storage container as a flat list or delimiter-based hierarchy, optionally filtered by name prefix.
List containers in the connected storage account, optionally filtered by name prefix, and return one page with a continuation cursor. Can include soft-deleted container versions needed by RESTORE_CONTAINER.
Acquire, renew, change, release, or irreversibly break a write/delete lease on one blob. Break disrupts the current lease holder, requires explicit confirmation, and cannot be undone.
Acquire, renew, change, release, or irreversibly break the delete lease on one Azure Blob container. Break disrupts the current lease holder, requires explicit confirmation, and cannot be undone.
Run a read-only SQL expression over supported Azure blob content and return Azure's streamed binary query result as a temporary file.
Rename a container in a hierarchical-namespace-enabled Azure Storage account.
Change an Azure page blob's fixed capacity to a new 512-byte-aligned size. Shrinking permanently discards pages beyond the new capacity.
Restore one soft-deleted Azure Blob container version, optionally under a different destination name. Container soft delete must be enabled.
Irreversibly seal one append blob so it can never accept another append. Requires explicit irreversible confirmation; optional ETag, lease, and append-position conditions can guard against concurrent changes.
Change a blob, snapshot, or version to an Azure access tier and optionally set archive rehydration priority. Tier changes can affect storage, retrieval, rehydration, and early-deletion charges.
Schedule or remove automatic deletion for a blob on a hierarchical-namespace-enabled Azure Storage account. Absolute uses expires_on; RelativeToCreation and RelativeToNow use millisecond expires_in; NeverExpire uses neither. Scheduling and removal each require explicit confirmation.
Place or remove a legal hold on an eligible Azure blob, snapshot, or version. Removing protection requires separate explicit confirmation.
Replace the connected account's supported Blob data-plane service configuration from a typed GET_SERVICE_PROPERTIES snapshot plus explicit changes. This is account-wide replacement, not a partial patch. Container delete retention, versioning, change feed, restore, last-access tracking, and cross-tenant replication require Azure Resource Manager and are not accepted here.
Replace all index tags on an Azure base blob or version. Pass an empty tag object to clear all tags.
Replace a container's public-access level and complete stored signed-identifier list. Omitted identifiers are deleted; private means no public-access header.
Create or replace an Unlocked time-based immutability policy that blocks writes and deletes until its deadline on an eligible blob, snapshot, or version. The policy remains removable; Locked mode is intentionally unsupported.
Stage one binary block for a later block-list commit. Keep every plain block ID for a blob at the same UTF-8 byte length; the tool base64-encodes IDs for Azure.
Ask Azure to stage one block from an independently readable HTTPS URL or source byte range. The destination remains the connected account.
Start a dedicated pollable copy from an Azure Blob HTTPS source and return its copy ID. Poll GET_BLOB_PROPERTIES on the destination, require its copy_id to match this result, and inspect copy_status until it is no longer pending; ABORT_BLOB_COPY can cancel a matching pending copy. This action never requests synchronous completion.
Restore the content and metadata of a soft-deleted Azure blob. Blob soft delete must be enabled and the retained version must still exist.
Replace HTTP response properties stored on an Azure blob without changing its content or user metadata. Azure clears every omitted HTTP property when this action sets any property.
Replace all user-defined metadata on an Azure Blob Storage blob. Existing keys omitted from the request are removed, and an empty metadata object clears all metadata.
Replace all user-defined metadata on an Azure Blob Storage container. Existing keys omitted from the request are removed, and an empty metadata object clears all metadata.
Set, raise, or increment an Azure page blob's user-controlled sequence number.
Upload a file or standard-base64 content as an Azure block blob with optional metadata and MIME type. Existing blobs are protected by default; set overwrite true only when replacement is intended.
Ask Azure to create a complete block blob by fetching an independently readable HTTPS source URL. The destination remains the connected account.
Write file or standard-base64 content into one 512-byte-aligned Azure page blob range.
Ask Azure to fetch one aligned HTTPS source range into an aligned destination page blob range. Prefer a public Azure Blob URL or one with a read SAS when non-Azure presigned providers return 500.
The Azure Blob Storage integration connects your Dench AI CRM directly to Azure Blob Storage, so agents can read and act on your Azure Blob Storage data as part of everyday work — answering questions in chat, keeping your CRM in sync, and running automations without anyone copying data between tools.
57 actions are available for agents to invoke on your behalf. Every call runs through Azure Blob Storage's own authorization, scoped to the account you connect.
Sign in to your Dench workspace and open Integrations.
Find Azure Blob Storage and click Connect — you'll authorize access through Azure Blob Storage's own sign-in flow. No API keys or code required.
Ask an agent to use Azure Blob Storage in chat, or call it from an automation.
Manage or disconnect the connection any time from workspace settings.
The Dench Azure Blob Storage integration connects your AI CRM to Azure Blob Storage, so AI agents can work with your Azure Blob Storage data as part of chats, automations, and CRM workflows. You connect your account once, and every agent in your workspace can use it — governed by your workspace permissions.
The Azure Blob Storage integration currently exposes 57 actions, including Abort Blob Copy, Append Block, Append Block from URL, Clear Page Blob Pages, Commit Block List, and Copy Blob from URL. Agents invoke them on your behalf from chat or from automations.
No. You connect Azure Blob Storage from your Dench workspace using Azure Blob Storage's own sign-in and authorization flow — no API keys to copy, no glue code to maintain.
Connections are authorized through Azure Blob Storage's own authentication flow, and Dench stores only the authorization needed to act on your behalf. You can review and disconnect the Azure Blob Storage connection from your workspace settings at any time.