.Net Bug: AzureChatExtensionsOptions for Azure AI Search is generating incorrect search queries.

[Cobra86]

Describe the bug The AzureChatExtensionsOptions for Azure AI Search is generating incorrect search queries. When passing a simple query like "list plans," the extension alters it to "list azure plans," "azure subscription plans," etc., rather than passing the original or minimally altered query to Azure AI Search. This leads to inaccurate search results. The expected behaviour is that the query should remain close to the user's input, such as "plans" or "list plans." Also, I'm not passing anything to the RoleInformation field.

Expected behavior The query generated by AzureChatExtensionsOptions should closely reflect the user's input, without adding unnecessary terms like "azure" or "subscription." For example, if the input is "list plans," the output should be "list plans" or simply "plans."

Platform

• AI Model: Azure OpenAI GPT4o
• OS: Windows
• IDE: Visual Studio
• Language: C#
• Source: NuGet package version 1.17.1

[dmytrostruk]

Hi @Cobra86 , I'm not sure if the issue is on Semantic Kernel side, because we are not modifying user input. Could you please include some code snippet, which will allow to reproduce the issue? Thanks in advance!

[Cobra86]

Hi @Cobra86 , I'm not sure if the issue is on Semantic Kernel side, because we are not modifying user input. Could you please include some code snippet, which will allow to reproduce the issue? Thanks in advance!

Sorry, I made a lot of changes since the new update, so i cant replicate or share the code. I didn't modify anything also I can see it in Intent field, It was set to list azure plan, or something relate to azure.

[Cobra86]

With the new update 21, it isn't passing modified query because now it's not returning anything when i typed list plans. I didn't update the index. i can confirm before when i type list plans it was returning some info.

[github-actions[bot]]

This issue is stale because it has been open for 90 days with no activity.

[markwallace-microsoft]

@dmytrostruk Can you take a look at this issue

[Cobra86]

@dmytrostruk @markwallace-microsoft This can be closed. Since the recent breaking changes to the Azure AI Search configuration, the issue is no longer present.