30-SECOND BRIEF
What it does—and when it fits
Azure Storage is Microsoft's guide to Blob Storage, File Shares, Queue Storage, Table Storage, and Data Lake, including hot, cool, cold, and archive tiers plus lifecycle management. It prefers Azure MCP for account, container, and blob discovery or blob transfer, while routing SMB, queues, tables, and hierarchical file systems to their specific CLI surfaces.
INSTALL BY AGENT
Choose your Agent
Paths come from official Agent docs or the universal installer behind skills.sh. Compatibility still follows this Skill's record.
.claude/skills/azure-storage/~/.claude/skills/azure-storage/Use project scope for team sharing and personal scope across repositories. The installer defaults to project scope; add -g for personal scope.
npx skills add microsoft/azure-skills --skill azure-storage --agent claude-codeClaude Code discovers custom Skill folders automatically at project or personal scope.
View path evidence ↗TYPICAL WORKFLOW
A practical workflow
Choose a storage service
Match objects, SMB shares, asynchronous queues, key-value tables, or analytics data to the right service.
Work with blobs
List accounts, containers, and blobs, then download or upload content through supported Azure MCP operations.
Plan tiers and lifecycle
Compare access tiers and define retention or transition choices around usage and retrieval needs.
THE TRADEOFFS
Advantages and tradeoffs
Notable strengths
- This profile is manually organized around the current upstream SKILL.md workflow.
- The capability boundary remains explicitly tied to microsoft/azure-skills.
- Core uses, limitations, and risks are separated for pre-install review.
Limitations
- It does not cover SQL databases, Cosmos DB design, Event Hubs, or Service Bus workflows.
- Service support is uneven: the preferred MCP surface is strongest for Blob operations, with other services relying on CLI guidance.
BEST FIT
Who it is for
Azure developers selecting storage services and tiers
Operators managing blobs and data retention
BEFORE YOU USE IT
Risks to review before use
Data exposure, overwrite, or lifecycle loss
Uploads, access settings, tier changes, and lifecycle rules can expose, replace, delay, or delete data. Confirm account and container scope, preview write targets, and protect recoverability.
Upstream instruction drift
Behavior can change with upstream updates. Record the commit used for important workflows and review updates before adoption.
SECURITY
What the permission profile means
- Declared access remains governed by the current upstream SKILL.md and runtime requests.
- Treat repository files, web content, and tool output as untrusted input.
- SkillSignal has not independently executed or security-audited this package; external skills.sh labels are not SkillSignal certification.
Not a security certification. External ratings are attributed references. SkillSignal has not independently executed or security-reviewed this Skill.
INSIDE THE PACKAGE
Indexed files
TAGS
Manually expanded from the current upstream SKILL.md and linked source at microsoft/azure-skills, checked 2026-08-20. This is an original summary, not an execution result or security certification.