PluginBench
Skill
Official
Pass
Audit score 90

azure-storage

microsoft/azure-skills

Azure Storage skill: Blob, File Shares, Queue, Table, and Data Lake with access tier guidance and lifecycle management

What is azure-storage?

Provides coding agents with reference knowledge and tooling for all five Azure Storage services: Blob Storage, File Shares, Queue Storage, Table Storage, and Data Lake. Covers storage account tiers (Standard/Premium), blob access tiers (Hot/Cool/Cold/Archive), redundancy options (LRS/ZRS/GRS/GZRS), and lifecycle management concepts. Includes MCP server commands for blob operations and CLI fallback commands, plus links to SDK quick-reference guides for Python, TypeScript, Java, and Rust.

  • Lists and manages Azure storage accounts, containers, and blobs via MCP server commands or Azure CLI
  • Guides selection between Blob Storage, File Shares, Queue Storage, Table Storage, and Data Lake
  • Explains blob access tiers (Hot, Cool, Cold, Archive) and when to use each based on access frequency
  • Compares storage account performance tiers (Standard vs Premium) and redundancy options (LRS, ZRS, GRS, GZRS)
  • Provides CLI commands for uploading, downloading, and listing blobs and containers
  • References SDK quick-start guides for Blob, Queue, File Share, Data Lake, and Table Storage across multiple languages

How to install azure-storage

npx skills add https://github.com/microsoft/azure-skills --skill azure-storage
Prerequisites
  • Azure subscription with at least one storage account
  • Azure CLI installed and authenticated (for CLI fallback commands)
  • Azure MCP server enabled for MCP tool commands (run /azure:setup or enable via /mcp)
  • Skill installed via: npx skills add https://github.com/microsoft/azure-skills --skill azure-storage
Claude Code
Cursor
Windsurf
Cline

How to use azure-storage

  1. 1.Install the skill using: npx skills add https://github.com/microsoft/azure-skills --skill azure-storage
  2. 2.Enable Azure MCP server via /azure:setup or /mcp for MCP tool access
  3. 3.Use the azure__storage MCP tool with command storage_account_list to list your storage accounts
  4. 4.Use storage_container_list and storage_blob_list to browse containers and blobs
  5. 5.Use storage_blob_get or storage_blob_put to download or upload blob content
  6. 6.If MCP is unavailable, fall back to az storage blob commands provided in the skill
  7. 7.Ask the agent to recommend the right blob access tier (Hot/Cool/Cold/Archive) based on your access patterns
  8. 8.Reference SDK guides for Python, TypeScript, Java, or Rust to build storage-integrated applications

Use cases

Good for
  • Upload or download files and blobs to/from Azure Blob Storage
  • Choose the right blob access tier to optimize storage costs
  • Set up SMB file shares for lift-and-shift workloads using Azure Files
  • Implement async task queues using Azure Queue Storage
  • Analyze big data with hierarchical namespace storage via Azure Data Lake
Who it's for
  • Developers building applications that read or write files to Azure Storage
  • Cloud engineers designing storage architectures and selecting appropriate tiers
  • DevOps engineers automating blob and container management via CLI or MCP
  • Data engineers working with Azure Data Lake for analytics workloads
  • Anyone evaluating Azure Storage redundancy options for durability requirements

azure-storage FAQ

When should I use Archive tier instead of Cool or Cold?

Archive is for blobs accessed rarely (180+ days). It has the lowest storage cost but requires rehydration before access, which adds latency. Use Cool for 30+ day infrequent access and Cold for 90+ day rare access when immediate retrieval is still needed.

Can I use this skill for Cosmos DB or SQL databases?

No. This skill covers Azure Storage services only. For Cosmos DB or SQL databases, use the azure-prepare skill instead.

Can I use this skill for Event Hubs or Service Bus messaging?

No. Event Hubs and Service Bus are covered by the azure-messaging skill. Queue Storage (covered here) is for simple async task queues, not full messaging infrastructure.

What redundancy option should I choose for disaster recovery?

GRS (16 nines durability) provides geo-redundant disaster recovery. GZRS combines zone and geo redundancy for the best overall durability. LRS is suitable for dev/test or easily recreatable data.

Do I need the MCP server or can I use the CLI?

Both are supported. The MCP server (azure__storage tool) is preferred when Azure MCP is enabled. If not, the skill provides equivalent az storage CLI commands for all major blob and container operations.

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.1.2"

Azure Storage Services

Services

ServiceUse WhenMCP ToolsCLI
Blob StorageObjects, files, backups, static contentazure__storageaz storage blob
File SharesSMB file shares, lift-and-shift-az storage file
Queue StorageAsync messaging, task queues-az storage queue
Table StorageNoSQL key-value (consider Cosmos DB)-az storage table
Data LakeBig data analytics, hierarchical namespace-az storage fs

MCP Server (Preferred)

When Azure MCP is enabled:

  • azure__storage with command storage_account_list - List storage accounts
  • azure__storage with command storage_container_list - List containers in account
  • azure__storage with command storage_blob_list - List blobs in container
  • azure__storage with command storage_blob_get - Download blob content
  • azure__storage with command storage_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

TierUse CasePerformance
StandardGeneral purpose, backupMilliseconds
PremiumDatabases, high IOPSSub-millisecond

Blob Access Tiers

TierAccess FrequencyCost
HotFrequentHigher storage, lower access
CoolInfrequent (30+ days)Lower storage, higher access
ColdRare (90+ days)Lower still
ArchiveRarely (180+ days)Lowest storage, rehydration required

Redundancy Options

TypeDurabilityUse Case
LRS11 ninesDev/test, recreatable data
ZRS12 ninesRegional high availability
GRS16 ninesDisaster recovery
GZRS16 ninesBest durability

Service Details

For deep documentation on specific services:

SDK Quick References

For building applications with Azure Storage SDKs, see the condensed guides:

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.