Skip to main content
skill

azure-storage-queue-rust — Claude Code skill: setup and use

Guides AI assistants in writing Rust code for Azure Queue Storage via azure_storage_queue. It helps send, read, and delete queue messages cleanly.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add microsoft/skills --skill azure-storage-queue-rust -a claude-code
Open on GitHub

What azure-storage-queue-rust does

This skill provides strict conventions for integrating Azure Queue Storage into Rust projects using the official azure_storage_queue crate. It enforces using QueueServiceClient for account operations and deriving a QueueClient for specific queues. For runtime calls, setting AZURE_STORAGE_QUEUE_ENDPOINT is mandatory.

Authentication has a key pitfall. The Rust Azure SDK lacks DefaultAzureCredential. Trying to call it breaks the build. The skill instructs the agent to use DeveloperToolsCredential locally and ManagedIdentityCredential in production environments.

It also enforces dependency management rules. Crates must be added via cargo add rather than direct manifest edits. To handle #[non_exhaustive] models cleanly, structs finish with ..Default::default() while ignoring Clippy update warnings.

What it helps with

  • authenticate Azure Queue clients without DefaultAzureCredential
  • send and read messages with azure_storage_queue in Rust
  • remove processed queue items using pop receipts
  • inspect queue contents without consuming messages via peek_messages

Example prompts for the agent

  • Write a Rust function to send a message to an Azure queue with QueueClient.
  • Show how to poll and delete messages from Azure Queue Storage using ManagedIdentityCredential.
  • Implement peek_messages in Rust to check the next queue items without dequeueing.

How to install azure-storage-queue-rust

1Skills CLI (Vercel)

npx skills add microsoft/skills --skill azure-storage-queue-rust -a claude-code

2Manually: put the files in place

~/.claude/skills/azure-storage-queue-rust/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/azure-storage-queue-rust/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about azure-storage-queue-rust

How do I install azure-storage-queue-rust in Claude Code?

Run npx skills add microsoft/skills --skill azure-storage-queue-rust -a claude-code in your terminal.

What does azure-storage-queue-rust do?

It guides coding agents on official azure_storage_queue crate patterns. It ensures valid client setups, message handling, and correct RBAC role selection.

Why does this skill avoid DefaultAzureCredential?

The Rust azure_identity crate does not provide DefaultAzureCredential. The code must use DeveloperToolsCredential for local testing or ManagedIdentityCredential in production.

Source text

SKILL.md · MIT
---
name: azure-storage-queue-rust
description: |
  Azure Queue Storage library for Rust. Send, receive, and manage queue messages.
  Triggers: "queue storage rust", "QueueClient rust", "send message rust", "receive messages rust", "QueueServiceClient rust", "queue rust".
license: MIT
metadata:
  author: Microsoft
  package: azure_storage_queue
---

# Azure Queue Storage library for Rust

Client library for Azure Queue Storage — send, receive, and manage queue messages.

Use this skill when:

- An app needs to send or receive messages from Azure Queue Storage in Rust
- You need to create or manage queues
- You need to peek, receive, or delete queue messages
- You need RBAC-based auth for queue operations

