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

Category	Lines	Description
Troubleshooting	L31-L35	Diagnosing and fixing Azure Impact Reporting connector failures and resolving Azure HPC Guest Health Reporting issues, errors, and data/health reporting problems.
Configuration	L36-L42	Configuring Azure Impact Reporting: creating alert connectors and retrieving valid impact and HPC Guest Health category values for correct classification.
Integrations & Coding Patterns	L43-L49	Patterns and examples for integrating Impact Reporting with Azure Monitor alerts, Logic Apps, diagnostic logs, Service Health, and APIs (sending, attaching data, and viewing insights).

Troubleshooting

Topic	URL
Troubleshoot Azure Impact Reporting connectors	https://learn.microsoft.com/en-us/azure/azure-impact-reporting/connectors-troubleshooting-guide

Configuration

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

Integrations & Coding Patterns

Topic	URL
Integrate Azure Monitor alerts with Impact Reporting	https://learn.microsoft.com/en-us/azure/azure-impact-reporting/azure-monitor-connector
Use Logic Apps to send Azure impact reports	https://learn.microsoft.com/en-us/azure/azure-impact-reporting/creating-logic-app
Attach diagnostic log files to Guest Health reports	https://learn.microsoft.com/en-us/azure/azure-impact-reporting/guest-health-log-upload
Report Azure workload impact via Service Health and API	https://learn.microsoft.com/en-us/azure/azure-impact-reporting/report-impact

Files1

1 files · 18.2 KB

Select a file to preview

Overall Score

68/100

Grade

C

Adequate

Safety

82

Quality

58

Clarity

75

Completeness

58

Summary

This skill provides expert guidance for Azure Impact Reporting development, covering troubleshooting, configuration, and integration patterns. It operates as a documentation reference index that directs agents to fetch remote Microsoft Learn documentation via network-accessible tools (mcp_microsoftdocs or fetch_webpage), with local quick-reference pointers organized by category.

Detected Capabilities

network accessdocumentation fetchingremote tool integration (mcp_microsoftdocs)webpage fetch

Trigger Keywords

Phrases that MCP clients use to match this skill to user intent.

azure impact reportingimpact reporting connectorconfigure impact categoriesazure hpc healthlogic apps impact reporting

Risk Signals

INFO

Network access to microsoft.learn documentation via external tool (mcp_microsoftdocs or fetch_webpage)

Line 16-19, compatibility section

INFO

External URL references to learn.microsoft.com for documentation retrieval

Category sections - Troubleshooting, Configuration, Integrations & Coding Patterns

Referenced Domains

External domains referenced in skill content, detected by static analysis.

github.comlearn.microsoft.com

Use Cases

Troubleshoot Azure Impact Reporting connector failures and HPC Guest Health reporting issues
Configure Impact Reporting alert connectors and validate impact category values
Integrate Impact Reporting with Azure Monitor, Logic Apps, and Service Health
Attach diagnostic logs to Guest Health impact reports
Access API patterns for reporting workload impact via Service Health

Quality Notes

Strength: Clear category index with line-range pointers and descriptive section headers enable efficient agent navigation
Strength: Explicit fallback mechanism documented (mcp_microsoftdocs preferred, fetch_webpage as fallback) with query string parameters
Strength: Scope is well-defined—explicitly excludes related skills (Azure Carbon Optimization, Cost Management, Monitor)
Strength: Provides version freshness check guidance (warn if metadata.generated_at > 3 months old)
Weakness: Category index table claims line ranges (L31-L35, etc.) but actual skill content ends at ~L49; line ranges are not populated with substantive quick-reference content, making the index decorative rather than functional
Weakness: No edge-case handling documented (e.g., what if mcp_microsoftdocs is unavailable and fetch_webpage also fails, or if network is offline)
Weakness: No examples of actual query outputs or expected response formats, limiting agent clarity on what 'done' looks like
Weakness: No guidance on how to interpret or act on retrieved documentation, or how to handle validation errors in category values

Model: claude-haiku-4-5-20251001Analyzed: Jun 26, 2026

Reviews

Add this skill to your library to leave a review.

No reviews yet

Be the first to share your experience.

azure-impact-reporting