Azure Messaging SDK Troubleshooting

SkillCommunication

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, 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.

Available today. Use it from your connected AI after setup.

Connect ahel once, and every AI you use reads what you have installed.

Then ask your AI: use the Azure Messaging SDK Troubleshooting skill

What this skill tells your AI

The instructions your AI receives, as published by olivomarco/vbd-copilot in skills/azure-messaging/SKILL.md and read by ahel’s review.

Quick Reference

PropertyValue
ServicesAzure Event Hubs, Azure Service Bus
MCP Toolsmcp_azure_mcp_eventhubs, mcp_azure_mcp_servicebus
Best ForDiagnosing SDK connection, auth, and message processing issues

When to Use This Skill

  • SDK connection failures, auth errors, or AMQP link errors
  • Message lock lost, session lock, or send/receive timeouts
  • Event processor or message handler stops processing
  • SDK configuration questions (retry, prefetch, batch size)

MCP Tools

ToolCommandUse
mcp_azure_mcp_eventhubsNamespace/hub opsList namespaces, hubs, consumer groups
mcp_azure_mcp_servicebusQueue/topic opsList namespaces, queues, topics, subscriptions
mcp_azure_mcp_monitorlogs_queryQuery diagnostic logs with KQL
mcp_azure_mcp_resourcehealthgetCheck service health status
mcp_azure_mcp_documentationDoc searchSearch Microsoft Learn for troubleshooting docs

Diagnosis Workflow

  1. Identify the SDK and version — Ask which language SDK and version the user is on
  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

Connectivity Troubleshooting

See Service Troubleshooting Guide for ports, WebSocket fallback, IP firewall, private endpoints, and service tags.

SDK Troubleshooting Guides

References

Use mcp_azure_mcp_documentation to search Microsoft Learn for latest guidance. See Service Troubleshooting Guide for network and service-level docs.

Signals

GitHub stars
67
Forks
44
Last commit
Jul 2026

ahel review

  • S4info
    community integration — published by olivomarco, not azure

Automated review, not a security audit. Ruleset v1.

ahel recommends instead

Advanced
Catalog kind
skill
Gateway key
azure-messaging-olivomarco
Source
github.com/olivomarco/vbd-copilot