azure-monitor
Expert knowledge for Azure Monitor development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when working with Log Analytics, AMA/DCR pipelines, alerts/ITSM, Application Insights, or Prometheus/OpenTelemetry, and other Azure Monitor related development tasks. Not for Azure Network Watcher (use azure-network-watcher), Azure Service Health (use azure-service-health), Azure Defender For Cloud (use azure-defender-for-cloud), Azure Cost Management (use azure-co
npx skills add MicrosoftDocs/Agent-Skills --skill azure-monitor --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
The skill offers expert guidance for Azure Monitor, covering troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, integrations & coding patterns, and deployment. It is intended for tasks involving Log Analytics, AMA/DCR pipelines, alerts/ITSM, Application Insights, Prometheus/OpenTelemetry, and related Azure Monitor development work. It explicitly avoids guidance for other Azure services like Network Watcher, Service Health, Defender for Cloud, or Cost Management.
How it works
- It instructs the agent to use category-based navigation to locate relevant sections in the Azure Monitor content. When a category provides line ranges, the agent should read specific lines using read_file with the given lines. When a category provides file links, the agent should read the referenced file with read_file.
- It requires network access to fetch documentation content via the preferred mcp_microsoftdocs:microsoft_docs_fetch tool (query: from=learn-agent-skill) or, if unavailable, the fallback fetch_webpage tool (query: from=learn-agent-skill&accept=text/markdown).
- It includes a Category Index with sections such as Troubleshooting, Best Practices, Decision Making, Architecture & Design Patterns, Limits & Quotas, Security, Configuration, Integrations & Coding Patterns, and Deployment, each pointing to locations like L37-L107 or linked files (e.g., configuration.md, integrations.md, deployment.md).
- It recommends updating when metadata.generated_at is older than 3 months and to install mcp_microsoftdocs if needed.
When to use it
Use when working with Azure Monitor development tasks across Log Analytics, AMA/DCR pipelines, alerts/ITSM, Application Insights, or Prometheus/OpenTelemetry. It is not for Azure Network Watcher, Azure Service Health, Azure Defender For Cloud, or Azure Cost Management.
What it can touch
- Tools: claude-code, copilot, codex (as declared in the skill). The skill requires network access to fetch documentation via mcp_microsoftdocs:microsoft_docs_fetch or fetch_webpage.
- It uses read_file on specific category references or linked files as instructed in the Category Index.
Caveats
- License: CC-BY-4.0
- Requires network access to fetch documentation content; fallback available if primary tool is unavailable.
- Metadata freshness check: if metadata.generated_at is more than 3 months old, suggest pulling the latest version from the repository.
- Explicitly not providing guidance for non-listed Azure services as noted in the description.
# Azure Monitor Skill This skill provides expert guidance for Azure Monitor. Covers troubleshooting, best practices, decision making, architecture & design patterns, 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` w
- How to Use This Skill
- Category Index
- Troubleshooting
- Best Practices
- Decision Making
- Architecture & Design Patterns
- Limits & Quotas
- Security
What does the azure-monitor skill do?
Expert knowledge for Azure Monitor development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when working with Log Analytics, AMA/DCR pipelines, alerts/ITSM, Application Insights, or Prometheus/OpenTelemetry, and other Azure Monitor related development tasks. Not for Azure Network Watcher (use azure-network-watcher), Azure Service Health (use azure-service-health), Azure Defender For Cloud (use azure-defender-for-cloud), Azure Cost Management (use azure-co
How do I install it?
Run `npx skills add MicrosoftDocs/Agent-Skills --skill azure-monitor --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.