Bing plugin marketplace page still instructs users to apply for retired Bing Search API key

[ianTPE]

Self Checks

• This is only for bug report, if you would like to ask a question, please head to Discussions.
• I have searched for existing issues Dify issues & Dify Official Plugins, including closed ones.
• I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
• [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:）
• Please do not modify this template :) and fill in all the required fields.

Dify version

N/A - Dify Marketplace plugin page issue

Plugin version

0.0.8

Cloud or Self Hosted

Cloud

Steps to reproduce

Summary

The Dify Marketplace Bing plugin page still instructs users to apply for a Bing API key on Azure, but Microsoft retired Bing Search APIs on 2025-08-11. Existing instances have been decommissioned and new signup is no longer possible.

This creates a documentation / marketplace mismatch: users following the current plugin setup instructions will attempt to obtain or configure an API that has already been retired.

Current behavior

The current Marketplace page for langgenius/bing (v0.0.8, updated 2026-04-27, 35,838 installs) still says:

Apply for Bing API Key on the Azure platform

Marketplace page:
https://marketplace.dify.ai/plugin/langgenius/bing

Microsoft retirement notice:
https://learn.microsoft.com/en-us/lifecycle/announcements/bing-search-api-retirement

Microsoft states that Bing Search APIs were retired on 2025-08-11 and existing instances were decommissioned. Customers are directed to migrate to Grounding with Bing Search as part of Azure AI Agents.

Related

• Original zh-hant-TW market/language bug: BingWebSearch can't use other Market and Language dify#7642 (Closed as not planned)
• Bing Search tool errors with claude-sonnet-4-6: The claude-sonnet-4-6 model encounters errors when invoking search tools such as Bocha and Bing in agent applications or agent nodes. #2994

Suggested fix

Please consider adding a deprecation / retirement warning to the active Marketplace page:

⚠️ Bing Search APIs were retired by Microsoft on 2025-08-11. This plugin no longer works with newly provisioned API keys, and Microsoft's recommended replacement (Grounding with Bing Search) is an Azure AI Agents tool with a different architecture, not a drop-in replacement for an HTTP search API.

It would also help to:

1. Remove the "Apply for Bing API Key on the Azure platform" instruction
2. Link to Microsoft's retirement notice
3. Recommend an alternative search plugin (e.g., Tavily, SearXNG, Google CSE) as the migration path for users who need web search in Dify workflows

Why this matters

This is not just outdated documentation — it is a hard technical blocker.

The plugin's source code (tools/bing/tools/bing_web_search.py) is hardcoded to call https://api.bing.microsoft.com/v7.0/search with the Ocp-Apim-Subscription-Key header, and parses Bing v7's JSON shape directly (webPages.value, news.value, entities.value, relatedSearches.value, computation.value).

Microsoft's recommended replacement, Grounding with Bing Search, is not an HTTP search API — it is an Azure AI Agents tool. Per Microsoft's official documentation:

• It is accessed through the Azure AI Agents SDK / REST API, not a search endpoint.
• Authentication is via Azure resource roles, not a subscription key header.
• The tool returns a model-generated response with citation annotations on a thread message, and Microsoft explicitly states: "Grounding with Bing Search tool does NOT return the tool output to developers and end users." — https://learn.microsoft.com/en-us/azure/ai-foundry/agents/how-to/tools/bing-grounding

Consequently, no API key obtained through Microsoft's recommended migration path can be made to work with this plugin without rewriting its entire request / response architecture. A user who follows the current Marketplace setup instructions today has no working path forward.

For zh-TW / Taiwan market users specifically, the original issue (langgenius/dify#7642) already showed that Bing's mkt=zh-hant-TW parameter was rejected — with the full v7 API now retired, there is no migration path documented anywhere in Dify's ecosystem.

✔️ Error log

No response

[dosubot]

Hi @ianTPE! I'm Dosu and I’m helping the dify-official-plugins team.

This is a well-documented and valid issue. I can confirm that the plugin's README still contains the instruction to "Please apply for an API Key on the Azure platform" [1], and the tool implementation in bing_web_search.py is hardcoded to call the Bing v7 API with Ocp-Apim-Subscription-Key authentication [2]. There are currently no open PRs or issues in this repository addressing the API retirement.

The provider configuration also defines subscription_key as a required credential [3], which ties the entire plugin to an authentication mechanism that can no longer be provisioned.

For users needing web search in Dify workflows today, alternative search plugins like Tavily, SearXNG, or Google Search are available in the marketplace as functional replacements.

To reply, just mention @dosu.

---

Docs are dead. Just use Dosu.

[Markzhangeth]

Hello, I see you're working on the Dify workflow project. We have a multi-model API transfer service compatible with OpenAI formats, supporting models like GPT, Claude, Gemini, and Kimi, suitable for developers to quickly integrate and reduce the cost of maintaining multiple models. If your project has API call requirements, I can give you some test credits to try it out. One-stop shop for large model APIs: https://xtokens.shop