The Azure SDK team is pleased to announce our August 2026 client library releases.

57 packages released this month.

Stable Packages (17)

  • App Configuration

  • Core - Client - Core

  • Device Update

  • Document Translation

  • OpenTelemetry AspNetCore

  • Planetary Computer

  • Resource Management - Computelimit

  • Resource Management - Container Service

  • Resource Management - Container Service Fleet

  • Resource Management - Cosmos DB

  • Resource Management - Event Hubs

  • Resource Management - Hybrid Compute

  • Resource Management - NetApp Files

  • Resource Management - Service Bus

  • System Events

  • System.ClientModel

  • Voice Live

Patch Updates (1)

  • OpenTelemetry Exporter

Beta Packages (37)

  • AI Agent Server - Core

  • AI Agent Server - Invocations

  • AI Agent Server - Responses

  • App Configuration

  • Code Transparency

  • Confidential Ledger

  • Content Understanding

  • Personalizer

  • Provisioning - Attestation

  • Provisioning - Compute

  • Provisioning - Domainregistration

  • Provisioning - Event Hubs

  • Provisioning - Iothub

  • Provisioning - Recoveryservices

  • Provisioning - Recoveryservicesbackup

  • Resource Management - App Configuration

  • Resource Management - Authorization

  • Resource Management - Cloud Health

  • Resource Management - Compute Fleet

  • Resource Management - Compute Recommender

  • Resource Management - Compute Schedule

  • Resource Management - Compute.Bulkactions

  • Resource Management - Container Registry

  • Resource Management - Container Service

  • Resource Management - Containerservicepreparedimgspec

  • Resource Management - Datadog

  • Resource Management - Discovery

  • Resource Management - Enclave

  • Resource Management - IoT Hub

  • Resource Management - NetApp Files

  • Storage - Blobs

  • Storage - Blobs Batch

  • Storage - Blobs ChangeFeed

  • Storage - Common

  • Storage - Files Data Lake

  • Storage - Files Share

  • Storage - Queues

Release highlights

AI Agent Server - Core 1.0.0-beta.27 Changelog

Features Added

  • Added a durable key-value state store client under Azure.AI.AgentServer.Core.Storage. FoundryStateStore.GetOrCreateAsync binds (creating if needed) a named, Foundry-backed store; instances expose async GetAsync/UpdateAsync/DeleteAsync for the store and CreateItemAsync/SetItemAsync/GetItemAsync/DeleteItemAsync/ListKeysAsync for its items, with optimistic concurrency (If-Match/ETag), optional per-user isolation, and store-level item TTL. The .NET analogue of the Python SDK’s FoundryStateStore.
  • Added support for Microsoft Entra authentication when exporting telemetry to Azure Monitor. When APPLICATIONINSIGHTS_AUTH_MODE is set to Entra, the Azure Monitor exporter attempts to use a system-assigned managed identity credential (falling back to connection-string authentication if the credential cannot be created).

AI Agent Server - Core 1.0.0-beta.28 Changelog

Features Added

  • FoundryStateStore item operations now accept an explicit callId and forward the ambient FoundryAgentRequestContext.Current.CallId by default. Resilient task handlers restore a top-level persisted call_id for every execution attempt.
  • Added resilient task and streaming primitives for building durable, long-running agents (Azure.AI.AgentServer.Core.Tasks and Azure.AI.AgentServer.Core.Streaming):
  • Register one-shot and multi-turn tasks with IServiceCollection.AddResilientTasks() and the ResilientTaskBuilder (AddTask / AddMultiTurnTask), including overloads that accept a source-generated JsonTypeInfo<TInput> for Native-AOT / trimming-safe input serialization. The reflection-based overloads carry [RequiresUnreferencedCode] / [RequiresDynamicCode] so trimming/AOT builds get a compile-time warning steering them to the JsonTypeInfo<TInput> overloads.
  • Run and resume tasks through ITaskInvoker (RunAsync, StartAsync, GetActiveRunAsync) with the TaskRun<TOutput> handle (await its Completion task, or Completion.WaitAsync(token) to cancel only your wait) and the TaskContext<TInput> handler surface (entry mode, retry attempt, cooperative cancellation, shutdown, and steering signals).
  • Configure per-task durability with TaskRegistrationOptions (title, timeout, retry) and TaskRetryPolicy (attempt count + an Azure.Core.DelayStrategy for the backoff).
  • Resumable event streaming with AgentEventStreamRegistry / AgentEventStream and AddAgentEventStreams(), supporting in-memory live, in-memory replay, and file-backed replay backings via AgentEventStreamOptions. The event representation is System.Net.ServerSentEvents.SseItem<string>: the caller places the serialized event text in SseItem<string>.Data and an opaque SseItem<string>.EventId is the resume/reconnect token (Subscribe(afterEventId), GetLastEventIdAsync()). Because the data is already a string, there is no payload codec — SseFormatter can frame a Subscribe(...) stream directly onto an HTTP response.
  • A single ResilientTaskException carrying an extensible ResilientTaskErrorCode (HandlerError, ExhaustedRetries, Conflict, PreconditionFailed, QueueFull) with code-specific data exposed as nullable properties (CurrentStatus, ActualLastInputId, Failure). Argument validation surfaces as ArgumentException and cancellation as OperationCanceledException; recovery deferral (ExitForRecoveryAsync) is an internal lifecycle handoff and never surfaces as an exception. The streaming layer keeps its AgentEventStreamException hierarchy.

