azure-messaging

Diagnose and resolve Azure Event Hubs and Service Bus SDK connection, authentication, and message processing issues.

Updated May 12, 2026
One-click install
npx skills add https://github.com/sohamda/apex-try-out-demo-repo --skill azure-messaging-sohamda
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: azure-messaging
Source: https://github.com/sohamda/apex-try-out-demo-repo/tree/main/.archive/_archived_skills/azure-messaging
Command: npx skills add https://github.com/sohamda/apex-try-out-demo-repo --skill azure-messaging-sohamda

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Developers hitting connection failures, authentication errors, AMQP link errors, message lock losses, or processor stalls with Azure Event Hubs and Service Bus SDKs often struggle to find the right fix across scattered documentation. This Skill provides a structured diagnosis workflow with language-specific troubleshooting guides. ## Core Features & Use Cases - Guided Diagnosis Workflow: A six-step process from identifying the SDK version through checking resource health, matching error messages, and recommending documented fixes. - Language-Specific SDK Guides: Troubleshooting references for Event Hubs and Service Bus across .NET, Java, JavaScript, and Python, covering common exceptions, logging setup, and retry configuration. - MCP Tool Integration: Uses Azure MCP tools for Event Hubs, Service Bus, Monitor log queries, resource health checks, and Microsoft Learn documentation search. - Use Case: When an Event Hubs consumer stops receiving messages or a Service Bus processor throws MessageLockLost, follow the workflow to check namespace health, match the error against the SDK guide, and apply the documented remediation. ## Quick Start Ask the agent to troubleshoot your Event Hubs or Service Bus SDK error, providing the SDK language, version, and the exact error message you are seeing.

Frequently Asked Questions about azure-messaging

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I troubleshoot Azure Event Hubs SDK connection failures?▼

Verify the connection string from the Azure portal, confirm AMQP ports 5671 and 5672 are open, and check namespace health with the resource health tool. If ports are blocked, switch to WebSockets over port 443 using the SDK's transport type setting.

How to fix Service Bus MessageLockLost errors?▼

MessageLockLost occurs when processing exceeds the lock duration or the AMQP link detaches from transient network issues. Reduce processing time, use AutoLockRenewer in Python or auto-lock renewal in other SDKs, and verify network stability.

Does the Event Hubs SDK support WebSockets when AMQP ports are blocked?▼

Yes, all four SDKs support AMQP over WebSockets on port 443. Use EventHubsTransportType.AmqpWebSockets in .NET, AmqpTransportType.AMQP_WEB_SOCKETS in Java, TransportType.AmqpOverWebsocket in Python, or webSocketOptions in JavaScript.

Why does my Event Hubs processor stop receiving messages?▼

Consumer disconnection is expected during load balancing when instances scale. If it persists over five minutes without scaling, check for soft delete or blob versioning on the checkpoint storage account, which cause delays during partition ownership negotiation.

Should I use DefaultAzureCredential in production for Service Bus?▼

No, DefaultAzureCredential is intended for local development only because its fallback chain adds latency and unpredictability. Use ManagedIdentityCredential in production with least-privilege RBAC roles such as Azure Service Bus Data Sender or Receiver.

How do I enable logging for Azure messaging SDKs?▼

Python uses the logging module on azure.eventhub or azure.servicebus loggers, JavaScript uses the DEBUG or AZURE_LOG_LEVEL environment variables, Java configures SLF4J loggers, and .NET uses standard event source filtering. Enable AMQP frame tracing for deeper diagnostics.