Merge pull request #235414 from gmndrg/main

Changes in cache documentation

Author: prmerger-automator[bot]

articles/search/cognitive-search-incremental-indexing-conceptual.md

@@ -7,7 +7,7 @@ author: HeidiSteen
 ms.author: heidist
 ms.service: cognitive-search
 ms.topic: conceptual
-ms.date: 01/31/2023
+ms.date: 04/21/2023
 ---
 
 # Incremental enrichment and caching in Azure Cognitive Search
@@ -80,23 +80,19 @@ If you know that a change to the skill is indeed superficial, you should overrid
 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.
 
 ```http
-PUT https://[servicename].search.windows.net/skillsets/[skillset name]?api-version=2020-06-30-Preview
-    {
-        "disableCacheReprocessingChangeDetection" : true
-    }
+PUT https://[servicename].search.windows.net/skillsets/[skillset name]?api-version=2020-06-30-Preview&disableCacheReprocessingChangeDetection
+  
 ```
 
 <a name="Bypass-data-source-check"></a>
 
 ### Bypass data source validation checks
 
-Most changes to a data source definition will invalidate the cache. However, for scenarios where you know that a change should not 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. 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.
+Most changes to a data source definition will invalidate the cache. However, for scenarios where you know that a change should not 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/update-data-source). 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.
 
 ```http
-PUT https://[search service].search.windows.net/datasources/[data source name]?api-version=2020-06-30-Preview
-    {
-        "ignoreResetRequirement" : true
-    }
+PUT https://[search service].search.windows.net/datasources/[data source name]?api-version=2020-06-30-Preview&ignoreResetRequirement
+ 
 ```
 
 <a name="Force-skillset-evaluation"></a>
@@ -181,9 +177,13 @@ REST API version `2020-06-30-Preview` or later provides incremental enrichment t
 
 + [Update Data Source](/rest/api/searchservice/update-data-source), when called with a preview API version, provides a new parameter named "ignoreResetRequirement", which should be set to true when your update action should not invalidate the cache. Use "ignoreResetRequirement" sparingly as it could lead to unintended inconsistency in your data that will not be detected easily.
 
+## Limitations
+
+If you are using [SharePoint indexer (Preview](search-howto-index-sharepoint-online.md), it is not recommended that the Incremental enrichment feature is used. There are conditions that may rise when indexing with this preview feature that would require to reset the indexer and invalidate the cache.
+
 ## Next steps
 
 Incremental enrichment is a powerful feature that extends change tracking to skillsets and AI enrichment. Incremental enrichment enables reuse of existing processed content as you iterate over skillset design. As a next step, enable caching on your indexers.
 
 > [!div class="nextstepaction"]
-> [Enable caching for incremental enrichment](search-howto-incremental-index.md)
+> [Enable caching for incremental enrichment](search-howto-incremental-index.md)