Analyze Azure resource health, diagnose issues from logs and telemetry, and create a remediation plan for identified problems.

Azure Resource Health & Issue Diagnosis This workflow analyzes a specific Azure resource to assess its health status, diagnose potential issues using logs and telemetry data, and develop a comprehensive remediation plan for any problems discovered. Prerequisites Azure MCP server configured and authenticated Target Azure resource identified (name and optionally resource group/subscription) Resource must be deployed and running to generate logs/telemetry Prefer Azure MCP tools ( azmcp ) over direct Azure CLI when available Workflow Steps Step 1: Get Azure Best Practices Action : Retrieve diagnostic and troubleshooting best practices Tools : Azure MCP best practices tool Process : 1. Load Best Practices : Execute Azure best practices tool to get diagnostic guidelines Focus on health monitoring, log analysis, and issue resolution patterns Use these practices to inform diagnostic approach and remediation recommendations Step 2: Resource Discovery & Identification Action : Locate and identify the target Azure resource Tools : Azure MCP tools + Azure CLI fallback Process : 1. Resource Lookup : If only resource name provided: Search across subscriptions using azmcp subscription list Use az resource list name <resource name to find matching resources If multiple matches found, prompt user to specify subscription/resource group Gather detailed resource information: Resource type and current status Location, tags, and configuration Associated services and dependencies 2. Resource Type Detection : Identify resource type to determine appropriate diagnostic approach: Web Apps/Function Apps : Application logs, performance metrics, dependency tracking Virtual Machines : System logs, performance counters, boot diagnostics Cosmos DB : Request metrics, throttling, partition statistics Storage Accounts : Access logs, performance metrics, availability SQL Database : Query performance, connection logs, resource utilization Application Insights : Application telemetry, exceptions, dependencies Key Vault : Access logs, certificate status, secret usage Service Bus : Message metrics, dead letter queues, throughput Step 3: Health Status Assessment Action : Evaluate current resource health and availability Tools : Azure MCP monitoring tools + Azure CLI Process : 1. Basic Health Check : Check resource provisioning state and operational status Verify service availability and responsiveness Review recent deployment or configuration changes Assess current resource utilization (CPU, memory, storage, etc.) 2. Service Specific Health Indicators : Web Apps : HTTP response codes, response times, uptime Databases : Connection success rate, query performance, deadlocks Storage : Availability percentage, request success rate, latency VMs : Boot diagnostics, guest OS metrics, network connectivity Functions : Execution success rate, duration, error frequency Step 4: Log & Telemetry Analysis Action : Analyze logs and telemetry to identify issues and patterns Tools : Azure MCP monitoring tools for Log Analytics queries Process : 1. Find Monitoring Sources : Use azmcp monitor workspace list to identify Log Analytics workspaces Locate Application Insights instances associated with the resource Identify relevant log tables using azmcp monitor table list 2. Execute Diagnostic Queries : Use azmcp monitor log query with targeted KQL queries based on resource type: General Error Analysis : Performance Analysis : Application Specific Queries : 3. Pattern Recognition : Identify recurring error patterns or anomalies Correlate errors with deployment times or configuration changes Analyze performance trends and degradation patterns Look for dependency failures or external service issues Step 5: Issue Classification & Root Cause Analysis Action : Categorize identified issues and determine root causes Process : 1. Issue Classification : Critical : Service unavailable, data loss, security breaches High : Performance degradation, intermittent failures, high error rates Medium : Warnings, suboptimal configuration, minor performance issues Low : Informational alerts, optimization opportunities 2. Root Cause Analysis : Configuration Issues : Incorrect settings, missing dependencies Resource Constraints : CPU/memory/disk limitations, throttling Network Issues : Connectivity problems, DNS resolution, firewall rules Application Issues : Code bugs, memory leaks, inefficient queries External Dependencies : Third party service failures, API limits Security Issues : Authentication failures, certificate expiration 3. Impact Assessment : Determine business impact and affected users/systems Evaluate data integrity and security implications Assess recovery time objectives and priorities Step 6: Generate Remediation Plan Action : Create a comprehensive plan to address identified issues Process : 1. Immediate Actions (Critical issues): Emergency fixes to restore service availability Temporary workarounds to mitigate impact Escalation procedures for complex issues 2. Short term Fixes (High/Medium issues): Configuration adjustments and resource scaling Application updates and patches Monitoring and alerting improvements 3. Long term Improvements (All issues): Architectural changes for better resilience Preventive measures and monitoring enhancements Documentation and process improvements 4. Implementation Steps : Prioritized action items with specific Azure CLI commands Testing and validation procedures Rollback plans for each change Monitoring to verify issue resolution Step 7: User Confirmation & Report Generation Action : Present findings and get approval for remediation actions Process : 1. Display Health Assessment Summary : 2. Generate Detailed Report : bash Critical fixes to restore service [Azure CLI commands with explanations] bash Performance and reliability improvements [Azure CLI commands with explanations] bash Architectural and preventive measures [Azure CLI commands and configuration changes] Error Handling Resource Not Found : Provide guidance on resource name/location specification Authentication Issues : Guide user through Azure authentication setup Insufficient Permissions : List required RBAC roles for resource access No Logs Available : Suggest enabling diagnostic settings and waiting for data Query Timeouts : Break down analysis into smaller time windows Service Specific Issues : Provide generic health assessment with limitations noted Success Criteria ✅ Resource health status accurately assessed ✅ All significant issues identified and categorized ✅ Root cause analysis completed for major problems ✅ Actionable remediation plan with specific steps provided ✅ Monitoring and prevention recommendations included ✅ Clear prioritization of issues by business impact ✅ Implementation steps include validation and rollback procedures

azure-resource-health-diagnose