Azure.AI.AgentServer.Invocations_1.0.0-beta.2

Azure OpenAI .NET Releases / 4/19/2026

📰 NewsDeveloper Stack & InfrastructureModels & Research

共有:

Key Points

Azure.AI.AgentServer.Invocations_1.0.0-beta.2 adds the x-agent-session-id response header to all Invocations protocol endpoints (GET, Cancel, OpenAPI), aligning behavior with the spec.
The update improves observability by logging whether user/chat isolation keys are present while ensuring key values are never recorded.
It adds inbound HTTP request logging for Tier 1 and Tier 2 deployments, capturing method, path, status code, duration, and correlation headers such as x-request-id and x-ms-client-request-id.
A breaking change makes InvocationsActivitySource internal so developers no longer create tracing activities directly; the framework manages tracing.
The release updates Azure.AI.AgentServer.Core dependency to include HttpClient instrumentation for distributed trace correlation.

Added x-agent-session-id response header on GET, Cancel, and OpenAPI endpoints. The POST
endpoint already set the header; all Invocations protocol endpoints now include it per spec §8.
Added isolation key presence logging (HasUserIsolationKey, HasChatIsolationKey) to all
endpoint handler logs (POST, GET, Cancel). Key values are never logged.
Added startup configuration logging: protocol registration is logged at Information level
when the host starts.
Added inbound request logging for Tier 1 and Tier 2 setups (via InvocationsServer.Run() or
AgentHost.CreateBuilder()). All incoming HTTP requests are logged with method, path, status
code, duration, and correlation headers (x-request-id, x-ms-client-request-id).

Made InvocationsActivitySource internal. The activity source is managed by
the framework; handlers do not need to create tracing activities directly.

Updated dependency on Azure.AI.AgentServer.Core to 1.0.0-beta.22, which adds outbound
HttpClient instrumentation for distributed trace correlation.

Dev.to

Dev.to

Dev.to

Dev.to

Reddit r/artificial