Integration · Cloud and hosting
AI agents for Azure Blob Storage
List containers and files, read and download files, upload any file, save JSON files, create containers and delete files in an Azure Storage account's Blob service, signed with the account's access key (Shared Key).
- Actions
- 8
- Read
- 4
- Write
- 4
Actions
What your agents can do in Azure Blob Storage
List containers and files, read and download files, upload any file, save JSON files, create containers and delete files in an Azure Storage account's Blob service, signed with the account's access key (Shared Key). Files go in and out by reference (fil_…), never as text. Lists come back as Azure's XML, which this tool returns as text.
Read 4
Look things up. Nothing changes.
List containers
Lists the storage account's containers (top-level folders), up to 5,000 a page, optionally only those whose name starts with a prefix.
List files
Lists the files (blobs) in a container, optionally only those whose name starts with a prefix like invoices/2026/.
Read a file
Reads one file (blob).
Download a file
Downloads one file (blob) of any type, text and JSON included, as a file reference in file.
Write 4
Create, change or send.
Upload a file
Uploads a file to a container as a block blob, replacing any file with the same name: a file a person attached, or one another tool returned (pass its file reference, fil_…).
Save a JSON file
Saves a JSON object or array as a file (block blob) in a container, with content type application/json, replacing any file with the same name.
Delete a fileDeletes data
Deletes one file (blob).
Create a container
Creates a private container (no anonymous access) in the storage account.
A person can approve first
Any write action can be set to wait for a person's approval before it runs, so an agent asks before it changes anything. Actions that delete data ask first by default.
Connection
How it connects
Connect it once in the console, then give it to the agents and workflows that need it.
Enter the sign-in details Azure Blob Storage gives you for its API.
What you enter
- Access key
Settings
- Storage account name
Kept safe
- Credentials are stored encrypted with your organization's own keys.
- They are opened only by the process that makes the call, at the moment it runs, and never go into a prompt or the browser.
- Calls go only to the tool's own servers.
Ideas
Ideas to start with
Starting points made only from the actions above. Mix them with any other tool your agents can use.
- 01
Ask about your Azure Blob Storage data
Ask a question in plain words. The agent can list containers, list files or read a file in Azure Blob Storage, then answers with what it found.
- 02
Let an agent update Azure Blob Storage
Have the agent upload a file or save a JSON file in Azure Blob Storage as part of a larger task. Turn on approval and a person signs off on each change first.
- 03
Share what it finds in Slack
Give one agent Azure Blob Storage and Slack: it can list containers in Azure Blob Storage and post a summary to a Slack channel in the same run.
Works well with
More Cloud and hosting tools
- Amazon Web Services7 actionsEvery AWS service from one connection: EC2, S3, Lambda, RDS, DynamoDB, IAM, ECS, EKS, CloudWatch, Bedrock and over four hundred more.
- Microsoft Azure7 actionsEvery Azure service from one connection: Virtual Machines, Storage, App Service, Functions, AKS, SQL, Cosmos DB, Key Vault, Networking, Monitor, OpenAI and every other resource provider of Azure Resource Manager.
- Google Cloud7 actionsEvery Google Cloud API from one connection: Compute Engine, Cloud Storage, BigQuery, Cloud Run, GKE, Cloud SQL, Pub/Sub, IAM, Vertex AI and two hundred more.
- Amazon S38 actionsList buckets and files, read and download files, upload any file, save JSON files and delete files in Amazon S3 (Simple Storage Service), signed with an AWS access key.
- Netlify5 actionsList sites and their deploys, start a build, check a deploy's status, and roll a site back to an earlier deploy, on the Netlify teams a personal access token can reach.
- Heroku16 actionsSee Heroku apps, dynos, releases and builds, restart dynos, scale process types, roll back a release and switch maintenance mode, with a Heroku API token.
FAQ
Azure Blob Storage and MyDeepAgents
Can MyDeepAgents connect to Azure Blob Storage?
Yes. The Azure Blob Storage connector has 8 actions: 4 read and 4 make changes. Your agents can call them as tools, and your workflows can run them as steps.
How do I connect Azure Blob Storage?
Enter the sign-in details Azure Blob Storage gives you for its API. You'll need: Access key. The connection also asks for: Storage account name. Credentials are stored encrypted with your organization's own keys and are opened only at the moment of a call.
Can an agent change data in Azure Blob Storage without asking?
Only if you let it. Each of the 4 actions that change data can be set to wait for a person's approval before it runs, and the one that deletes data asks first by default.
Can I use Azure Blob Storage in workflows as well as agents?
Yes. Every Azure Blob Storage action also works as a step in a workflow, and the same connection serves your agents and your workflows.
Early access
Put Azure Blob Storage to work
Connect it in a few minutes, give an agent the actions it needs, and decide which changes wait for a person.