[BUG] 404 when using the latest Azure.OpenAI (2.2.0-beta5) + Latest OpenAI (2.3.0)

[ericstj]

Library name and version

Azure.OpenAI 2.2.0-beta5, OpenAI 2.3.0

Describe the bug

I was trying to update to the latest OpenAI library and my application stopped working.

At first I thought it was a problem with OpenAI - I tracked it down to regressing with this change openai/openai-dotnet@dff9bb5

But then I realized that the latest OpenAI would work fine if I was using an older Azure.OpenAI library. It was only when using the latest Azure.OpenAI library together with latest OpenAI library that I hit this failure.

Expected behavior

Runs to completion with success.

Actual behavior

Exception:

System.ClientModel.ClientResultException: HTTP 404 (: 404)

Resource not found
   at OpenAI.ClientPipelineExtensions.ProcessMessage(ClientPipeline pipeline, PipelineMessage message, RequestOptions options)
   at OpenAI.Chat.ChatClient.CompleteChat(BinaryContent content, RequestOptions options)
   at OpenAI.Chat.ChatClient.CompleteChat(IEnumerable`1 messages, ChatCompletionOptions options, CancellationToken cancellationToken)
   at Azure.AI.OpenAI.Chat.AzureChatClient.CompleteChat(IEnumerable`1 messages, ChatCompletionOptions options, CancellationToken cancellationToken)
   at Program.<Main>$(String[] args) in C:\scratch\OpenAIRepro\Program.cs:line 28

Reproduction Steps

Repro's using the basic sample from Azure AI foundary

using Azure;
using Azure.AI.OpenAI;
using OpenAI.Chat;

var endpoint = new Uri(Environment.GetEnvironmentVariable("AZURE_OPENAI_ENDPOINT"));
var deploymentName = "gpt-4o-mini";
var apiKey = Environment.GetEnvironmentVariable("AZURE_OPENAI_API_KEY");

AzureOpenAIClient azureClient = new(
    endpoint,
    new AzureKeyCredential(apiKey));
var chatClient = azureClient.GetChatClient(deploymentName);

List<ChatMessage> messages = new List<ChatMessage>()
{
    new SystemChatMessage("You are a helpful assistant."),
    new UserChatMessage("I am going to Paris, what should I see?"),
};

var requestOptions = new ChatCompletionOptions()
{
    MaxOutputTokenCount = 4096,
    Temperature = 1.0f,
    TopP = 1.0f,

};

var response = chatClient.CompleteChat(messages, requestOptions);
System.Console.WriteLine(response.Value.Content[0].Text);

Project

<Project Sdk="Microsoft.NET.Sdk">

  <PropertyGroup>
    <OutputType>Exe</OutputType>
    <TargetFramework>net9.0</TargetFramework>
    <ImplicitUsings>enable</ImplicitUsings>
    <Nullable>enable</Nullable>
  </PropertyGroup>

  <ItemGroup>
    <PackageReference Include="Azure.AI.OpenAI" Version="2.2.0-beta.5" />
    <PackageReference Include="OpenAI" Version="2.3.0" />
  </ItemGroup>

</Project>

Environment

Windows, .NET 9.0, Visual Studio

[github-actions]

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

[ericstj]

I found the problem. It's due to a renamed in OpenAI.ChatClient.

azure-sdk-for-net/sdk/openai/Azure.AI.OpenAI/src/Custom/Chat/AzureChatClient.Protocol.cs

Line 11 in 460b3bb

internal override PipelineMessage CreateCreateChatCompletionRequest(BinaryContent content, RequestOptions options)

This override is being ignored, so the URI doesn't end up getting formatted correctly for AzureOpenAI deployments.

This was introduced in the above change I referenced here:
openai/openai-dotnet@dff9bb5#diff-5d5ccdf27249bd63ef574adc5967dee094b135dc3c84a3ca9580470c8adb607fL59-R59

Without renaming this will be broken.

It seems a similar issue happened before 9971fc8#diff-43ac532e15843974b4cb777d51456942e76bb47582932bb108685aa39ca67ed7L29-R18 worked around the bad name back in March @trrwilson