azure-messaging
microsoft/azure-skills
Troubleshoot Azure Event Hubs and Service Bus SDK issues: connections, auth, AMQP errors, and message processing
What is azure-messaging?
azure-messaging is a skill for coding agents that guides diagnosis and resolution of Azure Messaging SDK problems across Event Hubs and Service Bus. It covers connection failures, AMQP link errors, authentication issues, message/session lock problems, duplicate events, checkpoint resets, and SDK configuration. The skill uses MCP tools to inspect namespace health, query diagnostic logs, and search Microsoft Learn documentation, then recommends targeted fixes.
- Diagnoses SDK connection failures and AMQP link detach or detach-forced errors
- Troubleshoots message lock lost, lock expired, lock renewal failures, and batch lock timeouts
- Handles session lock lost, session lock expired, and session receiver errors
- Identifies idle timeout, connection inactivity, and slow reconnection issues
- Investigates duplicate events, checkpoint offset resets, and event processor stalls
- Guides SDK configuration for retry, prefetch, batch size, and receive batch behavior
How to install azure-messaging
npx skills add https://github.com/microsoft/azure-skills --skill azure-messaging- Azure Event Hubs or Service Bus namespace already provisioned
- Access to the namespace connection string or Azure credentials
- MCP tools available: mcp_azure_mcp_eventhubs, mcp_azure_mcp_servicebus, mcp_azure_mcp_monitor, mcp_azure_mcp_resourcehealth, mcp_azure_mcp_documentation
- azure-diagnostics skill installed (contains messaging troubleshooting guides under troubleshooting/messaging/)
- Knowledge of which SDK language and version is in use (Python, Java, JavaScript, .NET)
How to use azure-messaging
- 1.Install the skill: npx skills add https://github.com/microsoft/azure-skills --skill azure-messaging
- 2.Describe the error or symptom to your coding agent (e.g., 'message lock expired during batch processing')
- 3.The agent identifies the SDK language and version from context or asks if unclear
- 4.The agent checks namespace health using mcp_azure_mcp_resourcehealth
- 5.The agent matches the error against language-specific guides in azure-diagnostics troubleshooting/messaging/
- 6.The agent searches Microsoft Learn via mcp_azure_mcp_documentation for the specific error or topic
- 7.The agent queries diagnostic logs with mcp_azure_mcp_monitor if deeper investigation is needed
- 8.Apply the recommended configuration change or code fix cited from documentation
Use cases
- Event Hub consumer stops receiving messages and needs reconnection diagnosis
- Service Bus message lock expires during batch processing causing dead-lettering
- AMQP link detach errors appear intermittently in a .NET or Java SDK application
- Authentication errors prevent a Python or JavaScript client from connecting to a namespace
- Event processor host checkpoints reset unexpectedly causing duplicate event processing
- Developers building Event Hubs consumer or producer applications
- Developers integrating Azure Service Bus queues, topics, or subscriptions
- Engineers debugging AMQP-level connectivity issues in Azure messaging clients
- Teams using azure-sdk across Python, Java, JavaScript, or .NET for messaging
- Anyone troubleshooting SDK configuration or message processing reliability
azure-messaging FAQ
Yes. It covers both services, including queues, topics, subscriptions, consumer groups, and event processors.
The skill references Python, Java, JavaScript, and .NET SDK scenarios explicitly.
It diagnoses issues using MCP tools and recommends fixes with documentation references; it does not automatically change Azure resources.
Yes. The detailed language-specific troubleshooting guides are stored in azure-diagnostics under troubleshooting/messaging/, so that skill should also be installed.
Yes. AMQP link detach, detach-forced, idle timeout, and connection inactivity are explicitly covered scenarios.
Full instructions (SKILL.md)
Source of truth, from microsoft/azure-skills.
name: azure-messaging description: "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." license: MIT metadata: author: Microsoft version: "1.1.2"
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_resourcehealthto verify the namespace is healthy - Review the error message — Match against language-specific troubleshooting guide
- Look up documentation — Use
mcp_azure_mcp_documentationto 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_documentationto search Microsoft Learn for latest guidance.
Related skills
More from microsoft/azure-skills and the wider catalog.
finetuning
Fine-tune models on Azure AI Foundry with SFT, DPO, or RFT training methods.
azure-ai
Azure AI services skill for Search, Speech, OpenAI, and Document Intelligence in coding agents
azure-deploy
Execute Azure deployments for prepared applications with built-in error recovery and validation.
azure-diagnostics
Debug Azure production issues using AppLens, Azure Monitor, resource health, and systematic triage.
azure-prepare
Generate Azure deployment infrastructure (Bicep/Terraform, azure.yaml, Dockerfiles) for new or existing apps
azure-storage
Azure Storage skill: Blob, File Shares, Queue, Table, and Data Lake with access tier guidance and lifecycle management