v0.0.0-placeholderContent revision r2 Medium Riskโ๏ธ External commands
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.
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Agent request
Review the Skillstore skill "azure-messaging" from https://skillstore.io/skills/microsoft-azure-messaging.md and its manifest at https://skillstore.io/api/skills/microsoft-azure-messaging/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.
Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
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.
The skill directs Azure MCP tools to list messaging resources, check service health, and query diagnostic logs using the user's cloud permissions. These read operations may expose subscription topology and operational data.
The MCP tool table and diagnosis workflow explicitly describe resource listing, health checks, and KQL log queries. The documented operations are read-oriented but require authorized Azure access.
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
microsoft. (2026). azure-messaging security audit report (audit version 5) [Author version 0.0.0-placeholder]. Skillstore. https://skillstore.io/skills/microsoft-azure-messaging/audits/5
BibTeX citation
@techreport{microsoft-microsoft-azure-messaging-2026,
author = {microsoft},
title = {azure-messaging security audit report (audit version 5)},
institution = {Skillstore},
year = {2026},
number = {5},
url = {https://skillstore.io/skills/microsoft-azure-messaging/audits/5},
note = {Author version 0.0.0-placeholder}
}
CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "azure-messaging security audit report (audit version 5)"
version: "0.0.0-placeholder"
type: report
authors:
- name: "microsoft"
date-released: "2026-07-23"
url: "https://skillstore.io/skills/microsoft-azure-messaging/audits/5"
identifiers:
- type: other
value: "skillstore:microsoft-azure-messaging:audit:5"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this scoreEvidence Confidence: High
55
Architecture
90
Maintainability
87
Content
69
Community
91
Spec Compliance
What You Can Build
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.
Try These Prompts
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.
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.
Avoid
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.
Frequently Asked Questions
Which Azure services does this skill cover?
It covers Azure Event Hubs and Azure Service Bus SDK troubleshooting.
Which SDK languages can it troubleshoot?
The workflow is language-neutral and can guide troubleshooting when you provide the SDK language, version, and error.
Does it require access to my Azure subscription?
Live health, resource, and log checks require configured Azure MCP tools with appropriate permissions.
Can it modify queues, topics, hubs, or application code?
The documented workflow performs diagnosis and recommends fixes. It does not describe resource or code changes.
What information should I provide?
Provide the service, namespace, entity, SDK language, SDK version, error text, timestamps, and relevant configuration without secrets.
Can it diagnose message lock and session lock errors?
Yes. It covers lock loss, lock expiration, renewal failures, session errors, prefetch, and batch processing behavior.