2.2.0-beta.1 (2025-02-07)
This preview release aligns with the corresponding 2.2.0
beta of OpenAI
and the 2025-01-01-Preview
Azure OpenAI Service API version.
New features include since 2.1.0-beta.2 include:
- Audio input for Chat Completions using
gpt-4o-audio-preview
or other compatible models: provide input audio viaChatMessageContentPart.CreateInputAudioPart()
, setAudioOptions
andResponseModalities
onChatCompletionOptions
, retrieve response audio viaOutputAudio
onChatCompletion
, and reference audio history from the assistant by using theAssistantChatMessage(ChatCompletion)
constructor or usingChatMessageContentPart.CreateAudioPart(string)
. For more information, refer to the examples in the OpenAI README. - Predicted outputs in Chat Completions:
ChatCompletionOptions
accepts anOutputPrediction
property that can be used viaChatOutputPrediction.CreateStaticContentPrediction()
with text content to optimize operation efficiency for scenarios like code completion. For more information, see OpenAI's predicted outputs announcement. - Chat Completions
o
-series model feature support: the newdeveloper
message role viaDeveloperChatMessage
(used just likeSystemChatMessage
),ReasoningEffortLevel
on Chat Completion options - [AOAI exclusive]
UserSecurityContext
integration with Defender for Cloud; add aUserSecurityContext
instance toChatCompletionOptions
withSetUserSecurityContext()
Breaking Changes
- Batch: files uploaded for batch operations (
UploadFile
withFileUploadPurpose.Batch
) will now report astatus
ofprocessed
, matching expected behavior against OpenAI's/v1
endpoint. This is a change from past behavior where such files would initially reportpending
and a laterprocessed
,error
, or other status depending on operation progress. Batch input validation is instead consistently performed from the batch client.