Skip to main content
Weaviate Docs (migrated from docs.weaviate.io) Docs

Search documentation

Type to search this documentation.

On this pageOverview

Generative AI

Weaviate's integration with Azure OpenAI's APIs allows you to access their models' capabilities directly from Weaviate.

Configure a Weaviate collection to use a generative AI model with Azure OpenAI. Weaviate will perform retrieval augmented generation (RAG) using the specified model and your Azure OpenAI API key.

More specifically, Weaviate will perform a search, retrieve the most relevant objects, and then pass them to the Azure OpenAI generative model to generate outputs.

RAG integration illustration

Your Weaviate instance must be configured with the Azure OpenAI generative AI integration (generative-openai) module.

For Weaviate Cloud (WCD) users

This integration is enabled by default on Weaviate Cloud (WCD) instances.

For self-hosted users

You must provide a valid Azure OpenAI API key to Weaviate for this integration. Go to Azure OpenAI to sign up and obtain an API key.

Provide the API key to Weaviate using one of the following methods:

  • Set the AZURE_APIKEY environment variable that is available to Weaviate.
  • Provide the API key at runtime, as shown in the examples below.
Python
# Recommended: save sensitive data as environment variables
azure_key = os.getenv("AZURE_API_KEY")
JavaScript/TypeScript
const azureApiKey = process.env.AZURE_API_KEY || '';  // Replace with your inference API key

Configure a Weaviate index as follows to use an OpenAI Azure generative model.

To select the model, specify the Azure resource name.

Python
from weaviate.classes.config import Configureclient.collections.create(    "DemoCollection",    generative_config=Configure.Generative.azure_openai(        resource_name="<azure-resource-name>",        deployment_id="<azure-deployment-id>",    )    # Additional parameters not shown)
JavaScript/TypeScript
await client.collections.create({  name: 'DemoCollection',  generative: weaviate.configure.generative.azureOpenAI({    resourceName: '<azure-resource-name>',    deploymentId: '<azure-deployment-id>',  }),  // Additional parameters not shown});

Configure the following generative parameters to customize the model behavior.

Python
from weaviate.classes.config import Configureclient.collections.create(    "DemoCollection",    generative_config=Configure.Generative.azure_openai(        resource_name="<azure-resource-name>",        deployment_id="<azure-deployment-id>",        # # These parameters are optional        # frequency_penalty=0,        # max_tokens=500,        # presence_penalty=0,        # temperature=0.7,        # top_p=0.7,        # base_url="<custom-azure-url>"    )    # Additional parameters not shown)
JavaScript/TypeScript
await client.collections.create({  name: 'DemoCollection',  generative: weaviate.configure.generative.azureOpenAI({    resourceName: '<azure-resource-name>',    deploymentId: '<azure-deployment-id>',    // These parameters are optional    // frequencyPenalty: 0,    // maxTokens: 500,    // presencePenalty: 0,    // temperature: 0.7,    // topP: 0.7,  }),  // Additional parameters not shown});

For further details on these parameters, see consult the Azure OpenAI API documentation.

You can provide the API key as well as some optional parameters at runtime through additional headers in the request. The following headers are available:

  • X-Azure-Api-Key: The Azure API key.
  • X-Azure-Deployment-Id: The Azure deployment ID.
  • X-Azure-Resource-Name: The Azure resource name.

Any additional headers provided at runtime will override the existing Weaviate configuration.

Provide the headers as shown in the API credentials examples above.

After configuring the generative AI integration, perform RAG operations, either with the single prompt or grouped task method.

Single prompt RAG integration generates individual outputs per search result

To generate text for each object in the search results, use the single prompt method.

The example below generates outputs for each of the n search results, where n is specified by the limit parameter.

When creating a single prompt query, use braces {} to interpolate the object properties you want Weaviate to pass on to the language model. For example, to pass on the object's title property, include {title} in the query.

Python
collection = client.collections.use("DemoCollection")response = collection.generate.near_text(    query="A holiday film",  # The model provider integration will automatically vectorize the query    single_prompt="Translate this into French: {title}",    limit=2)for obj in response.objects:    print(obj.properties["title"])    print(f"Generated output: {obj.generated}")  # Note that the generated output is per object
JavaScript/TypeScript
let response;
const myCollection = client.collections.use("DemoCollection");

Grouped task RAG integration generates one output for the set of search results

To generate one text for the entire set of search results, use the grouped task method.

In other words, when you have n search results, the generative model generates one output for the entire group.

Python
collection = client.collections.use("DemoCollection")response = collection.generate.near_text(    query="A holiday film",  # The model provider integration will automatically vectorize the query    grouped_task="Write a fun tweet to promote readers to check out these films.",    limit=2)print(f"Generated output: {response.generative.text}")  # Note that the generated output is per queryfor obj in response.objects:    print(obj.properties["title"])
JavaScript/TypeScript
let response;
const myCollection = client.collections.use("DemoCollection");

See the Azure OpenAI documentation for a list of available models and their regional availability.

Once the integrations are configured at the collection, the data management and search operations in Weaviate work identically to any other collection. See the following model-agnostic examples:

Have a question or feedback? Here's how to reach us.

Suggest an edit

Propose a replacement for this page. The site team reviews it before applying any changes.

Export
Documentation menu