Skills azure-servicebus-dotnet
๐Ÿ“ฆ

azure-servicebus-dotnet

Content revision r2 Safe โš™๏ธ External commands๐ŸŒ Network access

Build Reliable Azure Service Bus .NET Workflows

Building reliable Azure Service Bus integrations requires correct authentication, settlement, batching, sessions, and error handling. This skill provides focused .NET patterns for common messaging workflows.

Supports: Claude Codex Code(CC)
๐Ÿฅ‰ 78 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "azure-servicebus-dotnet" from https://skillstore.io/skills/sickn33-azure-servicebus-dotnet.md and its manifest at https://skillstore.io/api/skills/sickn33-azure-servicebus-dotnet/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.

Test it

Using "azure-servicebus-dotnet". Create a secure sender for the orders queue.

Expected outcome:

A concise implementation plan using Microsoft Entra ID, one reusable client, a queue sender, safe batches, and async disposal.

Using "azure-servicebus-dotnet". How should failed order messages be handled?

Expected outcome:

  • Abandon transient failures so the message can be retried.
  • Dead-letter invalid messages with a clear reason and description.
  • Monitor delivery counts and inspect the dead-letter subqueue.

Using "azure-servicebus-dotnet". Design ordered processing for each customer.

Expected outcome:

A session design that uses the customer identifier as SessionId, maintains state, renews locks, and isolates failures by session.

Security Audit

Safe
v5 โ€ข 7/23/2026 Open versioned report

All 54 static findings are false positives. The command findings are Markdown fences or inline code, the network findings are official reference links, and the reconnaissance finding is a dead-letter API example. No prompt injection, exfiltration intent, obfuscated behavior, or executable skill code was found in SKILL.md.

1
Files scanned
343
Lines analyzed
0
Review items
0
False positives ignored
No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.
Audited by: codex View Audit History โ†’
Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/sickn33-azure-servicebus-dotnet/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/sickn33-azure-servicebus-dotnet/security.svg)](https://skillstore.io/skills/sickn33-azure-servicebus-dotnet?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/sickn33-azure-servicebus-dotnet?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-azure-servicebus-dotnet/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/sickn33-azure-servicebus-dotnet.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Academic citations (APA ยท BibTeX ยท CFF)

APA citation

sickn33. (2026). azure-servicebus-dotnet security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-azure-servicebus-dotnet/audits/5

BibTeX citation

@techreport{sickn33-sickn33-azure-servicebus-dotnet-2026, author = {sickn33}, title = {azure-servicebus-dotnet security audit report (audit version 5)}, institution = {Skillstore}, year = {2026}, number = {5}, url = {https://skillstore.io/skills/sickn33-azure-servicebus-dotnet/audits/5}, note = {Author version unspecified} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "azure-servicebus-dotnet security audit report (audit version 5)" version: "unspecified" type: report authors: - name: "sickn33" date-released: "2026-07-23" url: "https://skillstore.io/skills/sickn33-azure-servicebus-dotnet/audits/5" identifiers: - type: other value: "skillstore:sickn33-azure-servicebus-dotnet:audit:5" description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High
55
Architecture
85
Maintainability
87
Content
69
Community
83
Spec Compliance

What You Can Build

Implement Queue Messaging

Create a .NET sender and receiver with batching, explicit settlement, and secure Microsoft Entra ID authentication.

Operate Background Consumers

Configure processors, concurrency, error callbacks, lock handling, and dead-letter workflows for dependable message processing.

Design Ordered Messaging

Plan sessions, topics, subscriptions, administration settings, and cross-entity transactions for enterprise messaging requirements.

Try These Prompts

Create a Queue Sender
Show a minimal .NET queue sender using DefaultAzureCredential, safe batching, and proper async disposal. Use placeholders for my namespace and queue.
Build a Message Processor
Design a ServiceBusProcessor for {queue_name} with manual completion, concurrency of {count}, transient error handling, and graceful startup and shutdown.
Add Ordered Session Processing
Create a session-based order workflow using {session_key}. Include session state, lock renewal, retries, and dead-letter handling for invalid messages.
Review a Messaging Architecture
Review my Service Bus design for {requirements}. Assess entities, settlement, batching, sessions, transactions, identity, lifecycle, failure handling, and operational risks.

Best Practices

  • Prefer Microsoft Entra ID with DefaultAzureCredential for production authentication.
  • Reuse thread-safe clients and dispose senders, receivers, and processors before the main client.
  • Use safe batching, explicit settlement, and targeted handling for transient Service Bus failures.

Avoid

  • Do not embed connection strings or other credentials in source code or prompts.
  • Do not complete messages before business processing succeeds.
  • Do not create a new ServiceBusClient for every message.

Frequently Asked Questions

Which .NET package does this skill cover?
It covers Azure.Messaging.ServiceBus and references version 7.20.1.
Can it use passwordless Azure authentication?
Yes. The guidance recommends DefaultAzureCredential with a fully qualified Service Bus namespace.
Does it explain message settlement?
Yes. It covers complete, abandon, defer, and dead-letter operations.
Does it support ordered message processing?
Yes. It demonstrates sessions, session state, and session lock renewal.
Can it provision queues and topics?
It can explain administration client operations, but it does not execute provisioning.
Is generated guidance production ready?
No. Validate credentials, permissions, entity settings, retry behavior, observability, and failure handling in your environment.

Developer Details

Author

sickn33

License

MIT

Skillstore revision

r2

Version notice

The author did not declare a version.

Ref

f9e2c34b4f19c7f3e6b0a1e93227b5f77cc12526

Maintenance freshness

7/26/2026

Usage

7 downloads ยท 114 views

File structure

๐Ÿ“„ SKILL.md