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
The **GenAI (Generative AI) Prompt** skill executes a *chat completion* request against a Large Language Model (LLM) deployed in Azure AI Foundry or Azure OpenAI in Azure AI Foundry Models. Use this capability to create new information that can be indexed and stored as searchable content.
18
+
The **GenAI (Generative AI) Prompt** skill executes a *chat completion* request against a large language model (LLM) deployed in Azure AI Foundry or Azure OpenAI in Azure AI Foundry Models. Use this capability to create new information that can be indexed and stored as searchable content.
19
19
20
20
Here are some examples of how the GenAI prompt skill can help you create content:
21
21
@@ -24,7 +24,7 @@ Here are some examples of how the GenAI prompt skill can help you create content
24
24
- Simplify complex content
25
25
- Perform any other task that you can articulate in a prompt
26
26
27
-
The GenAI Prompt skill is available in the [2025-05-01-preview REST API](/rest/api/searchservice/skillsets/create?view=rest-searchservice-2025-05-01-preview&preserve-view=true) only. The skill supports text, image, and multimodal content such as a PDF that contains text and images.
27
+
The GenAI Prompt skill is available in the [latest preview REST API](/rest/api/searchservice/skillsets/create?view=rest-searchservice-2025-08-01-preview&preserve-view=true). This skill supports text, image, and multimodal content, such as a PDF that contains text and images.
28
28
29
29
> [!TIP]
30
30
> It's common to use this skill combined with a data chunking skill. The following tutorials demonstrate image verbalization with two different data chunking techniques:
@@ -37,6 +37,8 @@ The GenAI Prompt skill is available in the [2025-05-01-preview REST API](/rest/a
37
37
38
38
You can use any [chat completion inference model](/azure/ai-foundry/model-inference/concepts/models) deployed in AI Foundry, such as GPT models, Deepseek R#, Llama-4-Mavericj, Cohere-command-r, and so forth.
39
39
40
+
For image verbalization, the model you use to analyze the image determines what image formats are supported.
41
+
40
42
Billing is based on the pricing of the model you use.
Copy file name to clipboardExpand all lines: articles/search/enrichment-cache-how-to-configure.md
+10-10Lines changed: 10 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ author: HeidiSteen
6
6
ms.author: heidist
7
7
ms.service: azure-ai-search
8
8
ms.topic: how-to
9
-
ms.date: 07/28/2025
9
+
ms.date: 08/27/2025
10
10
ms.update-cycle: 180-days
11
11
ms.custom:
12
12
- ignite-2023
@@ -55,10 +55,10 @@ You can use the Azure portal, preview APIs, or preview Azure SDK packages to ena
55
55
56
56
On new indexers, add the `cache` property in the indexer definition payload when calling Create or Update Indexer.
57
57
58
-
We recommend the latest preview for [Create or Update Indexer (2025-05-01-preview)](/rest/api/searchservice/indexers/create-or-update?view=rest-searchservice-2025-05-01-preview&preserve-view=true).
58
+
We recommend the latest preview REST API for [Create or Update Indexer](/rest/api/searchservice/indexers/create-or-update?view=rest-searchservice-2025-08-01-preview&preserve-view=true).
59
59
60
60
```https
61
-
POST https://[service name].search.windows.net/indexers?api-version=2025-05-01-preview
61
+
POST https://[service name].search.windows.net/indexers?api-version=2025-08-01-preview
62
62
{
63
63
"name": "<YOUR-INDEXER-NAME>",
64
64
"targetIndexName": "<YOUR-INDEX-NAME>",
@@ -82,10 +82,10 @@ For existing indexers that already have a skillset, use the following steps to a
82
82
83
83
### Step 1: Get the indexer definition
84
84
85
-
Start with a valid, work indexer that has these components: data source, skillset, index. Using an API client, send a [GET Indexer](/rest/api/searchservice/indexers/get?view=rest-searchservice-2025-05-01-preview&preserve-view=true) request to retrieve the indexer. When you use the preview API version to the GET the indexer, a `cache` property set to null is added to the definition automatically.
85
+
Start with a valid, work indexer that has these components: data source, skillset, index. Using an API client, send a [GET Indexer](/rest/api/searchservice/indexers/get?view=rest-searchservice-2025-08-01-preview&preserve-view=true) request to retrieve the indexer. When you use the preview API version to the GET the indexer, a `cache` property set to null is added to the definition automatically.
86
86
87
87
```http
88
-
GET https://[YOUR-SEARCH-SERVICE].search.windows.net/indexers/[YOUR-INDEXER-NAME]?api-version=2025-05-01-preview
88
+
GET https://[YOUR-SEARCH-SERVICE].search.windows.net/indexers/[YOUR-INDEXER-NAME]?api-version=2025-08-01-preview
89
89
Content-Type: application/json
90
90
api-key: [YOUR-ADMIN-KEY]
91
91
```
@@ -98,7 +98,7 @@ In the index definition, modify `cache` to include the following required and op
98
98
+ (Optional) `enableReprocessing` boolean property (`true` by default), indicates that incremental enrichment is enabled. Set to `false` if you want to suspend incremental processing while other resource-intensive operations, such as indexing new documents, are underway and then switch back to `true` later.
99
99
100
100
```http
101
-
POST https://[service name].search.windows.net/indexers?api-version=2025-05-01-preview
101
+
POST https://[service name].search.windows.net/indexers?api-version=2025-08-01-preview
102
102
{
103
103
"name": "<YOUR-INDEXER-NAME>",
104
104
"targetIndexName": "<YOUR-INDEX-NAME>",
@@ -119,17 +119,17 @@ POST https://[service name].search.windows.net/indexers?api-version=2025-05-01-p
119
119
[Reset Indexer](/rest/api/searchservice/indexers/reset) is required when setting up incremental enrichment for existing indexers to ensure all documents are in a consistent state. You can use the Azure portal or an API client for this task.
120
120
121
121
```https
122
-
POST https://[YOUR-SEARCH-SERVICE].search.windows.net/indexers/[YOUR-INDEXER-NAME]/reset?api-version=2025-05-01-preview
122
+
POST https://[YOUR-SEARCH-SERVICE].search.windows.net/indexers/[YOUR-INDEXER-NAME]/reset?api-version=2025-08-01-preview
123
123
Content-Type: application/json
124
124
api-key: [YOUR-ADMIN-KEY]
125
125
```
126
126
127
127
### Step 4: Save the indexer
128
128
129
-
[Update Indexer](/rest/api/searchservice/indexers/create-or-update?view=rest-searchservice-2025-05-01-preview&preserve-view=true) with a PUT request, where the body of the request includes `cache`.
129
+
[Update Indexer](/rest/api/searchservice/indexers/create-or-update?view=rest-searchservice-2025-08-01-preview&preserve-view=true) with a PUT request, where the body of the request includes `cache`.
130
130
131
131
```http
132
-
PUT https://[YOUR-SEARCH-SERVICE].search.windows.net/indexers/[YOUR-INDEXER-NAME]?api-version=2025-05-01-preview
132
+
PUT https://[YOUR-SEARCH-SERVICE].search.windows.net/indexers/[YOUR-INDEXER-NAME]?api-version=2025-08-01-preview
133
133
Content-Type: application/json
134
134
api-key: [YOUR-ADMIN-KEY]
135
135
{
@@ -159,7 +159,7 @@ To run indexer, you can use the Azure portal or the API. In the Azure portal, fr
159
159
Alternatively, you can use REST to [run the indexer](/rest/api/searchservice/indexers/run):
160
160
161
161
```http
162
-
POST https://[YOUR-SEARCH-SERVICE].search.windows.net/indexers/[YOUR-INDEXER-NAME]/run?api-version=2025-05-01-preview
162
+
POST https://[YOUR-SEARCH-SERVICE].search.windows.net/indexers/[YOUR-INDEXER-NAME]/run?api-version=2025-08-01-preview
Copy file name to clipboardExpand all lines: articles/search/enrichment-cache-how-to-manage.md
+12-12Lines changed: 12 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ author: HeidiSteen
6
6
ms.author: heidist
7
7
ms.service: azure-ai-search
8
8
ms.topic: how-to
9
-
ms.date: 07/28/2025
9
+
ms.date: 08/27/2025
10
10
ms.update-cycle: 180-days
11
11
ms.custom:
12
12
- ignite-2023
@@ -43,10 +43,10 @@ The cache is created when you specify the "cache" property and run the indexer.
43
43
44
44
The following example illustrates an indexer with caching enabled. See [Configure enrichment caching](enrichment-cache-how-to-configure.md) for full instructions.
45
45
46
-
To set the cache property, use a preview REST API [Create or Update Indexer](/rest/api/searchservice/indexers/create-or-update?view=rest-searchservice-2025-05-01-preview&preserve-view=true) or a preview Azure SDK package that provides the feature. You can also enable enrichment caching in the Import data wizard in the Azure portal.
46
+
To set the cache property, use latest preview REST API for [Create or Update Indexer](/rest/api/searchservice/indexers/create-or-update?view=rest-searchservice-2025-08-01-preview&preserve-view=true) or a preview Azure SDK package that provides the feature. You can also enable enrichment caching in the Import data wizard in the Azure portal.
47
47
48
48
```json
49
-
POST https://[YOUR-SEARCH-SERVICE-NAME].search.windows.net/indexers?api-version=2025-05-01-preview
49
+
POST https://[YOUR-SEARCH-SERVICE-NAME].search.windows.net/indexers?api-version=2025-08-01-preview
50
50
{
51
51
"name": "myIndexerName",
52
52
"targetIndexName": "myIndex",
@@ -96,7 +96,7 @@ If you know that a change to the skill is indeed superficial, you should overrid
96
96
Setting this parameter ensures that only updates to the skillset definition are committed and the change isn't evaluated for effects on the existing cache. Use a preview API version, 2020-06-30-Preview or later. We recommend the latest preview API.
97
97
98
98
```http
99
-
PUT https://[servicename].search.windows.net/skillsets/[skillset name]?api-version=2025-05-01-preview&disableCacheReprocessingChangeDetection
99
+
PUT https://[servicename].search.windows.net/skillsets/[skillset name]?api-version=2025-08-01-preview&disableCacheReprocessingChangeDetection
100
100
101
101
```
102
102
@@ -107,7 +107,7 @@ PUT https://[servicename].search.windows.net/skillsets/[skillset name]?api-versi
107
107
Most changes to a data source definition will invalidate the cache. However, for scenarios where you know that a change shouldn't invalidate the cache - such as changing a connection string or rotating the key on the storage account - append the `ignoreResetRequirement` parameter on the [data source update](/rest/api/searchservice/data-sources/create-or-update). Setting this parameter to true allows the commit to go through, without triggering a reset condition that would result in all objects being rebuilt and populated from scratch.
108
108
109
109
```http
110
-
PUT https://[search service].search.windows.net/datasources/[data source name]?api-version=2025-05-01-preview&ignoreResetRequirement
110
+
PUT https://[search service].search.windows.net/datasources/[data source name]?api-version=2025-08-01-preview&ignoreResetRequirement
111
111
112
112
```
113
113
@@ -117,13 +117,13 @@ PUT https://[search service].search.windows.net/datasources/[data source name]?a
117
117
118
118
The purpose of the cache is to avoid unnecessary processing, but suppose you make a change to a skill that the indexer doesn't detect (for example, changing something in external code, such as a custom skill).
119
119
120
-
In this case, you can use the [Reset Skills](/rest/api/searchservice/skillsets/reset-skills?view=rest-searchservice-2025-05-01-preview&preserve-view=true) to force reprocessing of a particular skill, including any downstream skills that have a dependency on that skill's output. This API accepts a POST request with a list of skills that should be invalidated and marked for reprocessing. After Reset Skills, follow with a [Run Indexer](/rest/api/searchservice/indexers/run) request to invoke the pipeline processing.
120
+
In this case, you can use the [Reset Skills](/rest/api/searchservice/skillsets/reset-skills?view=rest-searchservice-2025-08-01-preview&preserve-view=true) to force reprocessing of a particular skill, including any downstream skills that have a dependency on that skill's output. This API accepts a POST request with a list of skills that should be invalidated and marked for reprocessing. After Reset Skills, follow with a [Run Indexer](/rest/api/searchservice/indexers/run) request to invoke the pipeline processing.
121
121
122
122
## Re-cache specific documents
123
123
124
124
[Resetting an indexer](/rest/api/searchservice/indexers/reset) will result in all documents in the search corpus being reprocessed.
125
125
126
-
In scenarios where only a few documents need to be reprocessed, use [Reset Documents (preview)](/rest/api/searchservice/indexers/reset-docs?view=rest-searchservice-2025-05-01-preview&preserve-view=true) to force reprocessing of specific documents. When a document is reset, the indexer invalidates the cache for that document, which is then reprocessed by reading it from the data source. For more information, see [Run or reset indexers, skills, and documents](search-howto-run-reset-indexers.md).
126
+
In scenarios where only a few documents need to be reprocessed, use [Reset Documents (preview)](/rest/api/searchservice/indexers/reset-docs?view=rest-searchservice-2025-08-01-preview&preserve-view=true) to force reprocessing of specific documents. When a document is reset, the indexer invalidates the cache for that document, which is then reprocessed by reading it from the data source. For more information, see [Run or reset indexers, skills, and documents](search-howto-run-reset-indexers.md).
127
127
128
128
To reset specific documents, the request provides a list of document keys as read from the search index. If the key is mapped to a field in the external data source, the value that you provide should be the one used in the search index.
129
129
@@ -138,7 +138,7 @@ Depending on how you call the API, the request will either append, overwrite, or
138
138
The following example illustrates a reset document request:
139
139
140
140
```http
141
-
POST https://[search service name].search.windows.net/indexers/[indexer name]/resetdocs?api-version=2025-05-01-preview
141
+
POST https://[search service name].search.windows.net/indexers/[indexer name]/resetdocs?api-version=2025-08-01-preview
142
142
{
143
143
"documentKeys" : [
144
144
"key1",
@@ -189,10 +189,10 @@ Preview APIs provide extra properties on indexers. We recommend the latest previ
189
189
190
190
Skillsets and data sources can use the generally available version. In addition to the reference documentation, see [Configure caching for incremental enrichment](enrichment-cache-how-to-configure.md) for details about order of operations.
191
191
192
-
+[Create or Update Indexer (api-version=2025-05-01-preview)](/rest/api/searchservice/indexers/create-or-update?view=rest-searchservice-2025-05-01-preview&preserve-view=true)
192
+
+[Create or Update Indexer (api-version=2025-08-01-preview)](/rest/api/searchservice/indexers/create-or-update?view=rest-searchservice-2025-08-01-preview&preserve-view=true)
+[Create or Update Skillset (api-version=2025-05-01-preview)](/rest/api/searchservice/skillsets/create-or-update?view=rest-searchservice-2025-05-01-preview&preserve-view=true) (New URI parameter on the request)
196
+
+[Create or Update Skillset (api-version=2025-08-01-preview)](/rest/api/searchservice/skillsets/create-or-update?view=rest-searchservice-2025-08-01-preview&preserve-view=true) (New URI parameter on the request)
197
197
198
-
+[Create or Update Data Source (api-version=2025-05-01-preview)](/rest/api/searchservice/data-sources/create-or-update?view=rest-searchservice-2025-05-01-preview&preserve-view=true), when called with a preview API version, provides a new parameter named "ignoreResetRequirement", which should be set to true when your update action shouldn't invalidate the cache. Use "ignoreResetRequirement" sparingly as it could lead to unintended inconsistency in your data that won't be detected easily.
198
+
+[Create or Update Data Source (api-version=2025-08-01-preview)](/rest/api/searchservice/data-sources/create-or-update?view=rest-searchservice-2025-08-01-preview&preserve-view=true), when called with a preview API version, provides a new parameter named "ignoreResetRequirement", which should be set to true when your update action shouldn't invalidate the cache. Use "ignoreResetRequirement" sparingly as it could lead to unintended inconsistency in your data that won't be detected easily.
0 commit comments