Systematic diagnosis and remediation for Azure production issues using AppLens, Azure Monitor, and resource health checks.
Works with
Covers Container Apps, Function Apps, and AKS clusters with service-specific troubleshooting guides for image pulls, cold starts, health probes, invocation failures, and node/pod issues
Includes AppLens MCP integration for AI-powered root cause analysis and Azure Monitor MCP for KQL-based log and metric queries
Provides a five-step diagnostic flow: identify sympt
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionazure-diagnosticsExecute the skills CLI command in your project's root directory to begin installation:
Fetches azure-diagnostics from microsoft/GitHub-Copilot-for-Azure and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate azure-diagnostics. Access via /azure-diagnostics in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
180
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
180
stars
AUTHORITATIVE GUIDANCE — MANDATORY COMPLIANCE
This document is the official source for debugging and troubleshooting Azure production issues. Follow these instructions to diagnose and resolve common Azure service problems systematically.
Activate this skill when user wants to:
| Service | Common Issues | Reference |
|---|---|---|
| Container Apps | Image pull failures, cold starts, health probes, port mismatches | container-apps/ |
| Function Apps | App details, invocation failures, timeouts, binding errors, cold starts, missing app settings | functions/ |
| AKS | Cluster access, nodes, kube-system, scheduling, crash loops, ingress, DNS, upgrades |
AKS Troubleshooting |
# Check resource health
az resource show --ids RESOURCE_ID
# View activity log
az monitor activity-log list -g RG --max-events 20
# Container Apps logs
az containerapp logs show --name APP -g RG --follow
# Function App logs (query App Insights traces)
az monitor app-insights query --apps APP-INSIGHTS -g RG \
--analytics-query "traces | where timestamp > ago(1h) | order by timestamp desc | take 50"
For AI-powered diagnostics, use:
mcp_azure_mcp_applens
intent: "diagnose issues with <resource-name>"
command: "diagnose"
parameters:
resourceId: "<resource-id>"
Provides:
- Automated issue detection
- Root cause analysis
- Remediation recommendations
For querying logs and metrics:
mcp_azure_mcp_monitor
intent: "query logs for <resource-name>"
command: "logs_query"
parameters:
workspaceId: "<workspace-id>"
query: "<KQL-query>"
See kql-queries.md for common diagnostic queries.
mcp_azure_mcp_resourcehealth
intent: "check health status of <resource-name>"
command: "get"
parameters:
resourceId: "<resource-id>"
# Check specific resource health
az resource show --ids RESOURCE_ID
# Check recent activity
az monitor activity-log list -g RG --max-events 20
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
microsoft/GitHub-Copilot-for-Azure
microsoft/GitHub-Copilot-for-Azure
microsoft/azure-skills
membranedev/application-skills
microsoft/azure-skills
davila7/claude-code-templates
azure-diagnostics fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
azure-diagnostics is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Solid pick for teams standardizing on skills: azure-diagnostics is focused, and the summary matches what you get after install.
azure-diagnostics has been reliable in day-to-day use. Documentation quality is above average for community skills.
Registry listing for azure-diagnostics matched our evaluation — installs cleanly and behaves as described in the markdown.
Registry listing for azure-diagnostics matched our evaluation — installs cleanly and behaves as described in the markdown.
Solid pick for teams standardizing on skills: azure-diagnostics is focused, and the summary matches what you get after install.
azure-diagnostics reduced setup friction for our internal harness; good balance of opinion and flexibility.
azure-diagnostics reduced setup friction for our internal harness; good balance of opinion and flexibility.
I recommend azure-diagnostics for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
showing 1-10 of 37