PluginBench
Skill
Official
Pass
Audit score 90

azure-messaging

microsoft/azure-skills

Troubleshoot Azure Event Hubs and Service Bus SDK issues—connection, auth, message processing, and configuration problems.

SourceView on skills.sh

What is azure-messaging?

Diagnoses and resolves issues with Azure Messaging SDKs for Event Hubs and Service Bus. Use this when facing connection failures, authentication errors, message lock timeouts, AMQP link errors, or message processing problems across Python, Java, JavaScript, and .NET implementations.

  • Diagnose SDK connection failures, authentication errors, and AMQP link detach issues
  • Resolve message lock lost/expired and lock renewal batch timeout problems
  • Troubleshoot event processor and message handler processing stops
  • Identify and fix idle timeout, slow reconnection, and session lock errors
  • Verify resource health and check SDK configuration (retry, prefetch, batch size)
  • Search Microsoft Learn documentation for language-specific troubleshooting guidance

How to install azure-messaging

npx skills add https://github.com/microsoft/azure-skills --skill azure-messaging
Claude Code
Cursor
Windsurf
Cline

How to use azure-messaging

  1. 1.Identify the SDK type (Event Hubs or Service Bus) and programming language from the error context
  2. 2.Use the resource health check to confirm the Azure namespace is healthy and operational
  3. 3.Match the error message against the language-specific troubleshooting guide in the skill documentation
  4. 4.Search Microsoft Learn via the documentation tool for the specific error code or symptom
  5. 5.Review and adjust SDK configuration settings (connection string, consumer group, batch size, retry policy)
  6. 6.Apply the recommended fix and verify message processing resumes

Use cases

Good for
  • Event Hub consumer stops receiving messages or checkpoint offset resets unexpectedly
  • Service Bus queue receiver encounters 'message lock expired' or 'session lock lost' errors
  • AMQP connection drops after idle timeout or link detach-forced error occurs
  • Batch message processing fails due to lock renewal timeout during high-load scenarios
  • Service Bus topic subscription or Event Hub consumer group configuration validation
Who it's for
  • Backend engineers troubleshooting Azure messaging SDK issues
  • DevOps teams diagnosing production Event Hubs or Service Bus failures
  • Developers implementing event-driven architectures with Python, Java, JavaScript, or .NET SDKs
  • Cloud architects validating messaging configuration and retry policies

azure-messaging FAQ

What SDKs and languages does this skill cover?

Event Hubs and Service Bus SDKs for Python, Java, JavaScript, and .NET. The skill provides language-specific troubleshooting guides and configuration recommendations for each.

How do I know if my issue is a connection problem or a message processing problem?

Use the diagnosis workflow: check resource health first, then review the error message. Connection errors typically mention AMQP, link detach, or timeout; message processing errors mention lock lost, checkpoint, or handler failures.

Can this skill fix my code, or does it only diagnose?

The skill diagnoses issues, recommends fixes based on Microsoft Learn documentation, and suggests configuration changes. You apply the fixes to your code or infrastructure.

What if my error message doesn't match the troubleshooting guides?

Use the documentation search tool to find the error code or symptom on Microsoft Learn. The skill can also help you gather diagnostic logs and check resource health to narrow down the root cause.

Does this skill work with both Event Hubs and Service Bus?

Yes. The skill covers both services and their SDKs. Specify which service you're using for more targeted troubleshooting guidance.

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.2.1"

Azure Messaging SDK Troubleshooting

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
  • 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

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