Hello all,

We are currently trying to implement the knowledge base connection and when we configure the reranking model we face the following error:

Also theoretically reranking is optional but still we cant proceed without a working one. We use version 1.3.25

Let me check the docs and codebase for this specific issue with Cohere reranking on Azure AI Foundry. I don't have access to tools to check the codebase directly right now. Based on your error, here's what's happening: *The issue: Azure AI Foundry's Cohere rerank models use a different API format than standard Cohere API. The "API version not supported" error suggests the platform is calling the model with an incompatible API version. Workarounds: 1. Skip reranking — Since it's optional, try selecting "None" or leaving reranker unconfigured and hit Save. If the UI still blocks you, that might be a bug worth reporting. 2. Use a different reranker — If you have access to Cohere directly (not via Azure), try adding that key and using it for reranking instead. 3. Try a chat model for reranking* — The UI says "Any LLM provider and model can be used" — try selecting a regular chat model like GPT-4 instead of a dedicated reranker. Could you confirm if leaving the reranker blank still blocks you from saving? That would help narrow down if this is a UI bug vs. the Azure API version mismatch. 🤖 Slack Agent

It definitely worked for me with classic LLMs, like qwen/sonnet

I know that Cohere Rerank is quite a special kind of model with own input/output types

perhaps that's the reason

I wonder if switching to a regular LLM may work as a temporary solution?

Yes! Using a regular LLM (like Qwen or Sonnet) for reranking instead of Cohere Rerank is a solid workaround. The platform supports LLM-based reranking, which prompts the model to score document relevance. Cohere Rerank via Azure AI Foundry uses a different API contract that doesn't seem to be fully supported yet. 🤖 Slack Agent

@user i have tried all the "normal" llms without success... will try a bit more.

hey! so I think there's two things here:

1. the form has some issues currently wrt the embedding configuration being optional

2. we don't currently support Cohere Rerank

we'll ship v1.3.26 later today with a fix for 1 and support for 2

thanks for the quick reply