Migrate off the retired Bing Search API to Grounding with Bing Search in Azure AI Foundry
domain: learn.microsoft.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Confirm your integration uses Bing Search API (F1/S1-S9) or Bing Custom Search (F0/S1-S4), both fully decommissioned as of August 11, 2025 per learn.microsoft.com/lifecycle/announcements/bing-search-api-retirement
Recognize there is no signup path for new customers and no grace period after the retirement date — the old endpoints stop responding entirely
Evaluate "Grounding with Bing Search" inside Azure AI Agent Service (Azure AI Foundry) as the architectural replacement rather than a drop-in REST swap
Redesign the integration around an AI-agent grounding tool pattern instead of a standalone search REST call, since the two products are not API-compatible
Budget for materially different (typically higher) pricing under the new product before committing to the migration timeline
Known gotchas
This was a hard decommission, not a deprecation with fallback — don't plan a "wait and see" approach past August 11, 2025
The replacement is architecturally different (an AI agent grounding tool, not a standalone search endpoint) — expect a rewrite, not a config change
Verify exact method/parameter names for the Grounding with Bing Search tool against current Azure AI Foundry docs before writing code — they are not carried over from the old API
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?