Agent skill · Security

azure-blob-storage

Expert knowledge for Azure Blob Storage development including troubleshooting, best practices, decision making, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when using Blob tiers, lifecycle policies, immutability, SAS/SFTP access, or NFS/BlobFuse mounts, and other Azure Blob Storage related development tasks. Not for Azure Files (use azure-files), Azure Table Storage (use azure-table-storage), Azure Queue Storage (use azure-queue-storage), Azure NetApp Files (use azure-netapp-files).

MicrosoftDocsgithub.com/MicrosoftDocsGitHub ↗
claude-codecopilotcodexCC-BY-4.0
Install
npx skills add MicrosoftDocs/Agent-Skills --skill azure-blob-storage --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 50 KB
Bundled scripts: none
Requires: Requires network access. Uses mcp_microsoftdocs:microsoft_docs_fetch or fetch_webpage to retrieve documentation.
Path: skills/azure-blob-storage/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 682 · +8 this week
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

Review
written from the skill's own SKILL.md · Aug 5, 2026

What it does

The skill provides expert guidance for Azure Blob Storage covering troubleshooting, best practices, decision making, limits & quotas, security, configuration, integrations & coding patterns, and deployment. It is intended for use with tasks related to Blob tiers, lifecycle policies, immutability, SAS/SFTP access, or NFS/BlobFuse mounts, and other Blob Storage development tasks.

How it works

The skill instructs the agent to use a Category Index to locate relevant sections. For categories with line ranges, the agent should read the file with the specified lines using read_file on the given lines. For categories with links, the agent should use read_file on the linked reference file. It requires network access and uses mcp_microsoftdocs:microsoft_docs_fetch (preferred) or fetch_webpage to retrieve documentation. It also alerts if metadata.generated_at is more than 3 months old and suggests pulling the latest version. It provides a set of categories (Troubleshooting, Best Practices, Decision Making, Limits & Quotas, Security, Configuration, Integrations & Coding Patterns, Deployment) each with references to topics and URLs for MS Learn documentation.

When to use it

Use when working on Azure Blob Storage development tasks such as troubleshooting storage tasks, applying best practices, planning costs and design, understanding limits and quotas, securing access, configuring monitoring and lifecycle, integrating with SDK/CLI/tools, and deployment scenarios.

What it can touch

The skill requires network access and uses the mcp_microsoftdocs:microsoft_docs_fetch or fetch_webpage tools to retrieve documentation. It references categories and linked files like security.md for content access.

Caveats

License: CC-BY-4.0. It relies on external Microsoft Learn documentation via network fetches. It is categorized under Security and relies on the availability of the mcp_microsoftdocs tooling; if unavailable, a fallback is suggested. No outcomes are promised beyond guidance to consult the referenced documentation.

From the SKILL.md

# Azure Blob Storage Skill This skill provides expert guidance for Azure Blob Storage. Covers troubleshooting, best practices, decision making, limits & quotas, security, configuration, integrations & coding patterns, and deployment. It combines local quick-reference content with remote documentation fetching capabilities. ## How to Use This Skill > **IMPORTANT for Agent**: Use the **Category Index** below to locate relevant sections. For categories with line ranges (e.g., `L35-L120`), use `read_file` with the specified lines. For categories with file links (e.g., `[security.md](security.md)`), use `read_file` on the linked reference file > **IMPORTANT for Agent**: If `metadata.generated_at` is more than 3 months old, suggest the user pull the latest version from the repository. If `mcp_microsoftdocs` tools are not available, suggest the user install it: [Installation Guide](https://github.com/MicrosoftDocs/mcp/blob/main/README.md) This skill requires **network access** to fetch documentation content: - **Preferred**: Use `mcp_microsoftdocs:microsoft_docs_fetch` with query string `from=learn-agent-skill`. Returns Markdown. - **Fallback**: Use `fetch_webpage` with query string `from

What's inside
Steps it walks through
  1. How to Use This Skill
  2. Category Index
  3. Troubleshooting
  4. Best Practices
  5. Decision Making
  6. Limits & Quotas
  7. Security
  8. Configuration
  9. Integrations & Coding Patterns
  10. Deployment
More from Agent-Skills
All skills →
About this skill
What does the azure-blob-storage skill do?

Expert knowledge for Azure Blob Storage development including troubleshooting, best practices, decision making, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when using Blob tiers, lifecycle policies, immutability, SAS/SFTP access, or NFS/BlobFuse mounts, and other Azure Blob Storage related development tasks. Not for Azure Files (use azure-files), Azure Table Storage (use azure-table-storage), Azure Queue Storage (use azure-queue-storage), Azure NetApp Files (use azure-netapp-files).

How do I install it?

Run `npx skills add MicrosoftDocs/Agent-Skills --skill azure-blob-storage --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From MicrosoftDocs/Agent-Skills, a repository with 682 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going