Azure OpenAI: duplication of api version

[koberghe]

App Version

3.23.12

API Provider

OpenAI Compatible

Model Used

o3

Roo Code Task Links (Optional)

No response

🔁 Steps to Reproduce

When configuring the Azure OpenAI provider, the API version must be specified in two separate locations: the Base URL field and the Set Azure API Version field.

For example, to use the o3 model, the Base URL must be the complete endpoint including the version string (e.g., .../chat/completions?api-version=2024-05-01-preview). In addition, the same version (2024-05-01-preview) must be selected in the Set Azure API Version field. (see screenshot)

If Base URL does not contain the version, I get a 404 Resource not found error.

If the Set Azure API Version field is left empty, the request fails with the error: o3 is enabled only for api versions 2024-12-01-preview and later. This suggests version 2024-12-01-preview is being used as a default, ignoring the version specified in the Base URL.

This duplication of information seems redundant and inconsistent with other features like codebase indexing, which does not have a separate version field and works correctly (see this ticket).

💥 Outcome Summary

404 Resource not found or o3 is enabled only for api versions 2024-12-01-preview and later

📄 Relevant Logs or Errors (Optional)

[dosubot]

The Roo Code documentation does not explain why the Azure OpenAI provider requires the API version in both the Base URL and the Set Azure API Version field, nor does it address the errors you described. This duplication appears to be a UI/UX inconsistency—other features like codebase indexing do not require a separate version field and work as expected. For now, the best workaround is to ensure you specify the same API version in both fields to avoid 404 or version mismatch errors. This looks like an area where the UI could be improved in future updates, so keeping an eye on release notes may be helpful.
Reference: OpenAI-compatible provider setup
Reference: Codebase Indexing FAQ

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}   

[roomote]

I am working on fixing this Azure OpenAI API version duplication issue. The problem is that users need to specify the API version in both the Base URL and the "Set Azure API Version" field, which is redundant and inconsistent with other features. I will investigate the codebase to understand how Azure OpenAI configuration is handled and implement a fix to eliminate this duplication.

[roomote]

Issue fixed! Created PR #5806 to eliminate Azure OpenAI API version duplication. The solution automatically extracts API version from Base URL when present, removing the need for separate field entry.