Bugs Fixed

  • Kept the task lease renewed across retry backoff delays so a long inter-attempt backoff cannot let the lease lapse and allow a concurrent re-invocation of the same task turn.
  • Hardened the resilient-task engine shutdown signalling against a benign race between a completing turn and host disposal.
  • A one-shot task whose durable completion write fails, and a multi-turn task whose durable suspend write fails, now surface the failure to the caller instead of reporting success while the record remains in_progress (which a later recovery scan could re-run).
  • The local file-backed task store now serializes its existence check and record write under the same lock as patch/delete, so two concurrent creates for the same id can no longer both succeed with the later write silently overwriting the earlier record.
  • The file-backed event-stream custom serializer/deserializer are now Func<object, string> / Func<string, object> (previously byte[]), matching the UTF-8 JSON-string on-disk format so a custom codec cannot silently corrupt non-UTF-8 payloads.
  • The local file-backed task store now writes each record through a temporary file and an atomic replace, so a crash mid-write can no longer leave a truncated record that reads back as a parse error and renders the task id permanently unusable.
  • The per-task write gate is no longer disposed when its bookkeeping entry is removed, closing a race where a concurrent write could observe ObjectDisposedException on a gate that was torn down while still in use.
  • A turn transition that replaces and disposes a handler’s cancellation source concurrently with a cancel/steering signal no longer surfaces ObjectDisposedException from the cancel path.
  • AddResilientTasks and AddAgentEventStreams are now safe against repeated registration: AddResilientTasks no longer registers the durability hosted service more than once (and rejects a conflicting second credential), and AddAgentEventStreams rejects a second configuring call instead of silently discarding its configuration.
  • Steering inputs that were queued but not yet drained when a process crashed are no longer stranded: on recovery the persisted pending_inputs queue is rehydrated into the in-process steering FIFO, so a recovered chain drains them instead of silently dropping them. Each queued input’s per-turn InputId is persisted alongside it so a recovered turn keeps its own identity and advances the chain head (last_input_id) exactly as it would without a crash.

AI Agent Server - Invocations 1.0.0-beta.6 Changelog

Features Added

  • AsyncAPI discovery endpoints — InvocationHandler now exposes two new virtual methods, GetAsyncApiJsonAsync and GetAsyncApiYamlAsync, served at GET /invocations/docs/asyncapi.json and GET /invocations/docs/asyncapi.yaml respectively. Both default to 404; override either or both to publish the AsyncAPI companion to the existing openapi.json endpoint for streaming/bidirectional surfaces (e.g. the invocations_ws WebSocket protocol) that OpenAPI cannot express. The path extension is authoritative for the returned content type — no Accept negotiation and no format conversion.

AI Agent Server - Responses 1.0.0-beta.8 Changelog

Features Added

  • Resilient responses. Resilient background responses (ResponsesServerOptions.ResilientBackground) are composed directly on the Azure.AI.AgentServer.Core durable-task and event-stream primitives rather than a bespoke Responses-owned recovery stack, matching the Python implementation. Interrupted background responses are automatically recovered and re-invoked in the next process lifetime.
  • Resilient streaming with checkpoint/resumption: handlers persist durable snapshots at safe boundaries via ResponseEventStream.Checkpoint() and, on a recovered entry, reconstruct the resumption response from ResponseContext.IsRecovery / ResponseContext.PersistedResponse.
  • Steerable conversations (ResponsesServerOptions.SteerableConversations) with in-turn steering: a superseding turn enqueues and drains against the active turn, observable through ResponseContext.IsSteeredTurn and ResponseContext.PendingInputCount; fork, lock, and queue-full conflicts map to 409 Conflict.
  • Internal metadata is persisted for recovery and stripped on egress so it never leaks to clients.
  • Fail-loud composition validation: misconfigured resilient setups fail at startup with actionable errors instead of silently degrading.
  • The local default response provider is now file-based (durable) when resilient background is enabled outside a hosted environment.
  • Every stored (store=true) request now runs its handler inside a Core resilient task — foreground or background, streaming or non-streaming — so a crashed turn is task-tracked and recovered/marked-failed by the next-lifetime recovery scan (matching the Python resilience contract; only store=false runs inline). Streaming relays the per-response event stream immediately, preserving standalone SSE error semantics for pre-creation failures and response.failed (not response.completed) for terminal persistence failures.
  • A streaming turn superseded by steering that reaches its terminal via the framework completion fallback (a non-cooperative handler that lets its token trip without emitting its own terminal) is now durably persisted as completed, so the client-visible response.completed matches the stored record and the turn is valid conversation context for the draining steered turn (FR-053).

