Web search on Azure Databricks

This page describes web search on Azure Databricks and how to use it to ground model responses with real-time information from the web. Web search is available for Anthropic models through Model Context Protocol (MCP).

Tip

Genie Code (Agent mode) can do this for you. Try this example prompt:

Query the databricks-gemini-2-5-pro model using the OpenAI client with the google_search parameter enabled, ask a question about a current event, and print the response.

Web search allows foundation models to retrieve up-to-date information from the internet during response generation. When web search is enabled, the model can search the web to find relevant information and incorporate it into its response. This is useful for questions about current events, recent data, or any topic where real-time information improves the response.

Enable web search for Anthropic models by using a web search MCP server, such as You.com from Azure Databricks Marketplace.

Anthropic models with MCP

Anthropic's native web search tool is not available through Azure Databricks Foundation Model APIs. Instead, you can add web search to Anthropic models using the Model Context Protocol (MCP) with a search provider such as You.com.

Set up the You.com MCP server

  1. Navigate to Marketplace > Agents > MCP Servers in your Azure Databricks workspace.
  2. Search for You.com and click Install.
  3. Configure the connection:
  • Connection name: Enter a name (for example, youcom_web_search).
  • Bearer token: Enter your You.com API key.
  1. Click Install.
  2. Grant USE CONNECTION privileges to appropriate users or groups under Catalog > Connections > [your connection] > Permissions.

After setup, the MCP server is available as a tool in AI Playground, agents, and other MCP-compatible clients. The proxy endpoint URL for your connection is:

https://<workspace_host>.databricks.com/api/2.0/mcp/external/<connection_name>

Use with Claude Code

If you use Claude Code with Azure Databricks Foundation Model APIs, add the You.com MCP server to enable web search:

claude mcp add youcom-search \
  --transport http \
  --url "https://<workspace_host>.databricks.com/api/2.0/mcp/external/<connection_name>" \
  --header "Authorization: Bearer <your-databricks-pat>"

Verify the server was added with claude mcp list.

Alternatively, add the server directly to ~/.claude.json:

{
  "mcpServers": {
    "youcom-search": {
      "type": "http",
      "url": "https://<workspace_host>.databricks.com/api/2.0/mcp/external/<connection_name>",
      "headers": {
        "Authorization": "Bearer <your-databricks-pat>"
      }
    }
  }
}

Supported models

Anthropic models (via MCP)

Web search via MCP is supported on all Anthropic foundation models that support tool use.

  • databricks-claude-sonnet-4-6
  • databricks-claude-sonnet-4-5
  • databricks-claude-opus-4-7
  • databricks-claude-opus-4-6
  • databricks-claude-opus-4-5
  • databricks-claude-opus-4-1
  • databricks-claude-sonnet-4

Data privacy and retention

When you enable web search through Azure Databricks Foundation Model APIs, the search runs on a Azure Databricks-hosted foundation model endpoint. The search query and results are processed by the hosted model regardless of which model your application calls. The same data-protection and retention terms that govern Model Serving apply to these requests:

  • Azure Databricks does not use inputs sent to Model Serving, or outputs from it, to train models. See Model Serving data protection.
  • Any temporary storage for abuse detection is kept in the same region as your workspace and is time-bounded. See Data retention.

The model formulates search queries from your prompt and sends them to an external search provider to retrieve results. Treat prompt content that reaches web search as data that leaves Azure Databricks for the search provider, and scope what your application sends accordingly.

Limitations

  • Web search is only available on pay-per-token foundation model endpoints. Provisioned throughput endpoints do not support web search.
  • Web search is not available for workspaces with HIPAA/BAA compliance enabled because web search queries are sent to external search services that are not HIPAA-compliant.
  • Web search results depend on the model's ability to formulate search queries and synthesize results. Response quality may vary.

Additional resources

  • Last updated on