Agent-Skills azure-impact-reporting

Expert knowledge for Azure Impact Reporting development including troubleshooting, configuration, and integrations & coding patterns. Use when wiring Impact Reporting to Monitor alerts, Logic Apps, HPC node health, Service Health, or its insights API, and other Azure Impact Reporting related development tasks. Not for Azure Carbon Optimization (use azure-carbon-optimization), Azure Cost Management (use azure-cost-management), Azure Monitor (use azure-monitor), Azure Policy (use azure-policy).

install
source · Clone the upstream repo
git clone https://github.com/MicrosoftDocs/Agent-Skills
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/MicrosoftDocs/Agent-Skills "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/azure-impact-reporting" ~/.claude/skills/microsoftdocs-agent-skills-azure-impact-reporting && rm -rf "$T"
manifest: skills/azure-impact-reporting/SKILL.md
source content

Azure Impact Reporting Skill

This skill provides expert guidance for Azure Impact Reporting. Covers troubleshooting, configuration, and integrations & coding patterns. It combines local quick-reference content with remote documentation fetching capabilities.

How to Use This Skill

IMPORTANT for Agent: Use the Category Index below to locate relevant sections. For categories with line ranges (e.g.,

L35-L120
), use
read_file
with the specified lines. For categories with file links (e.g.,
[security.md](security.md)
), use
read_file
on the linked reference file

IMPORTANT for Agent: If

metadata.generated_at
is more than 3 months old, suggest the user pull the latest version from the repository. If
mcp_microsoftdocs
tools are not available, suggest the user install it: Installation Guide

This skill requires network access to fetch documentation content:

  • Preferred: Use
    mcp_microsoftdocs:microsoft_docs_fetch
    with query string
    from=learn-agent-skill
    . Returns Markdown.
  • Fallback: Use
    fetch_webpage
    with query string
    from=learn-agent-skill&accept=text/markdown
    . Returns Markdown.

Category Index

CategoryLinesDescription
TroubleshootingL31-L35Diagnosing and fixing Azure Impact Reporting connector issues, including connection failures, data sync problems, configuration errors, and common troubleshooting steps.
ConfigurationL36-L42Configuring Azure Impact Reporting: creating alert connectors and retrieving valid impact and HPC Guest Health category values for correct classification.
Integrations & Coding PatternsL43-L49Patterns and APIs for integrating Impact Reporting with Azure Monitor alerts, Logic Apps, HPC VM node health, Service Health, and accessing insights via API and portal

Troubleshooting

TopicURL
Troubleshoot Azure Impact Reporting connectorshttps://learn.microsoft.com/en-us/azure/azure-impact-reporting/connectors-troubleshooting-guide

Configuration

TopicURL
Create Azure Impact Reporting connectors for alertshttps://learn.microsoft.com/en-us/azure/azure-impact-reporting/create-azure-monitor-connector
Use valid HPC Guest Health impact categorieshttps://learn.microsoft.com/en-us/azure/azure-impact-reporting/guest-health-impact-categories
Retrieve valid Azure Impact Reporting categorieshttps://learn.microsoft.com/en-us/azure/azure-impact-reporting/view-impact-categories

Integrations & Coding Patterns

TopicURL
Integrate Azure Monitor alerts with Impact Reportinghttps://learn.microsoft.com/en-us/azure/azure-impact-reporting/azure-monitor-connector
Use Logic Apps to send Azure impact reportshttps://learn.microsoft.com/en-us/azure/azure-impact-reporting/creating-logic-app
Report Azure workload impact via Service Health and APIhttps://learn.microsoft.com/en-us/azure/azure-impact-reporting/report-impact
View Azure Impact Reporting insights via API and portalhttps://learn.microsoft.com/en-us/azure/azure-impact-reporting/view-impact-insights