Breaking Changes

  • Removed ConversationChainMetadata, ConversationChainMetadataNamespace, ResponseContext.ConversationChainMetadata, and ResponseContextExtensions.MetadataNamespace. Durable application state now belongs in an explicit Azure.AI.AgentServer.Core.Storage.FoundryStateStore scoped with ResponseContext.ConversationChainId.
  • Removed the public ResponsesStreamProvider abstract class and the public IAsyncObserver<T> interface. SSE streaming is now composed on the Azure.AI.AgentServer.Core event-stream primitive (IEventStreamRegistry / IEventStream) rather than a Responses-owned stream provider, matching the Python implementation. The local default event-stream backing is in-memory replay, upgraded automatically to durable file-backed replay when resilient background is enabled outside a hosted environment.

App Configuration 1.11.0 Changelog

Features Added

  • Improved authentication in sovereign clouds (such as Bleu) when using a TokenCredential. Previously, if you did not set ConfigurationClientOptions.Audience, the client fell back to the Azure Public Cloud audience and authentication could fail. The client now infers the correct Microsoft Entra audience from your App Configuration endpoint, so no additional configuration is required. Public, Azure China, and Azure US Government endpoints continue to work as before, and you can still set Audience explicitly to override the inferred value.

App Configuration 1.12.0-beta.1 Changelog

Features Added

  • Added a Description property on ConfigurationSetting and ConfigurationSnapshot to associate descriptive text with settings and snapshots.
  • Added SettingFields.Description so Description can be requested when retrieving configuration settings.
  • Added support for 2024-09-01, 2026-04-01, and 2026-05-01-preview (default) service API versions.
  • Added support for the new feature flag endpoint via a dedicated FeatureFlagClient, which exposes GetFeatureFlag, GetFeatureFlags, AddFeatureFlag, SetFeatureFlag, and DeleteFeatureFlag operations (and their async counterparts), along with the FeatureFlag model and related types (FeatureFlagConditions, FeatureFlagAllocation, FeatureFlagTelemetryConfiguration, FeatureFlagVariantDefinition, etc.). Requires the 2026-05-01-preview service API version.

Code Transparency 1.0.0-beta.12 Changelog

Bugs Fixed

  • Fixed asynchronous registration and receipt retrieval against a still-pending transaction. When a write is routed to a backup node the service replies with a redirect whose Location (for example /entries/{entryId}) omits the api-version. CodeTransparencyRedirectPolicy now carries the originating request’s api-version onto followed 303/307/308 redirect targets, so the subsequent read stays on the versioned API instead of falling back to the service’s unversioned (legacy) behavior. On the versioned API a read of a not-yet-committed entry is answered with a 302 Found whose Location points back at the same entry URL; the followed read now treats that 302 as retriable, and the client’s default retry settings were raised (more, exponentially backed-off retries starting at 200 ms) so the pipeline polls until the committed receipt (200). All retry and delay values remain overridable through CodeTransparencyClientOptions.Retry.

Confidential Ledger 2.0.0-beta.1 Changelog

Features Added

  • Added support for stable API version 2026-02-23.
  • Added opt-in support for the Azure Confidential Ledger Gateway via ConfidentialLedgerClientOptions.UseLedgerGateway. When enabled:
  • The SDK skips the per-ledger CCF identity-service TLS bootstrap. The gateway uses publicly-rooted certificates, so the OS trust store is sufficient.
  • ConfidentialLedgerClient.PostLedgerEntry accepts an HTTP 202 response and returns an operation whose Id is the gateway-assigned operationId (read from the x-ms-webfe-operation-id response header, with a fallback to the response body). The operation transparently polls GET /app/operations/{operationId} and surfaces the underlying CCF transaction once committed.
  • Client-certificate (mTLS) authentication is rejected at construction time — only TokenCredential is supported by the gateway.
  • Primary-node redirect caching (added in 1.4.1-beta.5) is automatically disabled, since the gateway brokers node routing on the server side.
  • Added ConfidentialLedgerClient.GetOperationStatus / GetOperationStatusAsync for direct polling of the gateway operation queue.
  • Added ConfidentialLedgerClient.RehydratePostLedgerEntryOperation(string operationId) for resuming a previously-started write submission across process restarts (no I/O is performed until polling begins). Operation IDs remain valid on the server for the gateway’s operation-record retention period.

