Skills

Chapter 20 of 37

Azure Messaging

Troubleshoot and resolve issues with Azure Messaging SDKs for Event Hubs and Service Bus.

1 minute · 247 words · 7 sections

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_resourcehealth to verify the namespace is healthy
Review the error message — Match against language-specific troubleshooting guide
Look up documentation — Use mcp_azure_mcp_documentation to 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_documentation to search Microsoft Learn for latest guidance.

Install this repository

$ npx skills add microsoft/azure-skills

» /plugin marketplace add microsoft/azure-skills

Skills install per repository, not per chapter — the CLI has no documented per-skill form, so we do not print one.

About this skill

Trigger

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 verbatim description from this skill’s front matter — the string an agent matches on to decide whether to load it.

Licence: MIT
Also published for: GitHub — collapsed into this chapter because the copies are the same skill.
Source: skills/azure-messaging/SKILL.md

Colophon for this issue

Colophon

How this issue was made

Source

github.com/microsoft/azure-skills, branch main, last pushed 7 August 2026.

Licence

MIT — the text of every chapter is reproduced unmodified, frontmatter included, under the upstream licence.

Discovery

37 chapters found by walking the repository tree for SKILL.md, not by matching a directory convention. 6 distinct layouts observed: skills/*/SKILL.md, skills/azure-app-onboard/*/SKILL.md, skills/azure-kubernetes/*/SKILL.md, skills/microsoft-foundry/*/SKILL.md, skills/microsoft-foundry/models/deploy-model/*/SKILL.md, skills/microsoft-foundry/models/*/SKILL.md.

Duplicates collapsed

37 mirror copies folded into their canonical chapter — republished for GitHub. Copies match on content hash and on position once a leading per-agent prefix is stripped, because the same skill is routinely shipped under a dozen agent directories with a dozen different hashes.

Issue colours

Resolved from a curated brand profile — hue 251°, chroma 0.167. Two accent tones are generated per issue and each is proven against its own ground before it ships: a single accent that passes AA on both light and dark paper is arithmetically impossible.

Heading repairs

1 repair applied to this chapter so the document has one h1 and no skipped levels:

Shifted “7 headings” from h1 to h2 so the chapter title is the only h1.

Spec compliance

6 editorial notes across 3 of 37 chapters. They are printed in the margin of each chapter rather than as errors here.

Deploy — 2 notes
Prepare — 2 notes
Scaffold — 2 notes

Images

Images inside a chapter come from the upstream repository. Where the author gave no alternative text we mark the image decorative rather than inventing a description — a plausible caption we made up is worse than none for the reader who depends on it.

Marketplace

A plugin manifest is published at .claude-plugin/marketplace.json by Microsoft, declaring 1 plugin. It is read for editorial metadata only — never as the skill index, which is always the repository tree.

Signal

Install counts come from skills.sh. They measure downloads, not quality, and an unranked repository is not an unread one.

Agent surfaces

The whole issue is available as one markdown document at /microsoft/azure-skills.md, and each chapter at its own .md URL.

Publication

Set by Skills Docs from the source repository. Body text is Literata at the reader’s chosen size and measure; code is Geist Mono. Nothing on this page was written by us except this paragraph.

Azure Messaging SDK Troubleshooting

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

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)

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

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_resourcehealth to verify the namespace is healthy

Review the error message — Match against language-specific troubleshooting guide

Look up documentation — Use mcp_azure_mcp_documentation to search Microsoft Learn for the error or topic

Check configuration — Verify connection string, entity name, consumer group

Recommend fix — Apply remediation, citing documentation found

Connectivity, SDK, and auth troubleshooting guides are located in the azure-diagnostics skill under troubleshooting/messaging/.

Use mcp_azure_mcp_documentation to search Microsoft Learn for latest guidance.