Azure Messaging SDK Troubleshooting

Quick Reference

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

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

Connectivity Troubleshooting

See Service Troubleshooting Guide for ports, WebSocket fallback, IP firewall, private endpoints, and service tags.

SDK Troubleshooting Guides

• Event Hubs: Python | Java | JS | .NET
• Service Bus: Python | Java | JS | .NET

References

Use mcp_azure_mcp_documentation to search Microsoft Learn for latest guidance. See Service Troubleshooting Guide for network and service-level docs.