# Build Azure Service Bus Workflows in TypeScript

Reliable Azure Service Bus integrations require correct authentication, settlement, ordering, and recovery patterns. This skill provides focused TypeScript examples for common messaging workflows.

## Install

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

## Metadata

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

## Capabilities

- Shows how to install the Azure Service Bus and Azure Identity SDK packages.
- Configures passwordless Service Bus authentication with DefaultAzureCredential.
- Demonstrates sending, batching, receiving, and settling queue messages.
- Explains topic publishing and subscription receiving patterns.
- Covers ordered workflows with sessions and session state.
- Provides examples for dead-lettering, scheduling, deferral, peeking, and receive modes.

## Use Cases

- Build an order queue worker: Create a TypeScript producer and consumer with explicit message settlement and error handling.
- Standardize cloud messaging patterns: Define passwordless authentication, client reuse, batching, and resource lifecycle conventions for a team.
- Investigate failed deliveries: Inspect dead-letter messages and plan safe recovery or completion workflows.

## Prompt Templates

### Create a basic queue example

```
Show a TypeScript example that sends one message to [queue name] and receives it with peek-lock settlement.
```

### Design topic subscriptions

```
Design a TypeScript publisher and subscriber for [topic] and [subscription], including application properties and error handling.
```

### Add ordered processing

```
Create a session-based workflow for [process], preserving order by [group key] and maintaining session progress.
```

### Review production reliability

```
Review my Service Bus design for authentication, batching, settlement, dead-letter recovery, client lifecycle, and receive-mode risks.
```

## Limitations

- Provides reference snippets rather than a complete deployable application.
- Does not create Azure resources, role assignments, queues, topics, or subscriptions.
- Requires user-supplied namespaces, entity names, permissions, and deployment settings.
- Does not fully cover retries, lock renewal, observability, testing, or graceful shutdown.

## Best Practices

- Prefer Entra ID authentication and grant only required Service Bus roles.
- Reuse clients and close senders, receivers, and subscriptions during shutdown.
- Use peek-lock settlement and process the dead-letter queue explicitly.

## Anti Patterns

- Do not embed production connection strings or credentials in source code.
- Do not complete messages before business processing finishes successfully.
- Do not use receive-and-delete when message loss is unacceptable.

## Security Audit

- Audited at: 2026-07-23T23:05:52.439\+00:00
- Summary: All 39 static alerts are false positives caused by Markdown fences, TypeScript template literals, a normal namespace environment variable, and security guidance. No executable Ruby backticks, sensitive file access, system reconnaissance, prompt injection, or malicious intent were found.

## Stats

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