> **IMPORTANT:** Only use the official `azure_storage_queue` crate published by the [azure-sdk](https://crates.io/users/azure-sdk) crates.io user. Do NOT use unofficial or community crates. Official crates use underscores in names and none have version 0.21.0.

## Installation

```sh
cargo add azure_storage_queue azure_identity azure_core tokio
```

> If your code uses `azure_core` types directly, add `azure_core` to `Cargo.toml`. If you only use `azure_storage_queue` re-exports, direct `azure_core` dependency is optional.

## Environment Variables

```bash
AZURE_STORAGE_QUEUE_ENDPOINT=https://<account>.queue.core.windows.net/ # Required for all operations
```

## Authentication

Rust Azure SDK code must not use `DefaultAzureCredential`. The Rust identity crate does not provide that type.

```rust
use azure_core::http::Url;
use azure_identity::DeveloperToolsCredential;
use azure_storage_queue::QueueServiceClient;

#[tokio::main]
async fn main() -> Result<(), Box<dyn std::error::Error>> {
    // Local dev: DeveloperToolsCredential. Production: use ManagedIdentityCredential.
    let credential = DeveloperToolsCredential::new(None)?;
    let service_url = Url::parse("https://<storage_account_name>.queue.core.windows.net/")?;
    let service_client = QueueServiceClient::new(service_url, Some(credential), None)?;

    // Derive a queue client by name.
    let queue_client = service_client.queue_client("<queue_name>")?;
    Ok(())
}
```

Do not infer public SDK types from generated internal model names. Prefer the crate README/examples when checking queue client method signatures and message/result shapes.

## Client Types

| Client               | Purpose                               | Access                                   |
| -------------------- | ------------------------------------- | ---------------------------------------- |
| `QueueServiceClient` | Account-level operations, list queues | `QueueServiceClient::new()`              |
| `QueueClient`        | Queue operations, send/receive/delete | `service_client.queue_client("<name>")?` |

## Core Workflow

### Send a Message

```rust
use azure_core::http::Url;
use azure_identity::DeveloperToolsCredential;
use azure_storage_queue::{models::QueueMessage, QueueServiceClient};

#[tokio::main]
async fn main() -> Result<(), Box<dyn std::error::Error>> {
    let credential = DeveloperToolsCredential::new(None)?;
    let service_url = Url::parse("https://<storage_account_name>.queue.core.windows.net/")?;
    let service_client = QueueServiceClient::new(service_url, Some(credential), None)?;
    let queue_client = service_client.queue_client("<queue_name>")?;

    #[allow(clippy::needless_update)]
    let message = QueueMessage {
        message_text: Some("hello world".to_string()),
        ..Default::default()
    };
    queue_client.send_message(message.try_into()?, None).await?;
    Ok(())
}
```

### Receive Messages

```rust
use azure_core::http::Url;
use azure_identity::DeveloperToolsCredential;
use azure_storage_queue::QueueServiceClient;

#[tokio::main]
async fn main() -> Result<(), Box<dyn std::error::Error>> {
    let credential = DeveloperToolsCredential::new(None)?;
    let service_url = Url::parse("https://<storage_account_name>.queue.core.windows.net/")?;
    let service_client = QueueServiceClient::new(service_url, Some(credential), None)?;
    let queue_client = service_client.queue_client("<queue_name>")?;

    let response = queue_client.receive_messages(None).await?;
    let messages = response.into_model()?;
    for msg in messages.items.unwrap_or_default() {
        println!("{}", msg.message_text.as_deref().unwrap_or("<empty>"));
    }
    Ok(())
}
```

### Delete a Message

After receiving a message, delete it using the message ID and pop receipt:

```rust
let response = queue_client.receive_messages(None).await?;
let messages = response.into_model()?;
for msg in messages.items.unwrap_or_default() {
    if let (Some(id), Some(pop_receipt)) = (&msg.message_id, &msg.pop_receipt) {
        queue_client.delete_message(id, pop_receipt, None).await?;
    }
}
```

### Peek Messages

Peek at messages without removing them from the queue:

```rust
let response = queue_client.peek_messages(None).await?;
let messages = response.into_model()?;
for msg in messages.items.unwrap_or_default() {
    println!("Peeked: {}", msg.message_text.as_deref().unwrap_or("<empty>"));
}
```

## RBAC Roles

For Entra ID auth, assign one of these roles to the identity:

| Role                                   | Access                 |
| -------------------------------------- | ---------------------- |
| `Storage Queue Data Reader`            | Read and peek messages |
| `Storage Queue Data Contributor`       | Read/write messages    |
| `Storage Queue Data Message Sender`    | Send messages only     |
| `Storage Queue Data Message Processor` | Receive and delete     |

## Best Practices

1. **Use `cargo add` to manage dependencies, never edit `Cargo.toml` directly.** Add and remove Rust SDK dependencies with cargo commands instead of manual manifest edits.
2. **Add `azure_core` only when importing `azure_core` types directly.** If your code imports `azure_core::http::Url`, `azure_core::http::RequestContent`, or `azure_core::error::ErrorKind`, include `azure_core`; otherwise a direct dependency is optional.
3. **Use `DeveloperToolsCredential`** for local dev, **`ManagedIdentityCredential`** for production — Rust does not provide a single `DefaultAzureCredential` type
4. **Never hardcode credentials** — use environment variables or managed identity
5. **Assign RBAC roles** — ensure appropriate queue data roles for the identity
6. **Use `QueueServiceClient` as the entry point** and derive `QueueClient` from it via `queue_client()`
7. **Delete messages after processing** — use the message ID and pop receipt from `receive_messages`
8. **Reuse clients** — clients are thread-safe; create once, share across tasks
9. **Run `cargo clippy -- -D warnings`** when the prompt, eval, or CI expects lint-clean output
10. **Future-proof `#[non_exhaustive]` SDK models** — end model-struct initializers (e.g. `QueueMessage`) with `..Default::default()` (add `#[allow(clippy::needless_update)]`) and use a `_` wildcard arm when matching SDK enums, so new service-added fields/variants don't break your build

## Reference Links

| Resource      | Link                                                                                  |
| ------------- | ------------------------------------------------------------------------------------- |
| API Reference | https://docs.rs/crate/azure_storage_queue/latest                                      |
| crates.io     | https://crates.io/crates/azure_storage_queue                                          |
| Source Code   | https://github.com/Azure/azure-sdk-for-rust/tree/main/sdk/storage/azure_storage_queue |

© Microsoft · MIT · microsoft/skills

Similar skills

All skills for Cloud: AWS, Azure, GCP →

From the same set242

The whole set →
azure-app-onboard Takes a business idea or existing codebase to a running Azure deployment: picks services, estimates cost, writes IaC. ★ 3,149repo stars azure-app-onboard-prereq Assesses source code readiness before initiating Azure infrastructure deployment. It checks dependencies, frameworks, and tools without running build commands. ★ 3,149repo stars airunway-aks-setup Guides AI Runway setup on an existing AKS cluster, from checking nodes to deploying a model. Use it to install the controller and configure an inference provider. ★ 3,149repo stars azure-servicebus-ts This skill guides TypeScript work with Azure Service Bus queues, topics, sessions, and dead-letter flows. Use it when building message-driven applications. ★ 3,149repo stars azure-storage-queue-py A skill that gives the agent working patterns for Azure Queue Storage in Python: sending, receiving and deleting messages. Handy for background jobs. ★ 3,149repo stars azure-mgmt-fabric-py This skill guides Python work with Microsoft Fabric capacities and resources through the Azure SDK. Use it when building code to create, inspect, or change capacities. ★ 3,149repo stars azure-storage-blob-java Supplies ready-to-use patterns for the Azure Storage Blob Java SDK, covering authentication, container administration, and file uploads. ★ 3,149repo stars azure-security-keyvault-secrets-java This skill guides Java work with Azure Key Vault secrets, from client setup and retrieval to versioning, deletion, recovery, and backups. ★ 3,149repo stars

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor