Azure Messaging
Diagnose and fix Azure Event Hubs and Service Bus SDK failures when messages stall, locks expire, or AMQP connections drop in production.
Overview
Azure Messaging is an agent skill for the Operate phase that troubleshoots Azure Event Hubs and Service Bus SDK connection, authentication, and message-processing failures.
Install
npx skills add https://github.com/microsoft/azure-skills --skill azure-messagingWhat is this skill?
- Decision trees for Event Hubs and Service Bus SDK errors across Python, Java, JavaScript, and .NET
- AMQP idle timeout, link detach, lock renewal, and Event Processor Host checkpoint guidance
- Logging enablement and MCP-aligned Azure Event Hubs / Service Bus investigation hooks
Adoption & trust: 363k installs on skills.sh; 1.2k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your app loses Service Bus locks, stops receiving Event Hub events, or spews AMQP errors and you cannot tell if the bug is credentials, networking, SDK settings, or processor checkpoints.
Who is it for?
Indie builders running Azure messaging in staging or production who need fast SDK-side triage before opening a support ticket.
Skip if: Greenfield architecture picks (Event Hubs vs Kafka), Terraform-only provisioning with no runtime errors, or non-Azure message brokers.
When should I use this skill?
Event Hub or Service Bus SDK errors, AMQP connection failures, lock lost/expired, send timeouts, receiver disconnects, checkpoint or dead-letter issues, or when enabling SDK logging for Azure messaging.
What do I get? / Deliverables
You get a structured diagnosis path—symptom tables, logging steps, and fix checks—aligned to your SDK language and whether the issue is Event Hubs or Service Bus.
- Ordered troubleshooting steps matched to Event Hubs vs Service Bus and your SDK language
- Logging and configuration change recommendations to validate root cause
Recommended Skills
Journey fit
Messaging SDK failures surface after systems are running—this skill targets live connection, auth, and processing errors rather than greenfield design. Canonical shelf is operate/errors because the content is structured troubleshooting for SDK exceptions, dead-letter behavior, and receiver disconnects.
How it compares
Use for procedural SDK troubleshooting in chat—not as a hosted MCP server; Azure MCP tools complement this skill when the agent can query namespaces.
Common Questions / FAQ
Who is azure-messaging for?
Solo and indie developers using Azure Event Hubs or Service Bus client SDKs in Python, Java, JavaScript, or .NET who need agent-guided diagnosis when messaging breaks in real environments.
When should I use azure-messaging?
Use it in Operate when you see connection failures, authentication errors, AMQP link detach, idle timeouts, lock renewal failures, missing events, dead-letter growth, or Event Processor Host checkpoint issues; it is not for initial product ideation or landing-page validation.
Is azure-messaging safe to install?
Review the Security Audits panel on this Prism page for license and ingestion signals; the skill may guide enabling logging and using Azure APIs—avoid pasting production secrets into prompts and scope MCP credentials least-privilege.
SKILL.md
READMESKILL.md - Azure Messaging
# 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 1. **Identify the SDK and version** — Check the prompt for SDK and version clues; if not stated, proceed with diagnosis and ask later if needed 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 ## 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.