Skip to content
Custom Connectors

Full read-write Claude connector for Azure Blob Storage

Let Claude upload, organize, and clean up blobs in Azure Blob Storage

Stop driving the portal or az CLI for routine container work. Claude uploads blobs to the right prefix, copies and tidies what lives there, and sets metadata in the storage account where your files already are, with deletes held back for your approval.

Azure Blob Storage is Microsoft's object store for unstructured data, where teams keep files, backups, logs, media, and data lake objects in containers. People want Claude to do more than list a container: to upload blobs, organize prefixes, and manage what lives there.

What is an Azure Blob Storage MCP server?

A Azure Blob Storage MCP server is a small hosted service that exposes Azure Blob Storage's data and actions to Claude over the Model Context Protocol, so Claude can files and folders inside your own account. We build it as a custom connector with separate read and write tools, and destructive actions stay gated behind your approval.

What can Azure Blob Storage's current connector do today?

Today, Azure Blob Storage has no first-party Claude connector, and Claude cannot reach your containers on its own. Any read-leaning access usually comes from a general Azure or filesystem MCP server you wire up yourself. A custom connector adds scoped write actions over the Blob service, with separated read and write tools and gated deletes.

What does full read-write Azure Blob Storage access unlock?

Full read-write Azure Blob Storage access lets Claude upload a blob to a specific container and prefix, copy or move blobs between locations, set blob metadata and access tiers, generate a SAS URL, and delete blobs once you approve. The container housekeeping that used to mean the portal or az CLI happens through the assistant.

  • Upload a blob to a specific container and prefix
  • Copy or move blobs between containers or prefixes
  • Set or update blob metadata and access tier for lifecycle and cost tracking
  • Generate a scoped SAS URL for a single blob after you approve it
  • Delete a blob or a scoped set of blobs once you confirm
  • List a prefix and propose a batched reorganization for review

Can Claude upload files to a container in Azure Blob Storage?

Yes. With a custom Azure Blob Storage connector, Claude can upload a file or generated artifact to a specific container and prefix, setting the content type and metadata you specify. Upload is a scoped write tool limited to the containers the credential allows, so it never reaches paths you have not opened up.

Can Claude reorganize or move blobs between containers in Azure Blob Storage?

Claude can list a prefix in Azure Blob Storage, copy or move blobs between containers or prefixes, and set blob metadata and access tiers for lifecycle and cost tracking. For larger cleanups it can propose a batched reorganization for you to review first, so nothing shifts until you have seen the plan.

Will Claude delete blobs from Azure Blob Storage on its own?

No. Delete is a separate, gated write action in Azure Blob Storage. Claude can list blobs and propose what to remove, but nothing is deleted until you approve it. The Entra ID identity or SAS behind the connector can deny delete entirely, and Claude only ever has the access that credential already holds.

How an Azure Blob Storage connector works

We build a small MCP server that authenticates to Azure Blob Storage with a scoped credential, a Microsoft Entra ID identity or a SAS limited to the containers and prefixes the work needs. Read tools (list, get blob, read properties) and write tools (upload, copy, set metadata, delete) are separated, and destructive actions like delete require your confirmation. Claude only ever has the access the underlying credential already has, and we can pair this with storage firewall rules or IP allowlisting where your account supports it.

Frequently asked questions

Can Claude upload files to an Azure Blob Storage container, not just read them?
Yes. A custom connector exposes an upload write tool scoped to the containers and prefixes you allow, so Claude can put a file or generated artifact at a specific blob path with the content type and metadata you specify. There is no first-party connector today, so write access needs a purpose-built MCP server backed by a scoped credential.
Will Claude delete blobs from my container without my approval?
No. Delete is a separate, gated write action. Claude can list blobs and propose what to remove, but nothing is deleted until you approve it. You decide which actions run automatically and which require a confirmation step, and the credential can deny delete entirely if you prefer to keep it out of the connector.
Can I limit the connector to certain containers or storage accounts?
Yes. The connector authenticates with an Entra ID identity or SAS you control, and it inherits only the permissions that credential holds. You can scope it to specific containers or a single storage account, and if your setup needs it we can add storage firewall rules or IP allowlisting so access only comes from approved addresses.

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.