Bugs Fixed

  • PostLedgerEntryOperation.GetRawResponse() now returns the initial submit response before the first poll. Previously, callers using WaitUntil.Started who inspected response headers (for example x-ms-ccf-transaction-id or x-ms-webfe-operation-id) on the returned operation observed a NullReferenceException.

Confidential Ledger 2.0.0-beta.2 Changelog

Bugs Fixed

  • Failover requests are now validated by endpoint-specific transports against that ledger’s own identity TLS certificate, fetched from the independently validated Identity Service. A certificate trusted for one ledger cannot authenticate another ledger. Custom transports remain supported.
  • PostLedgerEntryOperation now treats transient 406 NotAcceptable responses from the status endpoint as Pending and tolerates exactly 3 consecutive 404 NotFound HTTP responses while a transaction is replicated. The operation-specific 404 tolerance no longer multiplies with pipeline retries; normal 404 retry behavior remains unchanged for other operations.
  • Archived-collection fallback responses now preserve the complete historical ledger entry payload, including optional tags.

Features Added

  • Added support to route retryable HTTP responses and retryable transport failures to failover ledgers for GetLedgerEntry, GetLedgerEntryAsync, GetCurrentLedgerEntry, and GetCurrentLedgerEntryAsync. No other reads or writes fail over. The primary and every failover endpoint receive independent normal retry budgets; caller cancellation never initiates failover, and the original primary failure is preserved if discovery or all failovers fail.
  • Added ConfidentialLedgerClientOptions.Failover to control the order in which failover endpoints are attempted: Ordered (default, preserves the order reported by the identity service) or Random (shuffles the candidates to spread load across failover ledgers).
  • Added ConfidentialLedgerClientOptions.FailoverNetworkTimeout. When set, this network timeout applies independently to requests against each failover endpoint. When unset, the configured retry network timeout applies.
  • The client now treats a GetLedgerEntry/GetLedgerEntryAsync response that is still in the Loading state as transient and automatically polls until the entry is committed, bounded by the client’s configured retry settings (ClientOptions.Retry.MaxRetries attempts with ClientOptions.Retry.Delay between attempts). Callers no longer need to write a manual polling loop.

  • Added ConfidentialLedgerClientOptions.EnableArchivedCollectionFallback. It defaults to true, so GetCurrentLedgerEntry and GetCurrentLedgerEntryAsync transparently fall back to a historical query for a collection whose latest entry has been archived (pruned), without additional caller logic or configuration. Set it to false to retain the legacy 404 Not Found behavior.

  • Added strongly typed convenience overloads for service operations. The existing protocol methods remain available for advanced scenarios.
  • Added experimental configuration and host-builder integration through ConfidentialLedgerClientSettings and ConfidentialLedgerClientHostExtensions.

Breaking Changes

  • Renamed and moved Azure.Security.ConfidentialLedger.Models.SecurityConfidentialLedgerModelFactory to Azure.Security.ConfidentialLedger.ConfidentialLedgerModelFactory.

Content Understanding 1.2.0-beta.3 Changelog

