# Plan and Build Azure Storage Solutions

Choosing the right Azure Storage service, tier, authentication method, and SDK pattern can be complex. This skill provides concise guidance, commands, and language-specific examples for secure storage implementations.

## Install

```bash
npx skillstore add microsoft/azure-storage
```

## Metadata

- Status: approved
- Slug: microsoft-azure-storage
- Version: 0.0.0-placeholder
- Author version: 0.0.0-placeholder
- Skillstore revision: r2
- Version status: valid
- Tree hash: 22c523efb269b6ad0b4290b72c7b4fa7b8ee73774002ac7fb1737d3b6a3dda73
- Author: microsoft
- GitHub username: microsoft
- License: MIT
- Repository: https://github.com/microsoft/github-copilot-for-azure/tree/main/plugin/skills/azure-storage/
- Ref: ebdfe608f5de2b66ff37ab4af12af8ac4f5e8006
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, env\_access, scripts, network, filesystem
- Quality score: 78
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/microsoft-azure-storage
- Manifest: https://skillstore.pages.dev/api/skills/microsoft-azure-storage/manifest

## Capabilities

- Compares Blob Storage, Files, Queues, Tables, and Data Lake for common workload requirements.
- Explains account performance tiers, blob access tiers, and storage redundancy options.
- Provides Azure MCP and CLI workflows for listing accounts, containers, and blobs, plus blob transfers.
- Supplies SDK package names and quick starts for Python, TypeScript, Java, Go, Rust, and .NET.
- Recommends local and production authentication patterns using Azure Identity credentials.
- Shares service-specific guidance for lifecycle, streaming, partitioning, queues, and access control.

## Use Cases

- Select a Storage Architecture: Compare services, access tiers, and redundancy options for a workload with clear performance, durability, and access requirements.
- Integrate an Application: Choose an SDK package, endpoint pattern, and environment-appropriate credential for a new storage integration.
- Operate Storage Resources: List accounts, inspect containers, and transfer blobs through Azure MCP or documented CLI workflows.

## Prompt Templates

### Choose a Storage Service

```
Compare Azure Blob Storage, Files, Queues, Tables, and Data Lake for [workload]. Recommend one service and explain the main tradeoffs.
```

### Choose Tiers and Redundancy

```
Recommend an access tier and redundancy option for [data type], accessed [frequency], retained for [duration], with [recovery requirement].
```

### Plan an SDK Integration

```
Outline a [language] integration for [Azure Storage service]. Include the package, endpoint pattern, local authentication, production authentication, and operational safeguards.
```

### Design a Production Migration

```
Create a migration plan from [current system] to [Azure Storage service]. Address identity, RBAC, data transfer, validation, rollback, monitoring, and lifecycle management.
```

## Limitations

- Does not cover SQL databases, Cosmos DB, Event Hubs, or Service Bus.
- Requires configured Azure credentials and permissions before MCP, CLI, or SDK operations can access resources.
- Provides condensed SDK examples rather than complete application implementations.
- Uses placeholder resource names and does not verify current pricing or regional availability.

## Best Practices

- Use managed identity and least-privilege Azure RBAC for production workloads.
- Choose access tiers from measured access frequency, retention, retrieval latency, and cost requirements.
- Stream large transfers and design idempotent operations with explicit retry and failure handling.

## Anti Patterns

- Do not hardcode credentials, connection strings, account keys, or long-lived SAS tokens.
- Do not use DefaultAzureCredential as an unrestricted production authentication strategy.
- Do not select a storage service or tier without workload, durability, latency, and retention requirements.

## Security Audit

- Audited at: 2026-07-23T19:31:39.197\+00:00
- Summary: All 65 static findings are false positives caused by Markdown formatting, example placeholders, official Azure endpoints, environment-selection checks, and relative documentation links. The files contain documentation and code samples, with no prompt injection, secret exfiltration, unsafe dynamic execution, path traversal, or system reconnaissance evidence. No semantic security findings were identified.

## Stats

- Views: 142
- Downloads: 9
- Favorites: 0
- Popularity score: 0