Loading source
Pulling the file list, source metadata, and syntax-aware rendering for this listing.
Source from repo
Configure Azure messaging services—Service Bus, Event Grid, Event Hubs, and Queue Storage—for async workflows
Files
Skill
Size
Entrypoint
Format
Open file
Syntax-highlighted preview of this file as included in the skill package.
SKILL.md
1---2name: azure-messaging3description: "Troubleshoot and resolve issues with Azure Messaging SDKs for Event Hubs and Service Bus. Covers connection failures, authentication errors, message processing issues, and SDK configuration problems. WHEN: event hub SDK error, service bus SDK issue, messaging connection failure, AMQP error, event processor host issue, message lock lost, message lock expired, lock renewal, lock renewal batch, send timeout, receiver disconnected, SDK troubleshooting, azure messaging SDK, event hub consumer, service bus queue issue, topic subscription error, enable logging event hub, service bus logging, eventhub python, servicebus java, eventhub javascript, servicebus dotnet, event hub checkpoint, event hub not receiving messages, service bus dead letter, batch processing lock, session lock expired, idle timeout, connection inactive, link detach, slow reconnect, session error, duplicate events, offset reset, receive batch."4license: MIT5metadata:6author: Microsoft7version: "0.0.0-placeholder"8---910# Azure Messaging SDK Troubleshooting1112## Quick Reference1314| Property | Value |15|----------|-------|16| **Services** | Azure Event Hubs, Azure Service Bus |17| **MCP Tools** | `mcp_azure_mcp_eventhubs`, `mcp_azure_mcp_servicebus` |18| **Best For** | Diagnosing SDK connection, auth, and message processing issues |1920## When to Use This Skill2122- SDK connection failures, auth errors, or AMQP link errors23- Idle timeout, connection inactivity, or slow reconnection after disconnect24- AMQP link detach or detach-forced errors25- Message lock lost, message lock expired, lock renewal failures, or batch lock timeouts26- Session lock lost, session lock expired, or session receiver errors27- Event processor or message handler stops processing28- Duplicate events or checkpoint offset resets29- SDK configuration questions (retry, prefetch, batch size, receive batch behavior)3031## MCP Tools3233| Tool | Command | Use |34|------|---------|-----|35| `mcp_azure_mcp_eventhubs` | Namespace/hub ops | List namespaces, hubs, consumer groups |36| `mcp_azure_mcp_servicebus` | Queue/topic ops | List namespaces, queues, topics, subscriptions |37| `mcp_azure_mcp_monitor` | `logs_query` | Query diagnostic logs with KQL |38| `mcp_azure_mcp_resourcehealth` | `get` | Check service health status |39| `mcp_azure_mcp_documentation` | Doc search | Search Microsoft Learn for troubleshooting docs |4041## Diagnosis Workflow42431. **Identify the SDK and version** — Check the prompt for SDK and version clues; if not stated, proceed with diagnosis and ask later if needed442. **Check resource health** — Use `mcp_azure_mcp_resourcehealth` to verify the namespace is healthy453. **Review the error message** — Match against language-specific troubleshooting guide464. **Look up documentation** — Use `mcp_azure_mcp_documentation` to search Microsoft Learn for the error or topic475. **Check configuration** — Verify connection string, entity name, consumer group486. **Recommend fix** — Apply remediation, citing documentation found495051## Troubleshooting Guides5253Connectivity, SDK, and auth troubleshooting guides are located in the azure-diagnostics skill under `troubleshooting/messaging/`.5455## References5657- Use `mcp_azure_mcp_documentation` to search Microsoft Learn for latest guidance.