Features Added

  • Added support for service API version 2026-06-01-preview, which is the default service API version for this beta package.
  • Added inline analysis convenience APIs AnalyzeInline / AnalyzeInlineAsync and AnalyzeBinaryInline / AnalyzeBinaryInlineAsync, available only with service API version 2026-06-01-preview. These return AnalysisResult in a single HTTP 200 response (no LRO polling) and throw RequestFailedException when the inline operation status is not Succeeded. AnalyzeBinaryInline* includes a ContentRange? convenience overload matching AnalyzeBinary*. See Sample 18 and Sample 19.
  • Added AnalyzeBinaryOptions and corresponding AnalyzeBinary* / AnalyzeBinaryInline* overloads for binary analyze request settings (ContentRange, ContentType, ProcessingLocation, and future options). Required analyzer ID and binary input live on the options bag. See Sample 01 and Sample 19.
  • Added AnalyzeOptions and corresponding Analyze* / AnalyzeInline* overloads for JSON analyze request settings (ModelDeployments, ProcessingLocation, and future options). Required analyzer ID and inputs live on the options bag.
  • Added semantic chunking for custom analyzers in 2026-06-01-preview: configure ContentAnalyzerConfig.ChunkingStrategy with SemanticChunkingStrategy (for example MaxTokens) when creating an analyzer, then read DocumentContent.Chunks (DocumentChunk spans into markdown) from the analysis result. See Sample 17.
  • Added analyzer workflow selection via ContentAnalyzerConfig.Workflow / ContentAnalyzerWorkflow for 2026-06-01-preview. Omit Workflow for standard extraction, or set ContentAnalyzerWorkflow.Agentic when an answer must be built from evidence. See Sample 16.
  • Added signature detection via DocumentSignature / DocumentContent.Signatures for 2026-06-01-preview when layout extraction is enabled (EnableLayout, including prebuilt-layout). See Detect signatures and Sample 10.
  • Added in-page segmentation opt-in via ContentAnalyzerConfig.AllowInPageSegments for 2026-06-01-preview. Used with EnableSegment, this allows classification segments to split within a page (for example supplemental statements appended after a K-1 tax form) instead of only at page boundaries. See Classify in-page segments.
  • Added embedded document metadata via AnalysisContent.Metadata for 2026-06-01-preview. See Extract document metadata.
  • Added analysis diagnostics via AnalysisResult.Infos for 2026-06-01-preview. The collection exposes service information as ResponseError values for troubleshooting. See Analysis diagnostics.
  • Updated ToLlmInput (preview) to emit analysis-result metadata (AnalysisContent.Metadata) under a metadata: front-matter block. See ToLlmInput.
  • Added AnalyzeOperationExtensions.GetUsageDetails() to return generated UsageDetails from a completed analyze LRO (Operation<AnalysisResult>) or inline analyze response (Response<AnalysisResult>). See Sample 03, Sample 18, and Sample 19. GetUsage() / AnalyzeUsageDetails are obsolete and retained for 1.1.0 compatibility.

Core - Client - Core 1.61.0 Changelog

