It seems that something is wrong with recent model roll-outs, affecting Azure OpenAI Assistants. This is easy to reproduce: Visit Azure AI Foundry -> Azure OpenAI Service -> Playground -> Assistant Playground Create a new Assistant on regions where Assistant preview is available (e.g. sweden, or us east region where Assistant is supported.) Error case 1) Try to change any parameter (e.g. temperature) --> update will fail with strange error message such as "temperature is not supported" Error case 2) try any simple message with the assistant --> this will fail with strange message about either "reasoning_effort", or "stream" Note that All existing Assistants are affected too -> same errors occur The results are same also for REST API calls and SDK calls (tested with JAVA SDK beta.5 version)

Azure OpenAI Assistants suddenly not working properly (both Playground & API)

Tae-Gil Noh 10

It seems that something is wrong with recent model roll-outs, affecting Azure OpenAI Assistants.

This is easy to reproduce:

Visit Azure AI Foundry -> Azure OpenAI Service -> Playground -> Assistant Playground
Create a new Assistant on regions where Assistant preview is available (e.g. sweden, or us east region where Assistant is supported.)
Error case 1) Try to change any parameter (e.g. temperature) --> update will fail with strange error message such as "temperature is not supported"
Error case 2) try any simple message with the assistant --> this will fail with strange message about either "reasoning_effort", or "stream"
Note that
1. All existing Assistants are affected too -> same errors occur
2. The results are same also for REST API calls and SDK calls (tested with JAVA SDK beta.5 version)

Ajouz, Ali 0 Reputation points

2025-02-27T13:57:25.5833333+00:00

I can confirm this problem. It impacts existing deployments
Tae-Gil Noh 10 Reputation points

2025-02-28T13:54:32.99+00:00
I think I now have more information about why some users this occurs, and why some users are okay with the Assistant.

If the Assistant is created within OpenAI resource ==> does NOT work (both new and existing)

If the Assistant is created within AIServices as "Hub" ==> does work (both new and existing)

As an example, the following picture:

AIServices "ai-useast1testhub59971" --> Assistants works okay there, no problem.

OpenAI "omq-gpt-models-us-ea..." --> Assistant does NOT work at all, as of now.

Please note that, "AIServices" resource is a "AI Hub" which has been created with "Create Project" process of AI Foundary. "OpenAI" resource is a service resource created from Azure site (just like creating any service). As I see it now, Assistants are currently working only on "AIServices" type of resource, but not with "OpenAI" resource.

To the Azure or Azure vendor personal who reads this -- this is still a terrible bug that breaks many running and pre-setup OpenAI Assistants running on Azure. Please fix this ASAP. I hope the above investigation was helpful to report / communicate the bug to AOAI dev team.
Tae-Gil Noh 10 Reputation points

2025-02-28T13:56:35.77+00:00

This is still a bug, IMHO. Please fix this ASAP!!