Azure Messaging SDK Troubleshooting skill
Troubleshoot and resolve issues with Azure Messaging SDKs for Event Hubs and Service Bus.
by microsoft·MIT license·★ 1,532 Stars on the repo·GitHub ↗
Use now
npx degit microsoft/azure-skills/skills/azure-messaging#main ~/.claude/skills/azure-messagingChecked ·commit main
Files of Azure Messaging SDK Troubleshooting
SKILL.md
Show the full text57 lines
Azure 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
- Idle timeout, connection inactivity, or slow reconnection after disconnect
- AMQP link detach or detach-forced errors
- Message lock lost, message lock expired, lock renewal failures, or batch lock timeouts
- Session lock lost, session lock expired, or session receiver errors
- Event processor or message handler stops processing
- Duplicate events or checkpoint offset resets
- SDK configuration questions (retry, prefetch, batch size, receive batch behavior)
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 — Check the prompt for SDK and version clues; if not stated, proceed with diagnosis and ask later if needed
- 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
Troubleshooting Guides
Connectivity, SDK, and auth troubleshooting guides are located in the azure-diagnostics skill under troubleshooting/messaging/.
References
- Use
mcp_azure_mcp_documentationto search Microsoft Learn for latest guidance.
| 1 | |
| 2 | name azure-messaging |
| 3 | description "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." |
| 4 | license MIT |
| 5 | metadata |
| 6 | author Microsoft |
| 7 | version "1.2.1" |
| 8 | |
| 9 | |
| 10 | # Azure Messaging SDK Troubleshooting |
| 11 | |
| 12 | ## Quick Reference |
| 13 | |
| 14 | | 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 | |
| 19 | |
| 20 | ## When to Use This Skill |
| 21 | |
| 22 | SDK connection failures, auth errors, or AMQP link errors |
| 23 | Idle timeout, connection inactivity, or slow reconnection after disconnect |
| 24 | AMQP link detach or detach-forced errors |
| 25 | Message lock lost, message lock expired, lock renewal failures, or batch lock timeouts |
| 26 | Session lock lost, session lock expired, or session receiver errors |
| 27 | Event processor or message handler stops processing |
| 28 | Duplicate events or checkpoint offset resets |
| 29 | SDK configuration questions (retry, prefetch, batch size, receive batch behavior) |
| 30 | |
| 31 | ## MCP Tools |
| 32 | |
| 33 | | 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 | |
| 40 | |
| 41 | ## Diagnosis Workflow |
| 42 | |
| 43 | **Identify the SDK and version** — Check the prompt for SDK and version clues; if not stated, proceed with diagnosis and ask later if needed |
| 44 | **Check resource health** — Use `mcp_azure_mcp_resourcehealth` to verify the namespace is healthy |
| 45 | **Review the error message** — Match against language-specific troubleshooting guide |
| 46 | **Look up documentation** — Use `mcp_azure_mcp_documentation` to search Microsoft Learn for the error or topic |
| 47 | **Check configuration** — Verify connection string, entity name, consumer group |
| 48 | **Recommend fix** — Apply remediation, citing documentation found |
| 49 | |
| 50 | |
| 51 | ## Troubleshooting Guides |
| 52 | |
| 53 | Connectivity, SDK, and auth troubleshooting guides are located in the azure-diagnostics skill under `troubleshooting/messaging/`. |
| 54 | |
| 55 | ## References |
| 56 | |
| 57 | Use `mcp_azure_mcp_documentation` to search Microsoft Learn for latest guidance. |
Discussion
Alternatives
API and interface designGuides stable API and interface design. Use when designing APIs, module boundaries, or any public interface. Use when creating REST or GraphQL endpoints, defining type contracts between modules, or establishing boundaries between frontend and backend.
Context7Pulls up-to-date, version-specific library docs and code examples into the prompt so the AI stops inventing old APIs.Context7 Documentation LookupFetch up-to-date documentation and code examples for any library, framework, SDK, CLI tool, or cloud service. Use whenever the user asks about a specific library — even well-known ones like React, Next.js, Prisma, Express, Tailwind, Django, or Spring Boot — because training data may not reflect recent API changes or version updates. Always use for: API syntax questions, configuration options, version migration issues, "how do I" questions mentioning a library name, debugging that involves library-specific behavior, setup instructions, and CLI tool usage. Use even when you think you know the answer. Do not rely on training data for API details, signatures, or configuration options — they are frequently out of date. Prefer this over web search for library documentation.
Adaptyv Bio Foundry APIHow to use the Adaptyv Bio Foundry API and Python SDK for protein experiment design, submission, and results retrieval. Use this skill whenever the user mentions Adaptyv, Foundry API, protein binding assays, protein screening experiments, BLI/SPR assays, thermostability assays, or wants to submit protein sequences for experimental characterization. Also trigger when code imports `adaptyv`, `adaptyv_sdk`, or `FoundryClient`, or references `foundry-api-public.adaptyvbio.com`.Browse more free Claude skills or everything in Development.