PluginBench
Skill
Official
Review
Audit score 70

azure-storage

microsoft/azure-skills

Manage Azure Blob Storage, File Shares, Queues, Tables, and Data Lake with access tier guidance.

SourceView on skills.sh

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
Prerequisites
  • 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
Claude Code
Cursor
Windsurf
Cline

How to use azure-storage

  1. 1.Enable Azure MCP by running /azure:setup or /mcp if not already enabled
  2. 2.Use storage_account_list to view available storage accounts
  3. 3.Use storage_container_list to list containers within a storage account
  4. 4.Use storage_blob_list to view blobs in a container
  5. 5.Use storage_blob_get to download blob content or storage_blob_put to upload files
  6. 6.Consult access tier comparison tables to select hot/cool/cold/archive based on access frequency and cost requirements
  7. 7.Configure lifecycle management policies to automatically transition blobs between tiers

Use cases

Good for
  • 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
Who it's for
  • 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

When should I use each blob access tier?

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.

What redundancy option should I choose?

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.

Can I use this skill for Cosmos DB or Event Hubs?

No. Use the azure-prepare skill for Cosmos DB and the azure-messaging skill for Event Hubs and Service Bus messaging.

How do I upload or download files?

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.

What languages are supported for Azure Storage SDKs?

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

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.