Azure · Cloud service
Azure Blob Storage with OrchestrAI
Catalog exported 2026-09-02
Create Azure Storage accounts and list accounts and containers from chat.
OrchestrAI exposes 3 Blob Storage operations: 2 are low-risk (read-only or low-impact), and 1 create or modify resources and run only after you confirm the plan.
What teams use it for
Teams use OrchestrAI to create a storage account for a new app or a Terraform state backend, then list its containers to confirm what is there. Listing all accounts in a subscription or resource group is a quick inventory step during a cost or security review. There is no operation to create a container or upload a blob, and nothing deletes an account, so day-to-day blob work stays in Storage Explorer or the CLI.
Every Blob Storage operation, with its risk level
| Operation | What it does | Risk | Step-level approval |
|---|---|---|---|
List Azure Storage Accounts |
List all Azure Storage accounts in the subscription or a resource group | Low risk | No |
List Azure Storage Containers |
List all containers in an Azure Storage account | Low risk | No |
Create Azure Storage Account |
Create an Azure Storage account | Creates resources | No |
Risk tiers come from the catalog: low is read-only or low-impact, medium creates resources and is reversible, high modifies existing resources, destructive may lose data. Every plan that creates or changes resources is shown with its cost estimate and waits for your confirmation. Operations marked with a step-level approval pause again on their own step. Destructive operations require a typed risk phrase.
Prompts that work
- Create a Standard_LRS storage account called acmelogsprod in rg-prod in centralus
- List all storage accounts in rg-data
- Show me the containers in the acmelogsprod storage account
Before anything runs
Every mutation shows its plan, cost estimate, and blast radius, then waits for your confirmation. Destructive operations require a typed risk phrase. Credentials are minted per run through OIDC federation and discarded afterward; nothing you create here is invisible later, because every resource lands in the desired-state ledger where drift is detected and can be converged. Details on the security page.
Frequently asked questions
- Which Azure Storage operations does OrchestrAI support?
- Three: create a storage account, list storage accounts, and list containers in an account. Listing is read-only and creating an account is medium risk.
- Can OrchestrAI delete an Azure Storage account?
- Deletion is not an available operation, which also means there is no path to losing blob data through OrchestrAI.
- Which Blob Storage operations need an extra approval step?
- None of the Blob Storage operations currently carries a step-level approval gate; they are read-only or run after plan confirmation like any other change.
Other Azure services
Related integrations
Try it on your own account
Connect your cloud read-only and see your resources, drift, and costs before anything runs. $5 minimum to start. Unused credits refunded in your first 14 days.
Unused credits refunded in your first 14 days.