Azure messaging
Skill microsoft/GitHub-Copilot-for-Azure/plugin/skills/azure-messaging
GitHub Copilot for Azure
npx -y skills add microsoft/GitHub-Copilot-for-Azure --skill azure-messagingAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
What its author says it does
Copied from the file, not written here
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.
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
3.2 KB, as published. Nobody here has run it
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.
Gives 0 of the 12 instructions most debug triage skills give
Counted across 839 of the 1,149 authors here whose files we hold, read 2026-08-06
- investigate root cause before proposing any fixin 102 of 839, across 65 files
- read error messages completelyin 90 of 839, across 48 files
- create a failing test case before fixingin 84 of 839, across 44 files
- reproduce the issue consistentlyin 82 of 839, across 40 files
- change one variable at a timein 82 of 839, across 42 files
- check recent changesin 74 of 839, across 35 files
- write the regression test before fixingin 74 of 839, across 36 files
- fix the root cause not the symptomin 60 of 839, across 43 files
- implement a single fix at a timein 59 of 839, across 20 files
- trace data flow backward to the sourcein 50 of 839, across 20 files
- remove all debug instrumentationin 49 of 839, across 13 files
- form a single hypothesisin 48 of 839, across 18 files
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.