Hi @Zaheer. Sadaf (Enterprise Services)
Thank you for your detailed follow‑up.
You are correct that the On‑Your‑Data and Chat Completions integration currently uses an internal Azure Cognitive Search API version (2023‑07‑01‑Preview) that doesn’t fully support query‑time scoring profiles, scoring parameters, or rank fusion with scoring profiles. This limitation causes scoring boosts like freshness to be ignored, even when "rankingOrder": "boostedRerankerScore" and a default scoring profile are set.
Root Cause
- The chat completion endpoint does not expose or pass
scoringProfile and scoringParameters fields in the search plugin section.
The internal API used by the model for "on‑your‑data" retrieval still calls an older search API version.
Semantic ranking (vector + hybrid rerank) overrides scoring profile ranks.
Current Workarounds
Option 1: Custom RAG Flow (Recommended) You can enforce scoring profiles by separating the steps:
Call Azure Cognitive Search REST API or SDK directly (using the 2025‑08‑01‑Preview API version or later).
Specify "scoringProfile": "freshness-profile" and related parameters.
Pass the retrieved documents (with applied boosts) to the Chat Completions API as context via messages or data_sources.
This ensures the scoring logic (freshness boost, etc.) is honored before semantic reranking from the model.
Option 2: Update to Newest Azure AI Foundry SDK If you’re using SDK‑based RAG (e.g., azure-ai-projects Python SDK), ensure it targets a search dependency with API version 2025‑08‑01‑preview or higher. You can override this version by defining a custom search connection in code:
urces": [
{
"type": "azure_search",
"parameters": {
"endpoint": f"https://{search_service}.search.windows.net",
"api_version": "2025-08-01-preview",
"authentication": {
"type": "system_assigned_managed_identity"
},
"index_name": search_index,
"scoring_profile": "freshness-profile",
"semantic_configuration": search_semantic_config
}
}
]
}
While the public Chat Playground may still reference an older API, the SDKs and REST custom integrations already allow using the new API version.
References
Azure OpenAI On‑Your‑Data OverviewAzure Cognitive Search Scoring ProfilesSemantic Search and Boosted RerankingAzure AI Foundry: Azure Search IntegrationAzure Search REST API (2025‑08‑01‑Preview)
https://free.blessedness.top/en-us/azure/search/index-add-scoring-profiles
https://free.blessedness.top/en-us/azure/search/semantic-how-to-enable-scoring-profiles
https://free.blessedness.top/en-us/azure/ai-foundry/openai/references/azure-search?tabs=python
https://free.blessedness.top/en-us/rest/api/searchservice/
At this time, Chat Completions does not support specifying scoring profiles directly in extra_body. Microsoft’s internal roadmap includes alignment of the On‑Your‑Data plugin with the new API versions in upcoming releases.
Please try the Custom RAG flow or explicit search connection override workaroundKindly let us know if the above helps or you need further assistance on this issue.
Please "upvote" if the information helped you. This will help us and others in the community as well.