# 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.

## Install

```bash
npx skillstore add sickn33/azure-servicebus-dotnet
```

## Metadata

- Status: approved
- Slug: sickn33-azure-servicebus-dotnet
- Skillstore revision: r2
- Version status: missing
- Tree hash: 9739fedca9889885be54cd64ae2a1002d10ef839abfa5b399e52c0282f76e070
- Author: sickn33
- GitHub username: sickn33
- License: MIT
- Repository: https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/azure-servicebus-dotnet
- Ref: f9e2c34b4f19c7f3e6b0a1e93227b5f77cc12526
- 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, network
- Quality score: 78
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/sickn33-azure-servicebus-dotnet
- Manifest: https://skillstore.pages.dev/api/skills/sickn33-azure-servicebus-dotnet/manifest

## Capabilities

- Explains package installation and client authentication with DefaultAzureCredential or connection strings.
- Provides patterns for sending, receiving, batching, and settling Service Bus messages.
- Demonstrates processors, ordered sessions, dead-letter queues, topics, and subscriptions.
- Shows administration operations and cross-entity transaction patterns.
- Summarizes important SDK types, disposal order, and client lifecycle guidance.
- Provides Service Bus exception handling and transport configuration guidance.

## Use Cases

- 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.

## Prompt Templates

### 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.
```

## Limitations

- The skill provides guidance and examples but does not provision Azure resources or run application code.
- Users must supply valid entity names, credentials, permissions, and environment settings.
- Examples require adaptation, testing, and operational review before production use.
- The guidance targets Azure.Messaging.ServiceBus version 7.20.1 and does not cover legacy SDKs.

## 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.

## Anti Patterns

- 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.

## Security Audit

- Audited at: 2026-07-23T22:59:06.531\+00:00
- Summary: 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.

## Stats

- Views: 114
- Downloads: 9
- Favorites: 0
- Popularity score: 0