Azure Event Hubs for Rust
A practical guide to sending, batching, and consuming Azure Event Hubs data with the official Rust SDK.
The skill explicitly requires the official azure_messaging_eventhubs crate, rejects unofficial crates, recommends managed identity for production, prohibits hardcoded credentials, and lists sender, receiver, and owner RBAC roles. These provide basic credential and permission guidance. Points are deducted because data flows, sensitive event handling, user confirmation for external send/receive effects, least-privilege selection, auditing, rollback, and the scope of DeveloperToolsCredential are not explained.
The installation, authentication, sending, batching, partition receiving, and start-position examples are broadly consistent, and event-level errors are matched. Points are deducted because crate/API versions are not pinned, no skill-specific build or test evidence is supplied, and connection failures, authorization errors, empty streams, reconnects, cancellation, duplicate consumption, and checkpointing are not handled. Static review caps this dimension at 10.
The name, description, and trigger phrases clearly target Rust Event Hubs sending, receiving, batching, and partition-start scenarios. Points are deducted because non-fit boundaries, input/output expectations, partition discovery, and production limitations are not stated; there is no Chinese-language guidance, and reachability or alternatives for Azure and crates.io in mainland-China networks are not discussed.
The document is readable and layered, with installation, environment variables, concepts, authentication, workflows, RBAC, best practices, references, MIT licensing, and author metadata. Points are deducted for missing version policy, changelog, maintainer and update path, troubleshooting, compatibility notes, and a complete runnable project; the warning about version 0.21.0 lacks supporting explanation or a replacement version.
The snippets directly demonstrate core ProducerClient and ConsumerClient calls, including single-event sending, batch sending, partition receiving, and start-position control, so they can support basic tasks. Points are deducted because they omit complete application context, lifecycle management, retries, checkpointing, and production configuration, while the consumer example may run indefinitely. No execution evidence is included; static calibration caps this dimension at 7.
The skill supplies docs.rs, crates.io, and Azure SDK source references and identifies an official crate source, giving limited traceability. Points are deducted because links are not version-pinned and the skill contains no tests, lockfile, runnable sample project, or outcome evidence; repository-level CI and harness files do not demonstrate coverage of this specific skill path. Static calibration caps this dimension at 5.
- Do not use the DeveloperToolsCredential example directly in production; specify ManagedIdentityCredential, required RBAC, and credential sources.
- Sending events creates external and potentially irreversible data writes; confirm the target namespace, Event Hub, data sensitivity, and least-privilege RBAC before implementation.
- Pin and verify a compatible azure_messaging_eventhubs version; the document provides no version number, build result, or troubleshooting guidance.
- Add retry, cancellation, reconnect, checkpointing, duplicate-consumption, and consumer-shutdown handling, and assess mainland-China reachability for Azure and crates.io dependencies.
What does this skill do, and when should you use it?
This skill helps Rust developers build Azure Event Hubs clients for streaming ingestion and batch processing. It focuses on the official azure_messaging_eventhubs crate and shows ProducerClient and ConsumerClient workflows. The guidance covers single-event sends, batch sends, partition receivers, start positions, Entra ID authentication, and RBAC roles. It is a good fit for SDK-level implementation guidance, but it does not provide a complete deployed application or infrastructure setup.
It guides users to add azure_messaging_eventhubs, azure_identity, tokio, and futures with cargo add; configure EVENTHUBS_HOST and EVENTHUB_NAME; create clients with DeveloperToolsCredential or ManagedIdentityCredential; send individual events with ProducerClient; create and send batches; open a ConsumerClient receiver on a partition; consume events through an asynchronous stream; select Earliest or Latest start positions; handle per-event success and failure results; and assign Azure Event Hubs Data Sender, Data Receiver, or Data Owner roles.
- A Rust developer needs to publish application events to Azure Event Hubs for streaming ingestion.
- A service must receive and process ordered events from a specific Event Hubs partition.
- A high-throughput producer needs batch creation and batch sending.
- A consumer must start at the earliest available event or at the latest position.
- A team needs local developer authentication and managed identity authentication in production.
What are this skill's strengths and limitations?
- Provides concrete Rust examples for sending, batching, and consuming partitioned events.
- Explicitly directs users to the official azure_messaging_eventhubs crate.
- Distinguishes local developer credentials from production managed identity.
- Covers batching, per-event error handling, and consumer start positions.
- Requires an existing Azure Event Hubs namespace, Event Hub, and appropriate RBAC permissions.
- Focuses on SDK usage rather than a complete application, deployment, or operations design.
- The README's test-coverage summary does not list Rust skills, so dedicated test evidence for this skill is absent from the source.
- The source does not specify supported Rust versions, pricing, or performance benchmarks.
How do you install this skill?
Run npx skills add microsoft/skills and select azure-eventhub-rust in the wizard. The collection installs skills into the selected agent's skill directory; the README does not document a separate installation command for this skill. Add the Rust dependencies with cargo add azure_messaging_eventhubs azure_identity tokio futures.
How do you use this skill?
In an Agent Skills-compatible coding agent, use a request such as “Implement Azure Event Hubs batch sending and partition consumption in Rust using the official azure_messaging_eventhubs crate.” The documented trigger phrases include “event hubs rust,” “ProducerClient rust,” “ConsumerClient rust,” “send event rust,” “streaming rust,” and “eventhub rust.” Set EVENTHUBS_HOST and EVENTHUB_NAME, and assign the required Event Hubs RBAC role for Entra ID authentication.