skill
Connect Observability
Find or connect an Azure application's or Foundry agent's telemetry for an explicit observability, monitoring, alerting, health or operational diagnosis request. Confirm source scope and task-specific telemetry access; not generic app connection, resource creation or deployment readiness. Instrumentation/collection design can precede deployment; answer conceptual questions directly. No automatic provisioning or changes.
About
# Connect your application
This is an experimental, instruction-guided onboarding workflow. Copilot reuses available tools or guides an approved setup when they are missing. The host performs supported installation/configuration and skill loading; Azure enforces access. Do not invent discovery APIs or deterministic sibling-skill invocation.
## Standalone availability gate
For an admitted task, check availability before reading any cross-skill reference or loading a sibling. Individual installation may omit them. Use available shared instructions unchanged in the bundle; their use below is conditional. Unknown availability follows the missing-reference fallback. Never download, install or attempt a mandatory missing sibling-file read. Without coordinator guidance, continue this local mapping/readiness workflow using supplied evidence or existing approved bounded operations. Confirm actual schemas and retain scope/window, budgets and distinct access/coverage states. Skip optional SRE review without its complete shared contract. If a health, investigation or comparator skill is absent, return readiness and the precise handoff blocker plus the smallest permitted manual next step, not a health or recovery claim. New connections, reads and writes keep separate approvals.
## Current-request intent gate
Before any journey header, diagram, discovery, onboarding question or read, confirm the current request concerns telemetry, monitoring, alerts, operational health/failure/latency diagnosis or incident recovery. "My API is slow" is sufficient; generic "fix"/"slow" without application/operational context is not. Answer conceptual observability questions directly without onboarding or tools. Explicit instrumentation/collection/alert setup or design is relevant before deployment: select an applicable setup/design workflow instead of demanding a deployed target. No setup request grants provisioning, installation or edits. Resource/app/agent creation, model deployment, RBAC, subscription, cost and general coding/docs are unrelated absent an explicit observability purpose or actual failure diagnosis. If incidentally loaded, continue the normal task or appropriate available workflow with normal approvals: no observability labels, stepper, tools or questions, and no coordinator invocation. A topic switch ends presentation; prior investigation is not sticky. Resume only for a relevant current request. Ask one minimal question only for genuinely ambiguous operational intent, before any presentation or reads. An explicit specialist request stays direct; do not force the coordinator.
After this gate admits a telemetry-connection task, read [the contract](references/contract.md) before constructing mapping or readiness inputs. Setup/design requests use their applicable workflow instead.
Only for an admitted actionable observability task, at the top of substantive answers, show **Using:** `connect-observability` only when host-loaded and being followed, plus **Stage:** Connect your application. For local instruction review use **Instructions read:** and **host activation unverified** instead. Show **Discovered:** only for a relevant skill/tool/MCP actually found, including external skills; state its kind, fit and unverified prerequisites. Discovery/loading does not prove tool execution or grant access. Propose the concrete bounded next action and ask **Allow once** or **Continue with current capabilities** when permission is missing. Reuse already covered, unexpired approval within scope, destination and remaining budget; preserve declines. Installation, connections, sign-in and writes need separate approvals. Use **Planned tools:** before execution and **Tools used:** only afterward, with actual outcomes. Keep labels compact; never invent capabilities or a load.
When continuing a coordinated journey, inherit its Detect or Investigate focus. Before the first substantive mapping/approval response or a meaningful transition, read the [journey indicator](references/shared/journey-indicator.md) and show its fenced Mermaid stepper below the header. Mapping is not a fifth stage. Use text fallback for reported rendering failure; never run an SVG renderer. An explicit standalone connection request still gets no forced journey diagram.
Python is optional for read-only onboarding through existing host tools. It is required for this package's deterministic local validation, readiness classification, and mapping load/save commands. A missing helper runtime must not be confused with missing Azure access.
## 1. Establish intent and available operations
Follow [the tool-prerequisite guide](references/tools.md) when required operations are missing, visible only as unresolved routers or denied at a source. It gives the smallest next setup/access step while keeping installation and bounded-read approvals separate. Sourced VS Code and Copilot CLI routes are available; fresh-client installation and live access remain unverified.
Keep the
Install
Run this command
git clone https://github.com/microsoft/azure-skills && cp -r azure-skills/.github/plugins/azure-observability/skills/connect-observability ~/.claude/skills/Works with
Manual steps
Clone the repository and copy the `.github/plugins/azure-observability/skills/connect-observability` folder into your Claude skills directory. Compatible with Claude Code, Cursor, Codex, and any Agent Skills-compatible agent.
Frequently asked questions
What is the Connect Observability skill?
Find or connect an Azure application's or Foundry agent's telemetry for an explicit observability, monitoring, alerting, health or operational diagnosis request. Confirm source scope and task-specific telemetry access; not generic app connection, resource creation or deployment readiness. Instrumentation/collection design can precede deployment; answer conceptual questions directly. No automatic provisioning or chan…
How do I install Connect Observability?
Run this in your terminal:
git clone https://github.com/microsoft/azure-skills && cp -r azure-skills/.github/plugins/azure-observability/skills/connect-observability ~/.claude/skills/Which AI tools does Connect Observability work with?
It works with claude_app, claude_code, claude_api, cursor, codex, windsurf, cline, zed.
Who made Connect Observability?
Microsoft, released under the MIT license.
Is Connect Observability free?
Yes, it is free to use under the MIT license.
npx skills add vercel-labs/agent-browser
npx skills add mattpocock/skills
npx skills add heygen-com/hyperframes
npx skills add mattpocock/skills
npx skills add designed-by-ai/skills
npx skills add mattpocock/skills
Audit before you install
Run any source through our checks - AI visibility, security, performance, and stack detection.
AI Agent / MCP Server Tester
ai testing
Automated Web Security Scan
security
AI Content Quality Test
arabic content
Site Stack Detector
migration
PageSpeed Analyzer
performance
AI SEO / AEO / GEO Audit
ai visibility
llms.txt Generator
ai visibility
Schema / JSON-LD Builder
ai visibility
Readability Score
arabic content
AI Cost Calculator
ai testing
Headline Analyzer
arabic content