mcpbeat

Azure Messaging

microsoft/azure-messaging

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.

820 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
1
copies elsewhere
how many repositories repackaged it
6 d ago
last touched
this folder, not the whole repository

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/microsoft/skills --skill azure-messaging

The instruction itself

7 sections, as written by the author

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.

Repackaged in 1 other repositories

same content, different owner
microsoft/azure-skills open on GitHub →

How to use it

Copy the folder

Take microsoft/azure-messaging from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.