azure-storage
microsoft/azure-skills
Manage Azure Blob Storage, File Shares, Queues, Tables, and Data Lake with access tier guidance.
What is azure-storage?
Azure Storage Services skill provides access to Blob Storage, File Shares, Queue Storage, Table Storage, and Data Lake Storage. Use it to upload/download files, manage storage accounts, choose appropriate access tiers (hot, cool, cold, archive), and configure lifecycle management. Not for SQL databases, Cosmos DB, or Event Hubs/Service Bus messaging.
- List and manage storage accounts, containers, and blobs via MCP tools or Azure CLI
- Upload and download blob content with storage_blob_put and storage_blob_get commands
- Compare and recommend storage access tiers (hot, cool, cold, archive) based on access patterns
- Configure redundancy options (LRS, ZRS, GRS, GZRS) for durability requirements
- Manage lifecycle policies and tier transitions for cost optimization
- Support SMB file shares, async queue messaging, NoSQL table storage, and hierarchical Data Lake namespaces
How to install azure-storage
npx skills add https://github.com/microsoft/azure-skills --skill azure-storage- Azure subscription with storage account(s) created
- Azure CLI installed, or Azure MCP enabled via /mcp or /azure:setup
- Appropriate permissions to access storage accounts and containers
How to use azure-storage
- 1.Enable Azure MCP by running /azure:setup or /mcp if not already enabled
- 2.Use storage_account_list to view available storage accounts
- 3.Use storage_container_list to list containers within a storage account
- 4.Use storage_blob_list to view blobs in a container
- 5.Use storage_blob_get to download blob content or storage_blob_put to upload files
- 6.Consult access tier comparison tables to select hot/cool/cold/archive based on access frequency and cost requirements
- 7.Configure lifecycle management policies to automatically transition blobs between tiers
Use cases
- Uploading application backups and static content to Blob Storage with appropriate access tiers
- Choosing between hot (frequent access), cool (30+ days), cold (90+ days), and archive (180+ days) tiers for cost management
- Setting up file shares for lift-and-shift migrations requiring SMB protocol support
- Implementing async task queues with Queue Storage for decoupled application workflows
- Configuring Data Lake Storage for big data analytics with hierarchical namespace organization
- Cloud architects designing Azure storage strategies
- DevOps engineers managing storage accounts and lifecycle policies
- Application developers building with Azure Storage SDKs
- Data engineers working with Data Lake and big data analytics
- System administrators migrating on-premises file shares to Azure Files
azure-storage FAQ
Use Hot for frequent access (lowest latency, highest storage cost), Cool for infrequent access (30+ days), Cold for rare access (90+ days), and Archive for long-term retention (180+ days, requires rehydration). Choose based on access patterns and cost trade-offs.
LRS (11 nines) for dev/test and recreatable data, ZRS (12 nines) for regional high availability, GRS (16 nines) for disaster recovery, and GZRS (16 nines) for maximum durability.
No. Use the azure-prepare skill for Cosmos DB and the azure-messaging skill for Event Hubs and Service Bus messaging.
Use storage_blob_put with a local file path to upload, or storage_blob_get to download blob content. Alternatively, use Azure CLI commands az storage blob upload and az storage blob download.
Azure provides SDKs in .NET, Java, JavaScript, Python, Go, and Rust. The skill includes condensed quick-reference guides for each language.
Full instructions (SKILL.md)
Source of truth, from microsoft/azure-skills.
name: azure-storage description: "Azure Storage Services including Blob Storage, File Shares, Queue Storage, Table Storage, and Data Lake. Answers questions about storage access tiers (hot, cool, cold, archive), when to use each tier, and tier comparison. Provides object storage, SMB file shares, async messaging, NoSQL key-value, and big data analytics. Includes lifecycle management. USE FOR: blob storage, file shares, queue storage, table storage, data lake, upload files, download blobs, storage accounts, access tiers, storage tiers, hot cool cold archive, storage tier comparison, when to use storage tiers, lifecycle management, Azure Storage concepts. DO NOT USE FOR: SQL databases, Cosmos DB (use azure-prepare), messaging with Event Hubs or Service Bus (use azure-messaging)." license: MIT metadata: author: Microsoft version: "1.2.1"
Azure Storage Services
Services
| Service | Use When | MCP Tools | CLI |
|---|---|---|---|
| Blob Storage | Objects, files, backups, static content | azure__storage | az storage blob |
| File Shares | SMB file shares, lift-and-shift | - | az storage file |
| Queue Storage | Async messaging, task queues | - | az storage queue |
| Table Storage | NoSQL key-value (consider Cosmos DB) | - | az storage table |
| Data Lake | Big data analytics, hierarchical namespace | - | az storage fs |
MCP Server (Preferred)
When Azure MCP is enabled:
azure__storagewith commandstorage_account_list- List storage accountsazure__storagewith commandstorage_container_list- List containers in accountazure__storagewith commandstorage_blob_list- List blobs in containerazure__storagewith commandstorage_blob_get- Download blob contentazure__storagewith commandstorage_blob_put- Upload blob content
If Azure MCP is not enabled: Run /azure:setup or enable via /mcp.
CLI Fallback
# List storage accounts
az storage account list --output table
# List containers
az storage container list --account-name ACCOUNT --output table
# List blobs
az storage blob list --account-name ACCOUNT --container-name CONTAINER --output table
# Download blob
az storage blob download --account-name ACCOUNT --container-name CONTAINER --name BLOB --file LOCAL_PATH
# Upload blob
az storage blob upload --account-name ACCOUNT --container-name CONTAINER --name BLOB --file LOCAL_PATH
Storage Account Tiers
| Tier | Use Case | Performance |
|---|---|---|
| Standard | General purpose, backup | Milliseconds |
| Premium | Databases, high IOPS | Sub-millisecond |
Blob Access Tiers
| Tier | Access Frequency | Cost |
|---|---|---|
| Hot | Frequent | Higher storage, lower access |
| Cool | Infrequent (30+ days) | Lower storage, higher access |
| Cold | Rare (90+ days) | Lower still |
| Archive | Rarely (180+ days) | Lowest storage, rehydration required |
Redundancy Options
| Type | Durability | Use Case |
|---|---|---|
| LRS | 11 nines | Dev/test, recreatable data |
| ZRS | 12 nines | Regional high availability |
| GRS | 16 nines | Disaster recovery |
| GZRS | 16 nines | Best durability |
Service Details
For deep documentation on specific services:
- Blob storage patterns and lifecycle -> Blob Storage documentation
- File shares and Azure File Sync -> Azure Files documentation
- Queue patterns and poison handling -> Queue Storage documentation
SDK Quick References
For building applications with Azure Storage SDKs, see the condensed guides:
- Blob Storage: Python | TypeScript | Java | Rust
- Queue Storage: Python | TypeScript
- File Shares: Python | TypeScript
- Data Lake: Python
- Tables: Python | Java
For full package listing across all languages, see SDK Usage Guide.
Azure SDKs
For building applications that interact with Azure Storage programmatically, Azure provides SDK packages in multiple languages (.NET, Java, JavaScript, Python, Go, Rust). See SDK Usage Guide for package names, installation commands, and quick start examples.
Related skills
More from microsoft/azure-skills and the wider catalog.
