Microsoft has released stable 2.3.0 of its Azure AI Agent Server Core Python package, with changes to how model-attribution data is carried and a compatibility change for users of the related Responses package. Teams using that package need Responses 2.4.0 or later alongside Core, or older compatibility shims will fail against a removed constant.
Microsoft AI Watch analysis
What happened
The Core 2.3.0 release notes say the stable release adds a percent-encoded foundry.originalsubject member to custom Foundry baggage for model attribution. The experimental modelattributionheaders helper can accept existing per-call headers, preserve unrelated dimensions and replace or clear competing subject assertions.
The release also stops emitting standalone subject headers on outbound model calls while retaining platform-to-container ingress parsing. It removes the internal EXPERIMENTALLINKMESSAGE constant, which the notes say older Responses compatibility shims require. Users of azure-ai-agentserver-responses are told to upgrade to 2.4.0 or later with Core.
Why it matters
This is a meaningful change for teams building services around Azure’s agent-server SDK: attribution data is carried differently, and a Core upgrade can require a matching Responses upgrade. The notes also say oversized subject tuples and merged baggage are rejected rather than forwarded, while unrelated baggage is preserved. That is useful implementation detail, not merely a version number in a changelog.
Our read
Stable status makes this a release developers can plan around, but the compatibility requirement deserves attention before upgrading. Check the Core and Responses versions together, and review any code relying on the old outbound subject headers. A tidy upgrade is usually preferable to discovering a removed constant in production, which is not most teams’ preferred debugging ritual.
What to watch
- Whether applications need changes to consume the new baggage-based attribution.
- How the stable release behaves across mixed protocol and agent-server setups.
- Whether later releases change the experimental header helper or attribution contract.
Discussion spark: Should model-attribution data be carried through shared baggage, or is a dedicated outbound header clearer and safer for developers?
Sources and evidence
- azure-ai-agentserver-core2.3.0 (30 October 2026, 05:20 UTC)
not affiliated with or endorsed by Microsoft