Azure Messaging Debugger

Azure Messaging SDK Troubleshooting

by microsoft · MIT license · ★ 1,532 on GitHub

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.

---
name: azure-messaging
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."
license: MIT
metadata:
  author: Microsoft
  version: "1.2.1"
---

# 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 |

Overview

Connectivity, SDK, and auth troubleshooting guides are located in the azure-diagnostics skill under troubleshooting/messaging/.

Manual install (npx, ZIP)

Claude Codenpx skills add microsoft/azure-skills --skill azure-messaging -g -a claude-code

Claude Code (degit)npx degit microsoft/azure-skills/skills/azure-messaging#main ~/.claude/skills/azure-messaging

Claude.ai / desktopZip the folder and upload it under Settings → Capabilities → Skills.

Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

SKILL.md3.2 KB

Read SKILL.md here

microsoft/main1 file shown

SKILL.md3.2 KB

Browse every file on GitHub↗

SKILL.md

Show the full text57 lines

azure-messaging/SKILL.md57 lines · 3.2 KB

PreviewCode

Outline

RawView on GitHub

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_resourcehealth to verify the namespace is healthy
Review the error message — Match against language-specific troubleshooting guide
Look up documentation — Use mcp_azure_mcp_documentation to 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_documentation to 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	1. 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	2. Check resource health — Use `mcp_azure_mcp_resourcehealth` to verify the namespace is healthy
45	3. Review the error message — Match against language-specific troubleshooting guide
46	4. Look up documentation — Use `mcp_azure_mcp_documentation` to search Microsoft Learn for the error or topic
47	5. Check configuration — Verify connection string, entity name, consumer group
48	6. 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.