azure-messaging
npx machina-cli add skill microsoft/GitHub-Copilot-for-Azure/azure-messaging --openclawAzure Messaging SDK Troubleshooting
Quick Reference
| Property | Value |
|---|---|
| Services | Azure Event Hubs, Azure Service Bus |
| MCP Tools | mcp_azure_mcp_eventhubs, mcp_azure_mcp_servicebus |
| Best For | Diagnosing SDK connection, auth, and message processing issues |
When to Use This Skill
- SDK connection failures, auth errors, or AMQP link errors
- Message lock lost, session lock, or send/receive timeouts
- Event processor or message handler stops processing
- SDK configuration questions (retry, prefetch, batch size)
MCP Tools
| Tool | Command | Use |
|---|---|---|
mcp_azure_mcp_eventhubs | Namespace/hub ops | List namespaces, hubs, consumer groups |
mcp_azure_mcp_servicebus | Queue/topic ops | List namespaces, queues, topics, subscriptions |
mcp_azure_mcp_monitor | logs_query | Query diagnostic logs with KQL |
mcp_azure_mcp_resourcehealth | get | Check service health status |
mcp_azure_mcp_documentation | Doc search | Search Microsoft Learn for troubleshooting docs |
Diagnosis Workflow
- Identify the SDK and version — Ask which language SDK and version the user is on
- Check resource health — Use
mcp_azure_mcp_resourcehealthto verify the namespace is healthy - Review the error message — Match against language-specific troubleshooting guide
- Look up documentation — Use
mcp_azure_mcp_documentationto search Microsoft Learn for the error or topic - Check configuration — Verify connection string, entity name, consumer group
- Recommend fix — Apply remediation, citing documentation found
Connectivity Troubleshooting
See Service Troubleshooting Guide for ports, WebSocket fallback, IP firewall, private endpoints, and service tags.
SDK Troubleshooting Guides
References
Use mcp_azure_mcp_documentation to search Microsoft Learn for latest guidance. See Service Troubleshooting Guide for network and service-level docs.
Source
git clone https://github.com/microsoft/GitHub-Copilot-for-Azure/blob/main/plugin/skills/azure-messaging/SKILL.mdView on GitHub Overview
Diagnose and resolve issues across Azure Event Hubs and Azure Service Bus SDKs. This guide helps you troubleshoot connection failures, authentication errors, message processing problems, and SDK configuration questions.
How This Skill Works
The troubleshooting process uses MCP tools to identify the language SDK and version, verify resource health, analyze error messages, and fetch language-specific guidance from Microsoft Learn. It then checks configuration like connection strings and entity names and guides remediation with concrete steps and references.
When to Use It
- SDK connection failures, auth errors, or AMQP link errors
- Message lock lost, session lock, or send/receive timeouts
- Event processor or message handler stops processing
- SDK configuration questions (retry, prefetch, batch size)
- General Azure Messaging SDK troubleshooting for Event Hubs and Service Bus
Quick Start
- Step 1: Identify the language SDK and version you are using.
- Step 2: Check resource health with mcp_azure_mcp_resourcehealth and review the error message.
- Step 3: Look up the relevant Microsoft Learn guidance with mcp_azure_mcp_documentation and verify configuration before retrying.
Best Practices
- Identify the language SDK and version you’re using before troubleshooting
- Check the namespace/resource health with mcp_azure_mcp_resourcehealth
- Match the error message to a language-specific troubleshooting guide
- Look up Microsoft Learn guidance with mcp_azure_mcp_documentation
- Verify critical configuration (connection string, entity name, consumer group) and re-test after fixes
Example Use Cases
- Troubleshooting an Event Hubs Python SDK not receiving messages
- Debugging a Service Bus Java SDK authentication error
- Fixing an AMQP link error in a Node.js Event Hubs client
- Addressing message lock lost during a long-running event processor
- Investigating a send timeout in a .NET Service Bus sender
