Skills azure-observability
๐Ÿ“ฆ

azure-observability

Content revision r1 Safe ๐Ÿ”‘ Env variablesโš™๏ธ External commands๐ŸŒ Network access

Monitor Azure Apps with Observability References

Azure teams need quick guidance for metrics, traces, logs, alerts, and workbook workflows. This skill organizes Azure Monitor, Application Insights, Log Analytics, KQL, and SDK references for Claude, Codex, and Claude Code users.

Supports: Claude Codex Code(CC)
๐Ÿ“Š 74 Adequate

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-observability" from https://skillstore.io/skills/microsoft-azure-observability.md and its manifest at https://skillstore.io/api/skills/microsoft-azure-observability/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

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.

Test it

Using "azure-observability". Which Azure service should I use to investigate slow API requests?

Expected outcome:

Use Application Insights for request duration and dependency traces. Use Log Analytics with KQL when you need deeper correlation across logs, exceptions, and infrastructure data.

Using "azure-observability". I need a quick query for recent application failures.

Expected outcome:

The skill can suggest an AppExceptions query filtered to the last hour, projecting time, message, and stack trace, then sorting by newest events.

Using "azure-observability". How should I start TypeScript telemetry setup?

Expected outcome:

Use the Azure Monitor OpenTelemetry package, configure the Azure Monitor exporter options, and keep the Application Insights connection string in a secure environment variable.

Security Audit

Safe
v4 โ€ข 7/6/2026 Open versioned report

The static alerts are false positives caused by Markdown code formatting, read-oriented Azure documentation examples, and normal Azure Monitor SDK configuration. No prompt injection, covert exfiltration intent, destructive command guidance, or automatic network behavior was found in the reviewed files.

9
Files scanned
329
Lines analyzed
0
Review items
0
False positives ignored
No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.
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
Security Assessment

Copy report link

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

Markdown badge

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

HTML badge

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

Embed card

<iframe src="https://skillstore.io/embed/skills/microsoft-azure-observability.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-observability security audit report (audit version 4) [Author version unspecified]. Skillstore. https://skillstore.io/skills/microsoft-azure-observability/audits/4

BibTeX citation

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

CITATION.cff

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

Skillstore Score

Why this score Evidence Confidence: High
36
Architecture
85
Maintainability
87
Content
69
Community
91
Spec Compliance

What You Can Build

Investigate production telemetry

Find the right Azure service, query pattern, and metric source for errors, latency, or infrastructure symptoms.

Add application instrumentation

Use OpenTelemetry and Application Insights references to plan basic tracing, logging, and sampling setup.

Prepare operational reporting

Choose Log Analytics, KQL, alerts, and workbooks guidance for incident reviews and service health reporting.

Try These Prompts

Choose an Azure observability service
Help me choose between Azure Monitor, Application Insights, Log Analytics, alerts, and workbooks for this monitoring task: [describe task].
Draft a KQL investigation query
Create a KQL query for Log Analytics that investigates [error, latency, or resource symptom] over [time range]. Explain which table and fields to review.
Plan Application Insights instrumentation
Review my application stack: [language and framework]. Recommend Azure Monitor OpenTelemetry or Application Insights setup steps, sampling guidance, and secure configuration practices.
Design an incident observability workflow
Design an Azure observability workflow for [service name]. Include metrics, traces, logs, KQL queries, alerts, workbook views, and SDK references for ongoing operations.

Best Practices

  • Confirm the workspace, subscription, and time range before running any telemetry query.
  • Use projections, aggregations, and limits in KQL to reduce noisy or expensive results.
  • Store connection strings and credentials outside prompts, logs, and checked-in files.

Avoid

  • Do not paste production secrets or full connection strings into prompts.
  • Do not run broad log queries without a time filter or row limit.
  • Do not rely on metrics alone when traces and logs are needed for root cause analysis.

Frequently Asked Questions

Does this skill execute Azure commands?
No. It provides references, example commands, KQL patterns, and SDK guidance for users or agents to apply deliberately.
Which Azure services does it cover?
It covers Azure Monitor, Application Insights, Log Analytics, alerts, workbooks, OpenTelemetry, Monitor Query, and Log Ingestion references.
Can it help write KQL queries?
Yes. It includes common KQL examples for exceptions, request performance, and resource usage that can be adapted to a workspace.
Does it require Azure MCP?
Azure MCP is preferred when available, but the skill also includes Azure CLI and SDK reference material.
Is it suitable for production incident response?
It can support investigation planning and query drafting, but users must validate commands, scopes, and results in their Azure environment.
How should secrets be handled?
Use environment variables, managed identity, Key Vault, or approved secret storage. Do not expose connection strings in prompts or logs.

Developer Details

Author

microsoft

License

MIT

Skillstore revision

r1

Version notice

The author did not declare a version.

Ref

b8ca75d2c0a7e7102978993058777d82b8ab2610

Maintenance freshness

7/18/2026

Usage

7 downloads ยท 105 views