-
Notifications
You must be signed in to change notification settings - Fork 3.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
.Net: Bug: SK can't call AzureOpenAI o1 model #10201
Comments
Relate to Azure/azure-sdk-for-net#47809 |
Hi @rwjdk, can you please make sure you are indeed sending the |
@moonbox3: As I'm using AzureOpenAI services I'm not sending a version at any point in the call (just the deployment name which in my case is "o1") I've checked the raw request to make sure and no version is mentioned in there In Azure AI Studio the version is 2024-12-17 (the only option) But taking above image I saw something odd - The target URI that you do not choose yourself (and never use in SK says api-version=2024-12-01-preview so it could be an Azure bug [I'm in swedenCentral Azure Region]) Can one in SK alter the target URI version? |
Did a quick test with the Azure.AI.OpenAI (v2.1.0) nuget package directly and it gives the same error so I guess SK Team depends on having this dependency supporting/working first :-/ |
Yes, you can use a different Azure API version. Tagging @SergeyMenshykh for a specific example on how to in .Net. |
@moonbox3 I tried that but as the underlying platform do not yet support the version it still fails with a not implemented exception :-/ Assume this is what you mean: |
It's not supported by the Azure.AI.OpenAI SDK yet - https://github.com/Azure/azure-sdk-for-net/blob/main/sdk/openai/Azure.AI.OpenAI/src/Custom/AzureOpenAIClientOptions.cs |
Describe the bug
When doing an agent.InvokeAsync call against the o1 model (version:2024-12-17) in Azure Open AI service you get error:
"HTTP 400 (BadRequest)\r\n\r\nModel o1 is enabled only for api versions 2024-12-01-preview and later"
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A normal LLM respose (in this case json due to structured output)
Platform
Additional context
Issue is properly the transative use of the azure.ai.openai beta2 package. I tried manually bumping this to latest, but it gave an feature not implemented exception
The text was updated successfully, but these errors were encountered: