azure-storage

devopsmicrosoft606K installs

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

Install

npx skills add https://github.com/microsoft/azure-skills --skill azure-storage

SKILL.md

---name: azure-storagedescription: 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: MITmetadata: author: Microsoftversion: 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__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

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

azure-diagnosticsmicrosoft608KDebug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe triage. WHEN: debug production issues, troubleshoot app service, app service high CPU, app service deployment failure, troubleshoot container apps, troubleshoot functions, troubleshoot AKS, VM RDP, Linux SSH, VM black screen, can't connect to VM, reset VM password, NSG or firewall blocking, kubectl cannot connect, kube-system/CoreDNS failures, pod pending, crashloop, node not ready, upgrade failures, a azure-preparemicrosoft608KPrepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Terraform), and Dockerfiles for the Azure Developer CLI (azd) workflow. USE ONLY when the user explicitly wants to use azd as the deployment tool, or the project already has an azure.yaml file. DO NOT USE FOR: non-azd deployments, Python App Service code-only deploys (use python-appservice-deploy), or cross-cloud migration (use azure-cloud-migrate). WHEN: prepare app for azd, create azure.yaml, set up az azure-aimicrosoft608KUse for Azure AI: Search, Speech, OpenAI, Document Intelligence. Helps with search, vector/hybrid search, speech-to-text, text-to-speech, transcription, OCR. WHEN: AI Search, query search, vector search, hybrid search, semantic search, speech-to-text, text-to-speech, transcribe, OCR, convert text to speech.azure-deploymicrosoft607KExecute Azure deployments for ALREADY-PREPARED applications that have existing .azure/deployment-plan.md and infrastructure files. DO NOT use this skill when the user asks to CREATE a new application — use azure-prepare instead. This skill runs azd up, azd deploy, terraform apply, and az deployment commands with built-in error recovery. Requires .azure/deployment-plan.md from azure-prepare and validated status from azure-validate. WHEN: \"run azd up\", \"run azd deploy\", \"execute deployment\",