AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

azure-storage

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).

Original source
microsoft
License
MIT
Pinned revision
3f5b461b2314e01c400564051e92469114c5b68f

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

Ask your assistant

Use Agentic Memory skills to read microsoft--azure-storage at revision 3f5b461b2314e01c400564051e92469114c5b68f, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 14

references/sdk/azure-storage-queue-ts.md

Queue Storage — TypeScript SDK Quick Reference

Condensed from azure-storage-queue-ts. Full patterns (SAS generation, poison message handling, visibility extension, message encoding) in the azure-storage-queue-ts plugin skill if installed.

Install

npm install @azure/storage-queue @azure/identity

Quick Start

import { QueueServiceClient } from "@azure/storage-queue";
import { DefaultAzureCredential } from "@azure/identity";
const client = new QueueServiceClient(`https://${accountName}.queue.core.windows.net`, new DefaultAzureCredential());

Best Practices

  • Use DefaultAzureCredential for local development only — in production, use ManagedIdentityCredential. See auth-best-practices.md
  • Always delete after processing — prevent duplicate processing
  • Handle poison messages — move failed messages to a dead-letter queue
  • Use appropriate visibility timeout — set based on expected processing time
  • Extend visibility for long tasks — update message to prevent timeout
  • Use JSON for structured data — serialize objects to JSON strings
  • Check dequeueCount — detect repeatedly failing messages
  • Use batch receive — receive multiple messages for efficiency