[BUG] o3-mini cannot be called from C# using the Azure OpenAI SDK because there is no place to add the api-reference

[benperk]

Library name and version

Azure.AI.OpenAI 2.1.0

Describe the bug

o3-mini cannot be called from C# using the Azure OpenAI SDK because there is no place to add the api-reference and it defaults to 2025-01-31. I receive this error. This is not happening with o1-mini or gpt-4o-mini.

HTTP 400 (BadRequest)Model {modelName} is enabled only for api versions 2024-12-01-preview and later.

When I append "?api-version=2024-12-01-preview" to the endpoint I receive this error.

HTTP 404 (404)Resource not found

Expected behavior

Expect the same behavior as with 01-mini and gpt-40-mini

Actual behavior

HTTP 400 (BadRequest)Model {modelName} is enabled only for api versions 2024-12-01-preview and later.

Reproduction Steps

var aoai_client = new AzureOpenAIClient(new Uri(parametersO3MINI.Endpoint), new DefaultAzureCredential());
chatClientO3MINI = aoai_client.GetChatClient(parametersO3MINI.Model);
optionsO3MINI = new()
{
Temperature = parametersO3MINI.Temperature,
FrequencyPenalty = parametersO3MINI.FrequencyPenalty,
PresencePenalty = parametersO3MINI.PresencePenalty,
Seed = parametersO3MINI.Seed,
};

var messagesO3MINI = new ChatMessage[]
{
new SystemChatMessage(system_prompt),
new UserChatMessage(user_prompt)
};
ChatCompletion completionO3MINI = chatClientO3MINI.CompleteChat(messagesO3MINI, optionsO3MINI);

Environment

.NET 8

[github-actions]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @jpalvarezl @ralph-msft @trrwilson.

[github-actions]

Hello @benperk. I'm an AI assistant for the azure-sdk-for-net repository. I have some suggestions that you can try out while the team gets back to you.

The current design in Azure.AI.OpenAI (v2.1.0) restricts API version configuration through a fixed enum, so there isn’t a direct way to override the API version via the client (i.e., adding an api-reference as a query parameter). Because o3-mini requires an API version of 2024-12-01-preview or later, using the default (2025-01-31) or any unsupported version results in the 400 error you’re seeing.

Suggestions:
• Consider evaluating if a newer package or update offers more flexibility in API version configuration; alternatively, if your scenario permits, adjust your endpoint settings to match a supported version.
• For more control, you might raise a feature request to allow the API version to be set via a get/set property (see discussion in this issue for context).
• As a temporary workaround, some have used proxy solutions to inject the proper query parameter, albeit acknowledging that it isn’t an ideal long-term resolution.

The team will get back to you shortly, hopefully this helps in the meantime.