Microsoft has confirmed it will sunset its public Bing Search API service on August 11, 2025, marking the end of an era for developers relying on this search integration tool. The shutdown impacts all tiers—from free users to enterprise clients—including legacy versions like Search v7 and Custom Search.

Once the deadline passes, Microsoft will disable all existing API resources and close new registration channels. A prominent banner now alerts users on the Bing Web Search API page, warning that new deployments are no longer possible.

As a replacement path, Microsoft pushes developers toward Azure AI Agent Service, specifically its "Grounding with Bing Search" feature designed to feed real-time web data into AI systems. While positioned as an upgrade, this shift demands adaptation to new technical architectures and payment models—details available through Microsoft's pricing portal.

The transition raises important compliance questions. Microsoft's documentation reveals that search queries and resource keys will route through Bing services rather than staying within Azure's standard boundaries. Though the company assures no end-user personal data gets transmitted, organizations must independently verify these workflows meet their regulatory requirements.

What should affected teams do now? Microsoft recommends auditing current API usage via the Azure portal to identify impacted resources. Early migration testing is crucial given the architectural differences between services. Some developers may need to explore third-party alternatives if Azure's solution doesn't align with their technical or budgetary constraints.

This strategic move reflects Microsoft's broader pivot toward AI-integrated services. By folding search capabilities into its Azure AI ecosystem, the company appears to prioritize cohesive developer experiences over standalone tools—but not without growing pains for existing implementations.

Key Points

1. Bing Search API shuts down permanently on August 11, 2025
2. Azure AI Agent Service becomes the recommended alternative
3. Data routing changes require compliance reviews
4. Pricing and architecture differences may impact migration plans
5. New user registrations are already blocked