Azure Messaging
MicrosoftOfficialCreated by Microsoft
- Skill
- Tool integration
- Cloud and DevOps
- MIT
- No issues found
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
The Azure Messaging skill provides a structured approach to diagnosing and resolving common issues encountered when using Azure Event Hubs and Service Bus SDKs. It integrates with specific MCP tools to verify resource health, query diagnostic logs, and search official documentation, helping developers address connectivity failures, AMQP errors, and message lock management problems efficiently.
What it does
- Diagnoses SDK connection failures, authentication errors, and AMQP link issues.
- Troubleshoots message processing problems including lock expiration, session errors, and duplicate events.
- Verifies Azure resource health status using integrated monitoring tools.
- Queries diagnostic logs via KQL to identify root causes of messaging failures.
- Searches official Microsoft Learn documentation for specific error codes and configuration guidance.
- Assists in validating SDK configurations such as retry policies, prefetch counts, and batch sizes.
When to use it
- When your application encounters connection timeouts or receiver disconnection errors.
- When message processing stops unexpectedly or locks are lost prematurely.
- When debugging AMQP link detach or session-related errors in Service Bus.
- When investigating unexpected duplicate events or checkpoint offset resets.
- When you need to verify if an Azure messaging namespace is experiencing service-side health issues.
Advantages
- Provides a standardized, repeatable workflow for complex messaging issues.
- Directly integrates with diagnostic and documentation tools for faster resolution.
- Covers a wide range of SDK-specific scenarios across multiple programming languages.
- Reduces manual effort in searching for troubleshooting patterns and configuration best practices.
Usage examples
- “My .NET application is throwing a message lock lost exception on Service Bus. How do I fix this?”
- The agent will verify the resource health, check your current lock duration configuration, and suggest adjustments to your message processing loop or lock renewal logic.
- “I am seeing AMQP link detach errors in my Python Event Hub consumer. What should I check?”
- The agent will guide you through checking connection stability, reviewing logs for specific error codes, and verifying your SDK configuration for idle timeouts.
Install
Download the skill as a ZIP:
https://mp-staging.autogineer.com/agent-skills/microsoft/azure-messaging/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip azure-messaging.zip -d .agents/skills
Documentation by Microsoft
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 healthyReview the error message — Match against language-specific troubleshooting guide
Look up documentation — Use
mcp_azure_mcp_documentationto search Microsoft Learn for the error or topicCheck 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.
Files
- ATTRIBUTION.mdAdded by AutoGineer977 B
- LICENSELicence file added by AutoGineer1.1 KiB
- SKILL.md3.2 KiB
Requirements and compatibility
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Security
No issues found by our static scan· No issues found
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Created by
- Microsoft
- Publisher
- Microsoft (Official)
- Source
- microsoft/skills · .github/plugins/azure-skills/skills/azure-messaging · commit 0696600
- Licence
- MIT License (redistribution allowed)
- LICENSE (added by AutoGineer from .github/plugins/azure-skills/LICENSE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
- Also distributed in
- microsoft/azure-skills
AutoGineer is not affiliated with or endorsed by Microsoft.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download azure-messaging.zip