mirror of
https://github.com/open-webui/open-webui.git
synced 2026-05-24 03:18:21 -05:00
[GH-ISSUE #14527] feat: Replacement for Bing Search #17290
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/open-webui#17290
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @decent-engineer-decent-datascientist on GitHub (May 30, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/14527
Check Existing Issues
Problem Description
Microsoft has officially announced the retirement of its Bing Search APIs (including v7 and Custom Search) effective August 11, 2025. After this date, existing instances will be decommissioned, and the API will no longer be available for new or existing users. Microsoft's recommended alternative is "Grounding with Bing Search" as part of Azure AI Agents, which is a more integrated solution within their Azure AI ecosystem and may not be a direct, standalone API replacement suitable for all existing use cases.
Desired Solution you'd like
Integration of Grounding with Bing Search:
https://learn.microsoft.com/en-us/azure/ai-services/agents/how-to/tools/bing-grounding?view=azure-python-preview&tabs=python&pivots=overview
Alternatives Considered
No response
Additional Context
I'm not sure this will entirely be possible. The "BingSearchTool" and even the REST API documentation show utilization via an "agents" workflow. From a precursory glance, I can't find a quick way to integrate this in. Some analysis help would be appreciated, and if there's a solution I can take on the implementation work and open a PR.
@tjbck commented on GitHub (May 31, 2025):
Yeah seems like "Grounding with Bing Search" is only available as part of Azure AI Agents to vendor lock you into their Azure ecosystem, as far as I can tell our bing search support will just have be deprecated from our end as well.