skill-apim-skuv1-investigator

Investigate Azure API Management SKUv1 incidents using ICM, alerts, and Kusto telemetry.

1|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/azaslonov/skills --skill skill-apim-skuv1-investigator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-apim-skuv1-investigator
Source: https://github.com/azaslonov/skills/tree/main/skill-apim-skuv1-investigator
Command: npx skills add https://github.com/azaslonov/skills --skill skill-apim-skuv1-investigator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a structured, hypothesis-driven approach to investigate and resolve incidents affecting Azure API Management SKUv1 (Dedicated/Classic) services, minimizing downtime and service disruption.

Core Features & Use Cases

  • ICM Incident Investigation: Analyze and troubleshoot Azure API Management SKUv1 incidents.
  • Health Monitoring: Investigate alerts related to Gateway, Portal, and Proxy health.
  • Root Cause Analysis: Perform diagnostics using Kusto telemetry and VM/VMSS data.
  • Mitigation & Escalation: Guide through immediate actions, rollbacks, and team escalations.
  • Use Case: When an ICM incident is raised for an APIM SKUv1 service experiencing gateway unavailability, this Skill helps systematically diagnose the cause, from DNS issues to VM health, and suggests appropriate mitigation steps.

Quick Start

Investigate ICM incident 503176286 for APIM service ApiM-Prd-Us-Sales-B2C-Public.

Frequently Asked Questions about skill-apim-skuv1-investigator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I troubleshoot Azure API Management SKUv1 incidents using ICM and Kusto?

To troubleshoot Azure API Management SKUv1 incidents, this Skill analyzes ICM incidents and Kusto telemetry using a structured methodology to identify root causes across service contexts, VM/VMSS diagnostics, and health monitoring alerts.

What is the best way to diagnose APIM SKUv1 gateway unavailability?

Diagnosing APIM SKUv1 gateway unavailability is best handled by following a hypothesis-driven methodology that checks DNS issues, VM health, and Kusto telemetry to pinpoint the failure and suggest immediate mitigation steps.

How does root cause analysis work for Azure API Management Dedicated service alerts?

Root cause analysis for Azure API Management Dedicated service alerts works by gathering service context and systematically analyzing Kusto telemetry and VM/VMSS data to isolate the underlying issue and determine rollback or escalation procedures.

Can I use this structured investigation approach for both APIM Dedicated and Classic tiers?

Yes, you can use this structured investigation approach for both APIM Dedicated and Classic tiers, as the methodology specifically targets Azure API Management SKUv1 services to minimize downtime and service disruption.

When do I need to escalate an APIM SKUv1 incident after initial diagnostics?

You need to escalate an APIM SKUv1 incident after initial diagnostics when immediate actions and rollbacks fail to resolve the issue, requiring team escalation guided by the structured findings from Kusto telemetry and VM/VMSS data.