Azure Table Storage Skill
This skill provides expert guidance for Azure Table Storage. Covers best practices, architecture & design patterns, limits & quotas, security, configuration, and integrations & coding patterns. 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
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=learn-agent-skill&accept=text/markdown. Returns Markdown.
Category Index
| Category | Lines | Description |
|---|
| Best Practices | L34-L38 | Guidance on designing scalable table schemas, partition/row key strategies, throughput optimization, and performance tuning patterns for Azure Table storage. |
| Architecture & Design Patterns | L39-L48 | Designing Azure Table Storage schemas: partition/row key strategies, query-optimized models, handling relationships, efficient updates, and common design patterns/anti-patterns. |
| Limits & Quotas | L49-L53 | Scalability limits, throughput targets, partition/key design, and performance best practices for Azure Table storage workloads. |
| Security | L54-L59 | Managing access to Azure Table data using Microsoft Entra ID and Azure RBAC, including assigning roles and configuring identity-based authorization. |
| Configuration | L60-L65 | Configuring Azure Table Storage monitoring: enabling metrics and logs, understanding available telemetry, and setting up alerts for performance, availability, and diagnostics. |
| Integrations & Coding Patterns | L66-L69 | Using Azure PowerShell to manage Table storage: create/delete tables, insert/query/update/delete entities, and script common data operations. |
Best Practices
Architecture & Design Patterns
Limits & Quotas
Security
Configuration
Integrations & Coding Patterns
