azure-messaging

Diagnose connection, authentication, and message processing issues in Azure Event Hubs and Service Bus SDKs.

Updated Jul 20, 2026
One-click install
npx skills add https://github.com/merceralex397-collab/alex-stack --skill azure-messaging-merceralex397-collab
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: azure-messaging
Source: https://github.com/merceralex397-collab/alex-stack/tree/main/dev/azure-profile/azure-skills-main/azure-skills-main/.github/plugins/azure-skills/skills/azure-messaging
Command: npx skills add https://github.com/merceralex397-collab/alex-stack --skill azure-messaging-merceralex397-collab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Azure Messaging SDK errors like connection failures, AMQP link detaches, message lock expirations, and stalled event processors are hard to diagnose without deep platform knowledge. This Skill provides a structured troubleshooting workflow for Event Hubs and Service Bus SDK issues across Python, Java, JavaScript, and .NET. ## Core Features & Use Cases - Error Diagnosis: Match SDK error messages (message lock lost, session lock expired, idle timeout, link detach) against language-specific troubleshooting guidance. - Resource Health Checks: Use Azure MCP tools to verify namespace health, list hubs, queues, topics, and query diagnostic logs with KQL. - Configuration Review: Validate connection strings, entity names, consumer groups, retry policies, prefetch, and batch settings. - Use Case: Your Event Hub consumer stops receiving messages with duplicate events after reconnect. The Skill checks resource health, identifies checkpoint offset reset behavior, and recommends the fix with documentation citations. ## Quick Start Ask the assistant to troubleshoot why your Service Bus receiver keeps throwing message lock expired errors during batch processing.

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?▼

Start by checking namespace health with the Azure resource health tool, then verify the connection string, entity name, and consumer group. Match the specific error message against the language-specific troubleshooting guide and search Microsoft Learn for the error.

Why does Service Bus throw message lock expired errors?▼

Message lock expired errors occur when processing exceeds the lock duration or lock renewal fails, especially in batch processing. The Skill helps identify whether to increase lock duration, enable auto lock renewal, or reduce batch processing time.

Which Azure SDK languages does this troubleshooting cover?▼

The troubleshooting guidance covers Azure Messaging SDKs for Python, Java, JavaScript, and .NET for both Event Hubs and Service Bus. Error matching uses language-specific troubleshooting guides referenced through the azure-diagnostics skill.

Can I diagnose Event Hub consumer not receiving messages?▼

Yes, the workflow checks resource health, consumer group configuration, and checkpoint offset state to find why an event processor stopped receiving. It also addresses duplicate events and offset resets after reconnection.

What tools are needed to query Service Bus diagnostic logs?▼

The Skill uses the Azure MCP monitor tool to run KQL queries against diagnostic logs, plus MCP tools for Event Hubs and Service Bus to list namespaces, queues, topics, and subscriptions during diagnosis.