# Diagnose Azure Messaging SDK Issues

Azure Event Hubs and Service Bus failures can be difficult to isolate across SDK, configuration, and service layers. This skill guides focused checks using Azure resources, diagnostic logs, and current Microsoft Learn guidance.

## Install

```bash
npx skillstore add microsoft/azure-messaging
```

## Metadata

- Status: approved
- Slug: microsoft-azure-messaging
- Version: 0.0.0-placeholder
- Author version: 0.0.0-placeholder
- Skillstore revision: r2
- Version status: valid
- Tree hash: 00fa3f7470c48a2b3e8de82d95f47ea66a4c2b0479aace69777fd16b86c79d36
- Author: microsoft
- GitHub username: microsoft
- License: MIT
- Repository: https://github.com/microsoft/github-copilot-for-azure/tree/main/plugin/skills/azure-messaging/
- Ref: ebdfe608f5de2b66ff37ab4af12af8ac4f5e8006
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands
- Quality score: 71
- Public page: https://skillstore.pages.dev/skills/microsoft-azure-messaging
- Manifest: https://skillstore.pages.dev/api/skills/microsoft-azure-messaging/manifest

## Capabilities

- Guides diagnosis of Azure Event Hubs and Service Bus SDK connection failures.
- Covers authentication, AMQP link, timeout, reconnection, and receiver issues.
- Checks namespace health and lists messaging entities through Azure MCP tools.
- Queries Azure diagnostic logs with KQL through the monitoring MCP tool.
- Reviews retry, prefetch, batch size, entity, consumer group, and checkpoint settings.
- Searches Microsoft Learn and cites relevant troubleshooting guidance.

## Use Cases

- Resolve SDK exceptions: Identify likely causes and focused checks for connection, authentication, AMQP, timeout, and lock errors.
- Investigate processing incidents: Correlate service health, diagnostic logs, and SDK configuration when receivers or event processors stop handling messages.
- Support Azure messaging users: Review resource topology, configuration details, and current Microsoft guidance before recommending remediation.

## Prompt Templates

### Identify an SDK error

```
Diagnose this Azure messaging error: [error]. The service is [Event Hubs or Service Bus], and the SDK language is [language].
```

### Investigate connection failures

```
Investigate repeated [timeout, disconnect, or AMQP error] for [namespace and entity]. Check resource health, configuration, and current Microsoft Learn guidance.
```

### Analyze message processing

```
Analyze why [processor or receiver] stops handling messages. Review locks, sessions, retries, prefetch, batch size, checkpoints, and relevant diagnostic logs.
```

### Correlate production failures

```
Build a diagnosis for [incident]. Correlate SDK version, timestamps, KQL log evidence, resource health, configuration, and documented remediation.
```

## Limitations

- Requires configured Azure MCP tools and sufficient Azure permissions for live resource checks.
- Does not include the detailed messaging guides stored in the separate azure-diagnostics skill.
- Does not change Azure resources or application code through the documented workflow.
- Focuses on Azure Event Hubs and Service Bus SDK issues, not all Azure messaging products.

## Best Practices

- Provide the service, SDK language, SDK version, full error message, and approximate failure time.
- Grant Azure MCP tools only the permissions needed to inspect the relevant subscription and namespace.
- Validate proposed changes in a nonproduction environment and cite current Microsoft Learn guidance.

## Anti Patterns

- Do not share connection strings, access keys, tokens, or message payloads in prompts.
- Do not change retry, prefetch, or batch settings without measuring processing behavior.
- Do not assume every SDK error is an Azure outage before checking application and network evidence.

## Security Audit

- Audited at: 2026-07-23T18:53:33.899\+00:00
- Summary: All ten static findings are false positives caused by Markdown backticks around MCP tool names, operation names, and a path. No shell or Ruby execution is present in SKILL.md. The documented Azure MCP workflow can read cloud resource metadata and diagnostic logs, so users should apply least-privilege access.

## Stats

- Views: 142
- Downloads: 10
- Favorites: 0
- Popularity score: 0