---
name: Azure Messaging
slug: azure-messaging
category: DevOps
description: Azure Messaging provides troubleshooting guidance for Azure Event Hubs and Service Bus SDKs, covering connection failures, authentication errors, and message processing issues. Use it when diagnosing AMQP errors, lock timeouts, or event processor failures.
github: "https://github.com/microsoft/azure-skills/tree/main/skills/azure-messaging"
language: Python
stars: 1390
forks: 231
install: "npx degit https://github.com/microsoft/azure-skills/tree/main/skills/azure-messaging ~/.claude/skills/azure-messaging"
installs_to: ~/.claude/skills/azure-messaging
source_path: skills/azure-messaging/SKILL.md
collection_size: 25
category_size: 798
collection_url: "https://dirskills.com/collections/microsoft/azure-skills"
added: 2026-08-19T07:27:43.307Z
last_synced: 2026-08-19T07:27:43.307Z
canonical_url: "https://dirskills.com/skills/azure-messaging"
---

# Azure Messaging

Azure Messaging provides troubleshooting guidance for Azure Event Hubs and Service Bus SDKs, covering connection failures, authentication errors, and message processing issues. Use it when diagnosing AMQP errors, lock timeouts, or event processor failures.

**Install:**

```bash
npx degit https://github.com/microsoft/azure-skills/tree/main/skills/azure-messaging ~/.claude/skills/azure-messaging
```

## README

# 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

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