Azure Service Bus for .NET
Guides .NET teams in building reliable Azure enterprise messaging workflows.
The document prefers Entra ID and presents connection strings as an alternative, with a production credential note; however, it does not specify least-privilege RBAC, sensitive-message handling, data flows, user confirmation, or rollback. The administration example includes direct queue deletion without confirmation or recovery guidance, so points are deducted.
It covers major paths including sending, receiving, settlement, processors, sessions, dead lettering, topics, administration, and transactions, with some error-handling and retry guidance. However, it lacks skill-specific tests, edge-case coverage, empty-message/lock-expiry handling, complete lifecycle examples, and diagnostic treatment for several failures. The score remains within the static-review cap.
The description, trigger terms, target SDK, and primary Service Bus scenarios are clear for .NET messaging work. Boundaries, input/output constraints, compatibility matrices, Chinese-language guidance, and mainland-China network or regional considerations are not stated, and production-architecture limits are underexplained.
The information architecture is readable and includes installation, authentication, environment variables, client hierarchy, workflows, type reference, best practices, error handling, related SDKs, and links. MIT licensing, author, and version metadata are present, but changelog, maintenance/update path, FAQ, known limitations, and version-drift guidance are absent.
The examples cover common Service Bus operations and provide directly useful patterns for code generation, with a clear core value proposition. Yet most snippets lack complete runnable context, prerequisite configuration, production-grade retry/idempotency/observability, and security detail, and no skill-specific output validation is supplied. Static calibration limits this to 7.
The skill gives an SDK version and official NuGet, API, GitHub, and troubleshooting links; the repository also shows general CI, evaluation workflows, and test-harness infrastructure. The supplied material does not provide skill-specific tests, execution results, or corroborated reproduction, so the static cap of 5 applies.
- The administration examples include external and destructive operations such as queue deletion; add explicit confirmation, permission boundaries, and recovery planning before use.
- Connection strings and message bodies may contain sensitive data; secure storage, log redaction, and least-privilege RBAC guidance are missing.
- The stated version and API examples should be compiled against the target SDK version in the real project; this review did not execute code.
- No guidance is provided for mainland-China connectivity, Azure region availability, or enterprise proxy configuration.
What does this skill do, and when should you use it?
This Agent Skill focuses on the Azure.Messaging.ServiceBus .NET SDK for queues, topics, subscriptions, sessions, and dead-letter handling. It covers authentication, client construction, sending and receiving, settlement, background processors, administration, and cross-entity transactions. Examples also show Azure.Identity and ASP.NET Core dependency injection. It is a good fit for teams building .NET applications that already use Azure Service Bus and want focused implementation guidance.
Provides coding agents with concrete .NET patterns for installing Azure.Messaging.ServiceBus and Azure.Identity, creating clients with Microsoft Entra credentials or connection strings, sending single or batched messages, receiving and settling messages, configuring ServiceBusProcessor, handling sessions and dead-letter queues, managing queues, topics, and subscriptions with ServiceBusAdministrationClient, and using TransactionScope for cross-entity transactions.
- A .NET developer needs reliable delivery for orders or background tasks through an Azure Service Bus queue.
- A team is implementing publish/subscribe messaging with topics and subscriptions.
- A workflow developer needs ordered processing for related messages by using Service Bus sessions.
- An operations-minded developer needs to inspect dead-letter metadata and define settlement behavior for invalid messages.
- A team is building a background consumer with controlled concurrency, error callbacks, and lock renewal.
What are this skill's strengths and limitations?
- Covers common Service Bus workflows from authentication and message delivery through entity administration.
- Includes concrete examples for batching, sessions, dead letters, background processing, and cross-entity transactions.
- Documents practical guidance on credential choice, client reuse, disposal, transient errors, transport, and lock duration.
- The skill is authored by Microsoft and released under the MIT license.
- It is narrowly focused on the Azure.Messaging.ServiceBus .NET SDK rather than generic queueing systems.
- Examples require an Azure Service Bus namespace or connection string; no local emulator or offline workflow is documented.
- The source does not specify a supported .NET SDK range, detailed permission setup, or Azure pricing.
- The repository README describes the collection as a work in progress, so content and tests may change.
How do you install this skill?
In an Agent Skills-compatible client, run npx skills add microsoft/skills and select azure-servicebus-dotnet in the installation wizard. The collection is installed into the selected agent directory, such as .github/skills/ for GitHub Copilot. The skill is located at .github/plugins/azure-sdk-dotnet/skills/azure-servicebus-dotnet/SKILL.md.
How do you use this skill?
Give the coding agent a concrete request containing a supported trigger, such as: Build a .NET ServiceBusProcessor for my-queue with manual message completion and abandonment on failure. You can also mention ServiceBusClient, ServiceBusSender, ServiceBusReceiver, ServiceBusProcessor, or dead letter queue. The source does not define a dedicated slash command.
How does this skill compare with similar options?
The source identifies Azure.Messaging.EventHubs for event streaming and Azure.Messaging.EventGrid for event routing; this skill focuses on Service Bus queues, topics, subscriptions, sessions, and settlement. It presents Microsoft Entra token credentials and connection strings as authentication options, with DefaultAzureCredential preferred for production.