What problem does it solve? Developers hitting connection failures, authentication errors, AMQP link errors, message lock losses, or processor stalls with Azure Event Hubs and Service Bus SDKs often struggle to find the right fix across scattered documentation. This Skill provides a structured diagnosis workflow with language-specific troubleshooting guides. ## Core Features & Use Cases - Guided Diagnosis Workflow: A six-step process from identifying the SDK version through checking resource health, matching error messages, and recommending documented fixes. - Language-Specific SDK Guides: Troubleshooting references for Event Hubs and Service Bus across .NET, Java, JavaScript, and Python, covering common exceptions, logging setup, and retry configuration. - MCP Tool Integration: Uses Azure MCP tools for Event Hubs, Service Bus, Monitor log queries, resource health checks, and Microsoft Learn documentation search. - Use Case: When an Event Hubs consumer stops receiving messages or a Service Bus processor throws MessageLockLost, follow the workflow to check namespace health, match the error against the SDK guide, and apply the documented remediation. ## Quick Start Ask the agent to troubleshoot your Event Hubs or Service Bus SDK error, providing the SDK language, version, and the exact error message you are seeing.