Skills azure-diagnostics

📦

azure-diagnostics

Name: azure-diagnostics
Author: microsoft

v0.0.0-placeholder Content revision r2 High Risk 🌐 Network access📁 Filesystem access🔑 Env variables⚙️ External commands

Diagnose Azure Production Issues

Azure production incidents can span services, logs, metrics, credentials, and network paths. This skill guides structured triage with Azure Monitor, AppLens, KQL, CLI, and service-specific checks.

Supports: Claude Codex Code(CC)

⚠️ 38 Poor

Stop for confirmation before installing.

Review the plan and obtain explicit user consent before changing files.

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

Review the Skillstore skill "azure-diagnostics" from https://skillstore.io/skills/microsoft-azure-diagnostics.md and its manifest at https://skillstore.io/api/skills/microsoft-azure-diagnostics/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/microsoft-azure-diagnostics.md Signed manifest GET /api/skills/microsoft-azure-diagnostics/manifest Signed lockfile GET /api/skills/microsoft-azure-diagnostics/lockfile

Test it

Using "azure-diagnostics". An App Service returns 503 errors after a deployment.

Expected outcome:

Resource health is normal, so review deployment history, startup logs, health checks, and recent configuration changes.
Likely causes include startup failure, port mismatch, missing settings, or locked deployment files.
Confirm the cause before restarting, scaling, or changing configuration.

Using "azure-diagnostics". AKS pods remain Pending after a node pool change.

Expected outcome:

Check node readiness, scheduling events, resource requests, taints, tolerations, zone constraints, and persistent volume placement.
Separate capacity shortages from scheduling policy conflicts before modifying the node pool or workloads.

Using "azure-diagnostics". A Service Bus client reports intermittent AMQP timeouts.

Expected outcome:

Review Azure health, firewall rules, ports, proxy behavior, dropped packets, SDK version, retry policy, and connection reuse.
Treat transient disconnects separately from persistent authentication or network failures.

Security Audit

High Risk

v5 • 7/23/2026 Open versioned report

All 58 static alerts are contextual false positives from Markdown, placeholder endpoints, environment-selection examples, and diagnostic commands. However, SKILL.md contains a high-severity authority claim that resembles prompt injection and could improperly influence an agent's instruction hierarchy.

Files scanned

2,477

Lines analyzed

Review items

False positives ignored

Confirmed security concerns (1)

High

SKILL.md:12-14

Prompt Injection Attempt Detected

SKILL.md states "AUTHORITATIVE GUIDANCE — MANDATORY COMPLIANCE" and calls itself the "official source." This authority claim can pressure an agent to treat untrusted skill text as higher-priority instructions.

The quoted text explicitly asserts mandatory authority and official status. This matches the audit's prompt-injection criteria even though the surrounding troubleshooting content is legitimate.

Risk Factors

🌐 Network access (8)

references/app-service/README.md:97 references/container-apps/README.md:62 references/functions/README.md:64 troubleshooting/aks/networking.md:18 troubleshooting/messaging/azure-eventhubs-dotnet.md:48 troubleshooting/messaging/azure-eventhubs-java.md:47 troubleshooting/messaging/azure-eventhubs-py.md:53 troubleshooting/messaging/service-troubleshooting.md:20

📁 Filesystem access (2)

references/app-service/README.md:97 troubleshooting/aks/aks-troubleshooting.md:3

🔑 Env variables (16)

⚙️ External commands (13)

SKILL.md:60 SKILL.md:77-87 SKILL.md:87-92 SKILL.md:92-103 SKILL.md:103-108 SKILL.md:108-115 SKILL.md:115-125 SKILL.md:125-131 SKILL.md:131-135 SKILL.md:135-141 troubleshooting/messaging/auth-best-practices.md:16 troubleshooting/messaging/auth-best-practices.md:81 troubleshooting/messaging/auth-best-practices.md:87

Audited by: codex View Audit History →

Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report

Copy report link

https://skillstore.io/skills/microsoft-azure-diagnostics/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/microsoft-azure-diagnostics/security.svg)](https://skillstore.io/skills/microsoft-azure-diagnostics?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/microsoft-azure-diagnostics?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/microsoft-azure-diagnostics/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/microsoft-azure-diagnostics.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Academic citations (APA · BibTeX · CFF)

APA citation

microsoft. (2026). azure-diagnostics security audit report (audit version 5) [Author version 0.0.0-placeholder]. Skillstore. https://skillstore.io/skills/microsoft-azure-diagnostics/audits/5

BibTeX citation

@techreport{microsoft-microsoft-azure-diagnostics-2026,
  author = {microsoft},
  title = {azure-diagnostics security audit report (audit version 5)},
  institution = {Skillstore},
  year = {2026},
  number = {5},
  url = {https://skillstore.io/skills/microsoft-azure-diagnostics/audits/5},
  note = {Author version 0.0.0-placeholder}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "azure-diagnostics security audit report (audit version 5)"
version: "0.0.0-placeholder"
type: report
authors:
  - name: "microsoft"
date-released: "2026-07-23"
url: "https://skillstore.io/skills/microsoft-azure-diagnostics/audits/5"
identifiers:
  - type: other
    value: "skillstore:microsoft-azure-diagnostics:audit:5"
    description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: Medium

Architecture

Maintainability

Content

Community

Spec Compliance

What You Can Build

Triage a production incident

Correlate resource health, recent changes, logs, and metrics before selecting a remediation.

Debug application failures

Investigate deployment errors, health probes, cold starts, runtime settings, and dependency failures.

Diagnose platform connectivity

Analyze AKS, Event Hubs, and Service Bus identity, networking, scaling, and client behavior.

Try These Prompts

Start basic incident triage

Diagnose this Azure issue: [symptom]. The affected service is [service], the resource is [resource], and the problem began at [time].

Build an evidence plan

Build a diagnostic plan for [resource]. Use [available logs or metrics], separate evidence from hypotheses, and list only read-only commands first.

Analyze a service failure

Troubleshoot [failure] in [Azure service]. Compare identity, configuration, networking, resource health, recent changes, and service-specific failure patterns.

Correlate a complex incident

Investigate [incident] across [resources]. Correlate deployments, resource health, KQL results, identity, dependencies, and network paths. Rank root causes by evidence.

Best Practices

Start with resource health and recent changes before collecting detailed logs.
Use read-only queries first, then request approval before any resource change.
Redact secrets, connection strings, tokens, customer data, and sensitive log fields from shared outputs.

Avoid

Do not run combined remediation commands before replacing placeholders and validating scope.
Do not treat a single error message as root cause without supporting logs or metrics.
Do not expose credentials or paste unrestricted production logs into prompts.