Grounding with Bing Search is not working

Question

According to this article: https://azure.microsoft.com/en-us/updates?id=483570 we need to replace Bing Search v7.0 with Grounding With Bing Search in "Agents" as described here: https://learn.microsoft.com/en-us/azure/ai-services/agents/how-to/tools/bing-grounding

We are heavy users of C# SemanticKernel and have until now used Bing Search v7.0 in a Function added to the kernel.

Since Bing Search is now deprecated, we will have to adjust the function to use Grounding with Bing Search.

This means that we have to rewrite a simple bicep deployment with a simple reference in our function to a rather complex "Agent" creation as described in the tutorial mentioned above.

We have several issues with that:

1: We now need to deploy an Azure Resource (Grounding with Bing Search) by hand or AzureCLI - no bicep/ARM template exists for this resource.

2: We have to write C# code logic, that creates an "Agent" that gets configured to use the resource, which is way more complex then just referencing the old Bing API v7.0 endpoint

3: All this needs to be done with a guide, that is completely off the rails - the https://learn.microsoft.com/en-us/azure/ai-services/agents/how-to/tools/bing-grounding documentation refers to Agents and Agents playground, in screenshots that do not align with the real world.

4: It is clear, that we are supposed to use assistants (which is still in preview), but there are no options to add "knowledge" to these assistants in the portal.

Our product relies on Bing Search. We were not planning on rewriting the interaction with Azure OpenAI to use assistants before assistants are out of preview - mainly because we use model switching a lot and the preview models do not support assistants.

Please advice a path out of this misery. We do not want to implement preview endpoints in our product. We do not want click-to-install or AzureCli on top of our existing bicep template, that rolls our our entire solution. Please device a way to bring back Bing Search v7.0 until these points are fixed.

Answer 1

Dear Axel,

Thank you for reaching out and sharing your concerns regarding the transition from Bing Search v7.0 to Grounding with Bing Search. I understand the challenges you’re facing, especially given the complexity of the new implementation and the lack of support for Bicep/ARM templates.

Lack of Bicep/ARM Support for Grounding with Bing Search Currently, Grounding with Bing Search requires manual deployment or Azure CLI, which disrupts your existing Bicep-based deployment workflow. While there is no official Bicep/ARM template for this resource yet, you can гse Azure CLI commands within your pipeline to automate the deployment of Grounding with Bing Search. Provide feedback to Microsoft via the Azure Feedback Portal to request Bicep/ARM support for this resource. Complexity of Agent Creation in C# The new Grounding with Bing Search requires creating and configuring an Agent, which is more complex than the previous Bing Search v7.0 integration. Refer to the official documentation for guidance on configuring the Agent. Consider encapsulating the Agent creation logic into a reusable C# library or helper class to reduce complexity in your main application code. Documentation and Real-World Alignment Issues The documentation for Grounding with Bing Search refers to Agents and the Agents Playground, which may not align with your current setup. Provide feedback on the documentation page to highlight discrepancies and request updates. Explore the Azure AI Services GitHub repository for sample code and community discussions that might offer practical insights.

Reliance on Preview Features Since Assistants are still in preview and lack certain features (e.g., model switching), you may want to delay adopting them until they are generally available. Continue using Bing Search v7.0 if possible, as it remains functional until fully deprecated. Monitor the Azure Updates page for announcements regarding the general availability of Assistants and related features. Temporary Workaround: Continue Using Bing Search v7.0. If Grounding with Bing Search does not meet your requirements at this time, you can continue using Bing Search v7.0 until a more suitable solution is available. However, be prepared to transition to the new approach once Bing Search v7.0 is fully deprecated. Long-Term Solution: Advocate for Improvements. To address the gaps in the current implementation. Submit feature requests for Bicep/ARM support and improved documentation via the Azure Feedback Portal. Engage with the Azure AI Services team through the Microsoft Q&A forum to share your feedback and seek guidance.

Evaluate whether you can temporarily continue using Bing Search v7.0. If transitioning to Grounding with Bing Search is necessary, use Azure CLI to automate the deployment and encapsulate the Agent creation logic in a reusable C# component. Provide feedback to Microsoft to advocate for Bicep/ARM support and improved documentation.

Let me know if you need further assistance or clarification.

Best regards,

Alex

p.s. If you found the answer helpful, please click on Upvote and Accept Answer. This will help other community members.