Azure api-version definitions seem wrong or out of date

API
1

Not sure if this is the ideal place to report this, I’d like to move some calls to Azure, they require an api-version in their endpoint calls, but these definition files seem to be out of date or wrong?

For example, there’s a tools-choice Param which allows 3 values: none, auto or required.

My setup requires the “required” value, yet on Azure, it complains that only none or auto are the only correct values.

From the OpenAI docs:

tool_choice

string or object

Optional

Controls which (if any) tool is called by the model. none means the model will not call any tool and instead generates a message. auto means the model can pick between generating a message or calling one or more tools. required means the model must call one or more tools. Specifying a particular tool via {"type": "function", "function": {"name": "my_function"}} forces the model to call that tool.

none is the default when no tools are present. auto is the default if tools are present.

2

This is what I used in my config for their client, they have a lot of bugs on the platform, even in playground, assistants are not saving functions properly (reported the bugs 2 time, probably still not fixed…).

They say API version is 2024-05-01-preview but their version I think is older than OpenAI API version, that’s my feeling, they just put 2024 to look nice :sweat_smile:. If you play with my configuration and create an intentional bug to see the errors, they will give you recommendation for version in logging. :wink:

My entire code is build to use both Platforms Azure OpenAI and OpenAI:

3

Urgh that is annoying :slight_smile:

Also noticed that their content filter can sometimes act very strangely, I’ve had completions failing because their filter seems overtuned.