You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/search/vector-search-overview.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,18 +9,18 @@ ms.service: azure-ai-search
9
9
ms.custom:
10
10
- ignite-2023
11
11
ms.topic: conceptual
12
-
ms.date: 05/08/2025
12
+
ms.date: 06/17/2025
13
13
---
14
14
15
-
# Vectors in Azure AI Search
15
+
# Vector search in Azure AI Search
16
16
17
-
Vector search is an approach in information retrieval that supports indexing and query execution over numeric representations of content. Because the content is numeric rather than plain text, matching is based on vectors that are most similar to the query vector, which enables matching across:
17
+
Vector search is an information retrieval approach that supports indexing and querying over numeric representations of content. Because the content is numeric rather than plain text, matching is based on vectors that are most similar to the query vector, which enables matching across:
18
18
19
-
+semantic or conceptual likeness ("dog" and "canine", conceptually similar yet linguistically distinct)
20
-
+multilingual content ("dog" in English and "hund" in German)
21
-
+multiple content types ("dog" in plain text and a photograph of a dog in an image file)
19
+
+Semantic or conceptual likeness. For example, "dog" and "canine" are conceptually similar but linguistically distinct.
20
+
+Multilingual content, such as "dog" in English and "hund" in German.
21
+
+Multiple content types, such as "dog" in plain text and an image of a dog.
22
22
23
-
This article provides [a high-level introduction to vector support](#vector-search-concepts) in Azure AI Search. It also explains integration with other Azure services and covers [terminology and concepts](#vector-search-concepts) related to vector search development.
23
+
This article provides a high-level introduction to vector support in Azure AI Search. It also explains integration with other Azure services and covers [terminology and concepts](#vector-search-concepts) related to vector search development.
24
24
25
25
We recommend this article for background, but if you'd rather get started, follow these steps:
26
26
@@ -29,7 +29,7 @@ We recommend this article for background, but if you'd rather get started, follo
29
29
> +[Create a vector index](vector-search-how-to-create-index.md)
You could also begin with the [vector quickstart](search-get-started-vector.md) or the [code samples on GitHub](https://github.com/Azure/azure-search-vector-samples).
32
+
You can also begin with the [vector quickstart](search-get-started-vector.md) or the [code samples on GitHub](https://github.com/Azure/azure-search-vector-samples).
Copy file name to clipboardExpand all lines: articles/search/vector-store.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -31,9 +31,9 @@ This article covers the key concepts for creating and managing a vector index, i
31
31
32
32
Azure AI Search supports two patterns for vector retrieval:
33
33
34
-
+**Classic search.** After users enter queries into a search bar, your application code or the search engine vectorizes the input and performs a vector search over the vector fields in your index. The search engine returns results as a flattened row set, and you can choose which fields to include in the response. Because there's no chat model or extra reasoning, you should include nonvector fields in your index to present human-readable results to users. For more information, see [Create a vector query](vector-search-how-to-query.md) and [Create a hybrid query](hybrid-search-how-to-query.md).
34
+
+**Classic search**. After users enter queries into a search bar, your application code or the search engine vectorizes the input and performs a vector search over the vector fields in your index. The search engine returns results as a flattened row set, and you can choose which fields to include in the response. Because there's no chat model or extra reasoning, you should include nonvector fields in your index to present human-readable results to users. For more information, see [Create a vector query](vector-search-how-to-query.md) and [Create a hybrid query](hybrid-search-how-to-query.md).
35
35
36
-
+**Generative search.** Language models use data from Azure AI Search to respond to user queries. An orchestration layer typically coordinates prompts and maintains context, feeding search results into chat models like GPT. This pattern is based on the [retrieval-augmented generation (RAG)](retrieval-augmented-generation-overview.md) architecture, where the search index supplies grounding data.
36
+
+**Generative search**. Language models use data from Azure AI Search to respond to user queries. An orchestration layer typically coordinates prompts and maintains context, feeding search results into chat models like GPT. This pattern is based on the [retrieval-augmented generation (RAG)](retrieval-augmented-generation-overview.md) architecture, where the search index supplies grounding data.
37
37
38
38
## Schema of a vector index
39
39
@@ -85,7 +85,7 @@ Vector indexes require more than just vector fields. For example, all indexes mu
85
85
]
86
86
```
87
87
88
-
Other fields, such as `content`, provide the human-readable equivalent of the `content_vector` field. If you're using language models exclusively for response formulation, you can omit nonvector content fields, but solutions that push search results directly to client apps should have nonvector content.
88
+
Other fields, such as the `content` field, provide the human-readable equivalent of the `content_vector` field. If you're using language models exclusively for response formulation, you can omit nonvector content fields, but solutions that push search results directly to client apps should have nonvector content.
89
89
90
90
Metadata fields are useful for filters, especially if they include origin information about the source document. Although you can't filter directly on a vector field, you can set prefilter or postfilter modes to filter before or after vector query execution.
0 commit comments