The Microsoft Bing Search APIs retired on August 11, 2025. Choose an alternative by the output your application needs: raw search results for an application-managed pipeline, grounded generated answers in an agent workflow, or content from an already-known URL. These are different contracts and should not be treated as interchangeable replacements.
Choose by the part of v7 your application used
| Existing dependency | Required replacement behavior | Acceptance check |
|---|---|---|
| Search result rows | Documented search endpoint returning the required fields | Titles, links, market controls and error semantics |
| A cited generated answer | A supported grounding workflow with its own agent contract | Answer, citations, limitations and current availability |
| Reading a known URL | Page extraction interface | Required passages and provenance |
| News, images or other specific surfaces | Documented support for the specific result type | Do not assume web-search output includes it |
The Microsoft retirement notice distinguishes the retired search service from a grounding option for AI agents. Inspect that option’s current documentation and account availability before committing. A grounding feature is not automatically a raw v7 result-array replacement. Azure AI Search also serves a different indexing and retrieval purpose; its name alone does not establish equivalence.
Write a migration acceptance record
List the old request fields your application actually sends and every response field it consumes. Name the required engine, locale and result surface. Save a representative query set and an empty-result/error case. Test the replacement against those requirements before changing application routing. If a necessary field is absent, record the incompatibility rather than silently substituting a snippet or rank.
For SearchCans Bing search, the request goes to POST /api/v1/search with t:"bing". The documented result list is data.organic and the source URL field is link. A follow-up Reader request is a separate operation for page text. A successful search response is not evidence that the complete article or document has been read.
Keep selection and implementation separate
This page owns the replacement decision. The Bing v7 migration guide owns old-endpoint scanning, environment-key changes and runnable request adaptation. General SERP billing is explained in the pricing-model guide. Provider prices and limits should come from their current official contract rather than an old comparison table.
After establishing an accepted response contract, use a controlled Google versus Bing comparison before choosing a result source for the same query task.