Bugs Fixed

  • Fixed an issue where response content logging could emit more bytes than were actually read when a non-buffered (streaming) response was read into a buffer larger than the response body. Previously, when the read began at offset 0, the entire caller-supplied buffer was logged — including the bytes past the response payload, which for a pooled buffer contain unrelated in-process content — and the configured LoggedContentSizeLimit was not applied. The logging policy now logs only the bytes that were read. (#61399)
  • Fixed an issue where RequestFailedException could throw a secondary ArgumentNullException while formatting a failed response that had a text content-type header but an empty body, masking the actual service failure. The exception now preserves the original HTTP status, reason phrase, and headers, and no longer formats empty response content.
  • Fixed AzureCliCredential to not pass both --tenant and --subscription flags to the Azure CLI, as the CLI rejects this combination. When a tenant is requested (for example, via challenge-based authentication) it now takes precedence and --subscription is omitted; --subscription is used only when no tenant is requested. (#58949)

Features Added

  • Added AzureAuthorityHosts.AzureBleuCloud (https://login.sovcloud-identity.fr/), the Microsoft Entra authority host for Bleu Cloud, the national partner cloud for France. Interactive credentials’ Authenticate methods now also resolve the default Azure Resource Manager scope for Bleu Cloud.

Device Update 1.1.0 Changelog

Features Added

  • Regenerated the client library from the TypeSpec specification for the Device Update for IoT Hub 2026-06-01 GA API version.
  • Added support for TLS-secured update payload downloads.

Document Translation 3.0.0 Changelog

Features Added

  • Added support for the 2026-03-01 service API version, which is now the default.
  • Added image translation support: the TranslateTextWithinImage property on BatchOptions for batch requests, and a translateTextWithinImage parameter on SingleDocumentTranslationClient.Translate and TranslateAsync for single document requests.
  • Added StartTranslation and StartTranslationAsync convenience overloads on DocumentTranslationClient that take an IEnumerable<DocumentTranslationInput> plus a translateTextWithinImage flag, so batch image translation can be enabled without constructing a TranslationBatch/BatchOptions.
  • Added image scan reporting to DocumentStatusResult: ImageCharactersDetected, ImagesCharged, TotalImageScansSucceeded, and TotalImageScansFailed.
  • Added the DeploymentName property to TranslationTarget to specify the deployment name of the custom translation model for a batch translation request.
  • Added the DeploymentName property to DocumentStatusResult, exposing the deployment name of the custom translation model used for the translation.
  • Added the deploymentName parameter to SingleDocumentTranslationClient.Translate and TranslateAsync for single document translation requests.
  • Added dependency-injection and hosting support via DocumentTranslationClientHostExtensions, SingleDocumentTranslationClientHostExtensions, the DocumentTranslationClientSettings and SingleDocumentTranslationClientSettings types, and new constructors that accept these settings.

Breaking Changes

  • Changed the default DocumentTranslationClientOptions.ServiceVersion from V2024_05_01 to V2026_03_01, and removed the interim V2024_11_01_Preview and V2025_12_01_Preview preview service versions. Use the stable V2026_03_01 version instead.
  • Added deploymentName and translateTextWithinImage parameters (positioned after category) to the SingleDocumentTranslationClient.Translate and TranslateAsync overloads. This is a binary-breaking change for existing callers.
  • Made the format type parameter required (FileFormatType fileFormatType instead of FileFormatType? type) on DocumentTranslationClient.GetSupportedFormats and GetSupportedFormatsAsync, since the 2026-03-01 service version requires it. Specify FileFormatType.Document or FileFormatType.Glossary. The previous nullable overload is retained for binary compatibility but now throws NotSupportedException when called without a type.

OpenTelemetry AspNetCore 1.6.0 Changelog

Bugs Fixed

  • Hardened Azure Monitor ingestion and Live Metrics redirect handling to prevent credentials and telemetry from being forwarded to untrusted destinations. (#61244)

OpenTelemetry Exporter 1.8.3 Changelog

Bugs Fixed

  • Hardened ingestion and Live Metrics redirect handling to reject untrusted destinations before replaying telemetry or caching the redirect. Redirect targets must now use HTTPS and match an approved Azure Monitor trust boundary, preventing credentials and telemetry from being forwarded to attacker-controlled endpoints. (#61244)

Personalizer 2.0.0-beta.3 Changelog

Bugs Fixed

Breaking Changes

Features Added

Planetary Computer 1.0.0 Changelog

Features Added

  • General availability release of the Azure Planetary Computer client library for .NET.
  • Full support for STAC API (v1.0.0) operations: collections, items, search, and tiles endpoints.
  • Data client with support for rendering data (GetTile, GetPreview, GetStatistics, GetBounds, GetWmtsCapabilities).
  • Ingestion client for managing data ingestion workflows.
  • Managed Storage Shared Access Signature (SAS) client for secure token generation.
  • Full async/await support throughout the SDK.
  • Support for .NET 8.0, .NET 10.0, and .NET Standard 2.0.
  • Added PlanetaryComputerProClientSettings to support creating a PlanetaryComputerProClient from IConfiguration, including configuration-based credential resolution and dependency injection registration.
  • Data client methods with many parameters use options bag pattern for improved usability (e.g., GetItemPointAsync(GetItemPointOptions)).

Provisioning - Attestation 1.0.0-beta.1 Changelog

Provisioning - Compute 1.0.0-beta.2 Changelog

Provisioning - Domainregistration 1.0.0-beta.1 Changelog

Provisioning - Event Hubs 1.2.0-beta.1 Changelog

Provisioning - Iothub 1.0.0-beta.1 Changelog

Provisioning - Recoveryservices 1.0.0-beta.1 Changelog

Provisioning - Recoveryservicesbackup 1.0.0-beta.1 Changelog

Resource Management - App Configuration 1.5.0-beta.2 Changelog

Resource Management - Authorization 1.2.0-beta.1 Changelog

Resource Management - Cloud Health 1.0.0-beta.4 Changelog

Resource Management - Compute Fleet 1.1.0-beta.3 Changelog

Resource Management - Compute Recommender 1.1.0-beta.1 Changelog

Resource Management - Compute Schedule 1.2.0-beta.5 Changelog

Resource Management - Compute.Bulkactions 1.2.0-beta.1 Changelog

Resource Management - Computelimit 1.4.0 Changelog

Resource Management - Container Registry 1.5.0-beta.3 Changelog

Resource Management - Container Service 1.6.0 Changelog

Resource Management - Container Service 1.7.0-beta.1 Changelog

Resource Management - Container Service Fleet 1.2.0 Changelog

Resource Management - Containerservicepreparedimgspec 1.0.0-beta.1 Changelog

Resource Management - Cosmos DB 1.5.0 Changelog

Resource Management - Datadog 1.1.0-beta.2 Changelog

Resource Management - Discovery 1.0.0-beta.1 Changelog

Resource Management - Enclave 1.0.0-beta.1 Changelog

Resource Management - Event Hubs 1.3.0 Changelog

Resource Management - Hybrid Compute 1.1.0 Changelog

Resource Management - IoT Hub 1.2.0-beta.4 Changelog

Resource Management - NetApp Files 1.18.0 Changelog

Resource Management - NetApp Files 1.19.0-beta.1 Changelog

Resource Management - Service Bus 1.2.0 Changelog

Storage - Blobs 12.30.0-beta.1 Changelog

Features Added

  • Added support for service version 2026-10-06.
  • Added AccessTier, AccessTierInferred, AccessTierChangedOn, and SmartAccessTier to BlobDownloadDetails.
  • Added support for PUT blob operations returning both the existing MD5 content hash and the new CRC64 checksum.
  • Added support for Apache Arrow response format for GetBlobs and GetBlobsByHierarchy.
  • Added support for the EndBefore property in GetBlobs and GetBlobsByHierarchy. Note that EndBefore is currently only available for Apache Arrow response format and is not returned for XML response format.

Breaking Changes

  • Block IDs generated during partitioned uploads are now randomly generated instead of based on sequential integers. This ensures uniqueness across concurrent uploads to the same blob but means block IDs are no longer predictable or ordered.

Storage - Blobs Batch 12.27.0-beta.1 Changelog

Features Added

  • Added support for service version 2026-10-06.

Storage - Blobs ChangeFeed 12.0.0-preview.64 Changelog

Features Added

  • Added support for service version 2026-10-06.

Storage - Common 12.29.0-beta.1 Changelog

Features Added

  • This release contains bug fixes to improve quality.

Storage - Files Data Lake 12.28.0-beta.1 Changelog

Features Added

  • Added support for service version 2026-10-06.

Storage - Files Share 12.28.0-beta.1 Changelog

Features Added

  • Added support for service version 2026-10-06.
  • Added ShareFileClient.GetAllRangeList(), GetAllRangeListAsync(), GetAllRangeListDiff(), and GetAllRangeListDiffAsync().

Storage - Queues 12.28.0-beta.1 Changelog

Features Added

  • Added support for service version 2026-10-06.

System Events 1.1.0 Changelog

Features Added

  • Implemented IJsonModel and IPersistableModel deserialization methods for events.

System.ClientModel 1.15.0 Changelog

Features Added

  • Added sealed, one-shot AsyncStreamingClientResult<T> for asynchronous streaming responses, with factories for custom producers, server-sent events, and newline-delimited JSON.

Bugs Fixed

  • Fixed an issue where response content logging could emit more bytes than were actually read when a non-buffered (streaming) response was read into a buffer larger than the response body. Previously, when the read began at offset 0, MessageLoggingPolicy logged the entire caller-supplied buffer — including the bytes past the response payload, which for a pooled buffer contain unrelated in-process content — and the configured MessageContentSizeLimit was not applied. Only the bytes that were read are now logged. (#61399)

Voice Live 1.2.0 Changelog

Features Added

  • Added AzureRealtimeNativeVoice and AzureRealtimeNativeVoiceName with 12 new voice options (Aarti, Andrew, Ava, Denise, Diya, Elsa, Florian, Francisca, Meera, Xiaoxiao, Ximena, Yunxi).
  • Added AllowParallelToolCalls property on VoiceLiveSessionOptions.
  • Added Channels and ReferenceSource (EchoCancellationReferenceSource) properties on AudioEchoCancellation.
  • Added streaming text input events: ClientEventInputTextDelta, ClientEventInputTextDone.
  • Added ServerEventResponseInvocationDelta for streaming invocation deltas.
  • Added ExpiresOn property on VoiceLiveSessionResponse (server-set session expiration time).
  • Added the 2026-07-15 GA service version (VoiceLiveClientOptions.ServiceVersion.V2026_07_15), which is now the default.

Latest Releases

View all the latest versions of .NET packages here.

Installation Instructions

To install any of our packages, please search for them via Manage NuGet Packages... in Visual Studio (with Include prerelease checked) or copy these commands into your terminal:

$> dotnet add package Azure.AI.AgentServer.Core --version 1.0.0-beta.27
$> dotnet add package Azure.AI.AgentServer.Core --version 1.0.0-beta.28
$> dotnet add package Azure.AI.AgentServer.Invocations --version 1.0.0-beta.6
$> dotnet add package Azure.AI.AgentServer.Responses --version 1.0.0-beta.8
$> dotnet add package Azure.AI.ContentUnderstanding --version 1.2.0-beta.3
$> dotnet add package Azure.AI.Personalizer --version 2.0.0-beta.3
$> dotnet add package Azure.AI.Translation.Document --version 3.0.0
$> dotnet add package Azure.AI.VoiceLive --version 1.2.0
$> dotnet add package Azure.Analytics.PlanetaryComputer --version 1.0.0
$> dotnet add package Azure.Core --version 1.61.0
$> dotnet add package Azure.Data.AppConfiguration --version 1.11.0
$> dotnet add package Azure.Data.AppConfiguration --version 1.12.0-beta.1
$> dotnet add package Azure.IoT.DeviceUpdate --version 1.1.0
$> dotnet add package Azure.Messaging.EventGrid.SystemEvents --version 1.1.0
$> dotnet add package Azure.Monitor.OpenTelemetry.AspNetCore --version 1.6.0
$> dotnet add package Azure.Monitor.OpenTelemetry.Exporter --version 1.8.3
$> dotnet add package Azure.Provisioning.Attestation --version 1.0.0-beta.1
$> dotnet add package Azure.Provisioning.Compute --version 1.0.0-beta.2
$> dotnet add package Azure.Provisioning.DomainRegistration --version 1.0.0-beta.1
$> dotnet add package Azure.Provisioning.EventHubs --version 1.2.0-beta.1
$> dotnet add package Azure.Provisioning.IotHub --version 1.0.0-beta.1
$> dotnet add package Azure.Provisioning.RecoveryServices --version 1.0.0-beta.1
$> dotnet add package Azure.Provisioning.RecoveryServicesBackup --version 1.0.0-beta.1
$> dotnet add package Azure.ResourceManager.AppConfiguration --version 1.5.0-beta.2
$> dotnet add package Azure.ResourceManager.Authorization --version 1.2.0-beta.1
$> dotnet add package Azure.ResourceManager.CloudHealth --version 1.0.0-beta.4
$> dotnet add package Azure.ResourceManager.Compute.BulkActions --version 1.2.0-beta.1
$> dotnet add package Azure.ResourceManager.Compute.Recommender --version 1.1.0-beta.1
$> dotnet add package Azure.ResourceManager.ComputeFleet --version 1.1.0-beta.3
$> dotnet add package Azure.ResourceManager.ComputeLimit --version 1.4.0
$> dotnet add package Azure.ResourceManager.ComputeSchedule --version 1.2.0-beta.5
$> dotnet add package Azure.ResourceManager.ContainerRegistry --version 1.5.0-beta.3
$> dotnet add package Azure.ResourceManager.ContainerService --version 1.6.0
$> dotnet add package Azure.ResourceManager.ContainerService --version 1.7.0-beta.1
$> dotnet add package Azure.ResourceManager.ContainerServiceFleet --version 1.2.0
$> dotnet add package Azure.ResourceManager.ContainerServicePreparedImgSpec --version 1.0.0-beta.1
$> dotnet add package Azure.ResourceManager.CosmosDB --version 1.5.0
$> dotnet add package Azure.ResourceManager.Datadog --version 1.1.0-beta.2
$> dotnet add package Azure.ResourceManager.Discovery --version 1.0.0-beta.1
$> dotnet add package Azure.ResourceManager.Enclave --version 1.0.0-beta.1
$> dotnet add package Azure.ResourceManager.EventHubs --version 1.3.0
$> dotnet add package Azure.ResourceManager.HybridCompute --version 1.1.0
$> dotnet add package Azure.ResourceManager.IotHub --version 1.2.0-beta.4
$> dotnet add package Azure.ResourceManager.NetApp --version 1.18.0
$> dotnet add package Azure.ResourceManager.NetApp --version 1.19.0-beta.1
$> dotnet add package Azure.ResourceManager.ServiceBus --version 1.2.0
$> dotnet add package Azure.Security.CodeTransparency --version 1.0.0-beta.12
$> dotnet add package Azure.Security.ConfidentialLedger --version 2.0.0-beta.1
$> dotnet add package Azure.Security.ConfidentialLedger --version 2.0.0-beta.2
$> dotnet add package Azure.Storage.Blobs --version 12.30.0-beta.1
$> dotnet add package Azure.Storage.Blobs.Batch --version 12.27.0-beta.1
$> dotnet add package Azure.Storage.Blobs.ChangeFeed --version 12.0.0-preview.64
$> dotnet add package Azure.Storage.Common --version 12.29.0-beta.1
$> dotnet add package Azure.Storage.Files.DataLake --version 12.28.0-beta.1
$> dotnet add package Azure.Storage.Files.Shares --version 12.28.0-beta.1
$> dotnet add package Azure.Storage.Queues --version 12.28.0-beta.1
$> dotnet add package System.ClientModel --version 1.15.0

Feedback

If you have a bug or feature request for one of the libraries, please file an issue in our repo.