Merge pull request #268018 from HeidiSteen/heidist-fix

[azure search] Revs on low-engagement articles

Author: American-Dipper

articles/search/media/search-incremental-index/portal-option.png

@@ -8,7 +8,7 @@ ms.service: cognitive-search
 ms.custom:
   - ignite-2023
 ms.topic: how-to
-ms.date: 02/29/2024
+ms.date: 03/04/2024
 ---
 
 # Enable caching for incremental enrichment in Azure AI Search
@@ -20,22 +20,31 @@ This article explains how to add caching to an enrichment pipeline so that you c
 
 Cached content is placed in Azure Storage using account information that you provide. The container, named `ms-az-search-indexercache-<alpha-numerc-string>`, is created when you run the indexer. It should be considered an internal component managed by your search service and must not be modified.
 
-If you're not familiar with setting up indexers, start with [indexer overview](search-indexer-overview.md) and then continue on to [skillsets](cognitive-search-working-with-skillsets.md) to learn about enrichment pipelines. For more background on key concepts, see [incremental enrichment](cognitive-search-incremental-indexing-conceptual.md).
-
 ## Prerequisites
 
-Azure Storage is used to store cached enrichments. The storage account must be [general purpose v2](../storage/common/storage-account-overview.md#types-of-storage-accounts).
-
-Preview APIs or beta Azure SDKs are required for enabling cache on an indexer. The portal does not currently provide an option for caching enrichment.
++ [Azure Storage](/azure/storage/common/storage-account-create) for storing cached enrichments. The storage account must be [general purpose v2](../storage/common/storage-account-overview.md#types-of-storage-accounts).
 
-If you are planning to [index blobs](search-howto-indexing-azure-blob-storage.md), and you require the documents to be removed from both your cache and index when they are deleted from your data source, it is necessary to enable a [deletion policy](search-howto-index-changed-deleted-blobs.md) within the indexer. Without this policy, the deletion from the cache is not supported.
++ [For blob indexing only](search-howto-indexing-azure-blob-storage.md), if you need synchronized document removal from both the cache and index when blobs are deleted from your data source, enable a [deletion policy](search-howto-index-changed-deleted-blobs.md) in the indexer. Without this policy, document deletion from the cache isn't supported.
 
+You should be familiar with setting up indexers. Start with [indexer overview](search-indexer-overview.md) and then continue on to [skillsets](cognitive-search-working-with-skillsets.md) to learn about enrichment pipelines. For more background on key concepts, see [incremental enrichment](cognitive-search-incremental-indexing-conceptual.md).
 
 > [!CAUTION]
 > If you're using the [SharePoint Online indexer (Preview)](search-howto-index-sharepoint-online.md), you should avoid incremental enrichment. Under certain circumstances, the cache becomes invalid, requiring an [indexer reset and run](search-howto-run-reset-indexers.md), should you choose to reload it.
 
 ## Enable on new indexers
 
+You can use the Azure portal, preview APIs, or beta Azure SDKs are required to enable an enrichment cache on an indexer.
+
+### [**Azure portal**](#tab/portal)
+
+1. On the left, select **Indexers**, and then select **Add indexer**.
+1. Provide an indexer name and an existing index, data source, and skillset.
+1. Enable incremental caching and set the Azure Storage account.
+
+   :::image type="content" source="media/search-incremental-index/portal-option.png" alt-text="Screenshot of the portal option for enrichment cache.":::
+
+### [**REST**](#tab/rest)
+
 On new indexers, add the "cache" property in the indexer definition payload when calling [Create or Update Indexer (2021-04-30-Preview)](/rest/api/searchservice/preview-api/create-or-update-indexer). You can also use the previous preview API version, 2020-06-30-Preview.
 
 ```https
@@ -49,13 +58,14 @@ POST https://[service name].search.windows.net/indexers?api-version=2021-04-30-P
             "storageConnectionString" : "<YOUR-STORAGE-ACCOUNT-CONNECTION-STRING>",
             "enableReprocessing": true
         },
-        "fieldMappings" : [],
-        "outputFieldMappings": [],
-        "parameters": []
-        }
+    "fieldMappings" : [],
+    "outputFieldMappings": [],
+    "parameters": []
     }
 ```
 
+---
+
 ## Enable on existing indexers
 
 For existing indexers that already have a skillset, use the following steps to add caching. As a one-time operation, reset and rerun the indexer in full to load the cache.
@@ -122,7 +132,7 @@ PUT https://[YOUR-SEARCH-SERVICE].search.windows.net/indexers/[YOUR-INDEXER-NAME
     }
 ```
 
-If you now issue another GET request on the indexer, the response from the service will include an `ID` property in the cache object. The alphanumeric string is appended to the name of the container containing all the cached results and intermediate state of each document processed by this indexer. The ID will be used to uniquely name the cache in Blob storage.
+If you now issue another GET request on the indexer, the response from the service includes an `ID` property in the cache object. The alphanumeric string is appended to the name of the container containing all the cached results and intermediate state of each document processed by this indexer. The ID is used to uniquely name the cache in Blob storage.
 
 ```http
     "cache": {
@@ -134,7 +144,7 @@ If you now issue another GET request on the indexer, the response from the servi
 
 ### Step 5: Run the indexer
 
-To run indexer, you can use the portal or the API. In the portal, from the indexers list, select the indexer and click **Run**. One advantage to using the portal is that you can monitor indexer status, note the duration of the job, and how many documents are processed. Portal pages are refreshed every few minutes.
+To run indexer, you can use the portal or the API. In the portal, from the indexers list, select the indexer and select **Run**. One advantage to using the portal is that you can monitor indexer status, note the duration of the job, and how many documents are processed. Portal pages are refreshed every few minutes.
 
 Alternatively, you can use REST to [run the indexer](/rest/api/searchservice/run-indexer):
 
@@ -150,13 +160,13 @@ api-key: [YOUR-ADMIN-KEY]
 
 ## Check for cached output
 
-Find the cache in Azure Storage, under Blob container. The container name will be  `ms-az-search-indexercache-<some-alphanumeric-string>`.
+Find the cache in Azure Storage, under Blob container. The container name is  `ms-az-search-indexercache-<some-alphanumeric-string>`.
 
-A cache is created and used by an indexer. Its content is not human readable.
+A cache is created and used by an indexer. Its content isn't human readable.
 
 To verify whether the cache is operational, modify a skillset and run the indexer, then compare before-and-after metrics for execution time and document counts. 
 
-Skillsets that include image analysis and Optical Character Recognition (OCR) of scanned documents make good test cases. If you modify a downstream text skill or any skill that is not image-related, the indexer can retrieve all of the previously processed image and OCR content from cache, updating and processing only the text-related changes indicated by your edits.  You can expect to see fewer documents in the indexer execution document count, shorter execution times, and fewer charges on your bill. 
+Skillsets that include image analysis and Optical Character Recognition (OCR) of scanned documents make good test cases. If you modify a downstream text skill or any skill that isn't image-related, the indexer can retrieve all of the previously processed image and OCR content from cache, updating and processing only the text-related changes indicated by your edits.  You can expect to see fewer documents in the indexer execution document count, shorter execution times, and fewer charges on your bill. 
 
 The [file set](https://github.com/Azure-Samples/azure-search-sample-data/tree/main/ai-enrichment-mixed-media) used in [cog-search-demo tutorials](cognitive-search-tutorial-blob.md) is a useful test case because it contains 14 files of various formats JPG, PNG, HTML, DOCX, PPTX, and other types. Change `en` to `es` or another language in the text translation skill for proof-of-concept testing of incremental enrichment.
 
@@ -166,7 +176,7 @@ The following error occurs if you forget to specify a preview API version on the
 
 `"The request is invalid. Details: indexer : A resource without a type name was found, but no expected type was specified. To allow entries without type information, the expected type must also be specified when the model is specified."`
 
-A 400 Bad Request error will also occur if you are missing an indexer requirement. The error message will specify any missing dependencies.
+A 400 Bad Request error will also occur if you're missing an indexer requirement. The error message specifies any missing dependencies.
 
 ## Next steps