Last set of APIs for relinks

Author: HeidiSteen

articles/search/cognitive-search-attach-cognitive-services.md

@@ -133,9 +133,9 @@ Enrichments are billable operations. If you no longer need to call Azure AI serv
 
 ### [**REST**](#tab/cogkey-rest-remove)
 
-1. [Get Skillset](/rest/api/searchservice/get-skillset) so that you have the full definition.
+1. [Get Skillset](/rest/api/searchservice/skillsets/get) so that you have the full definition.
 
-1. Formulate an [Update Skillset](/rest/api/searchservice/update-skillset) request, providing the JSON definition of the skillset.
+1. Formulate an [Update Skillset](/rest/api/searchservice/skillsets/create-or-update) request, providing the JSON definition of the skillset.
 
 1. Remove the key in the body of the definition, and then send the request:
 

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

@@ -83,7 +83,7 @@ Modifying a skill and reprocessing of that skill typically go hand in hand. Howe
 
 If you know that a change to the skill is indeed superficial, you should override skill evaluation by setting the `disableCacheReprocessingChangeDetection` parameter to true:
 
-1. Call [Update Skillset](/rest/api/searchservice/update-skillset) and modify the skillset definition.
+1. Call [Update Skillset](/rest/api/searchservice/skillsets/create-or-update) and modify the skillset definition.
 1. Append the "disableCacheReprocessingChangeDetection=true" parameter on the request.
 1. Submit the change.
 

articles/search/cognitive-search-skill-deprecated.md

@@ -40,7 +40,7 @@ August 31, 2024
 
 Use [Microsoft.Skills.Text.V3.EntityRecognitionSkill](cognitive-search-skill-entity-recognition-v3.md) instead. It provides most of the functionality of the EntityRecognitionSkill at a higher quality. It also has richer information in its complex output fields.
 
-To migrate to the [Microsoft.Skills.Text.V3.EntityRecognitionSkill](cognitive-search-skill-entity-recognition-v3.md), make one or more of the following changes to your skill definition. You can update the skill definition using the [Update Skillset API](/rest/api/searchservice/update-skillset).
+To migrate to the [Microsoft.Skills.Text.V3.EntityRecognitionSkill](cognitive-search-skill-entity-recognition-v3.md), make one or more of the following changes to your skill definition. You can update the skill definition using the [Update Skillset API](/rest/api/searchservice/skillsets/create-or-update).
 
 1. *(Required)* Change the `@odata.type` from `"#Microsoft.Skills.Text.EntityRecognitionSkill"` to `"#Microsoft.Skills.Text.V3.EntityRecognitionSkill"`.
 
@@ -368,7 +368,7 @@ August 31, 2024
 
 Use [Microsoft.Skills.Text.V3.SentimentSkill](cognitive-search-skill-sentiment-v3.md) instead. It provides an improved model and includes the option to add opinion mining or aspect-based sentiment. As the skill is significantly more complex, the outputs are also very different.
 
-To migrate to the [Microsoft.Skills.Text.V3.SentimentSkill](cognitive-search-skill-sentiment-v3.md), make one or more of the following changes to your skill definition. You can update the skill definition using the [Update Skillset API](/rest/api/searchservice/update-skillset).
+To migrate to the [Microsoft.Skills.Text.V3.SentimentSkill](cognitive-search-skill-sentiment-v3.md), make one or more of the following changes to your skill definition. You can update the skill definition using the [Update Skillset API](/rest/api/searchservice/skillsets/create-or-update).
 
 > [!NOTE]
 > The skill outputs for the Sentiment Skill V3 are not compatible with the index definition based on the SentimentSkill. You will have to make changes to the index definition, skillset (later skill inputs and/or knowledge store projections) and indexer output field mappings to replace the sentiment skill with the new version.
@@ -396,7 +396,7 @@ August 31, 2024
 
 Use [Microsoft.Skills.Text.V3.EntityRecognitionSkill](cognitive-search-skill-entity-recognition-v3.md) instead. It provides most of the functionality of the NamedEntityRecognitionSkill at a higher quality. It also has richer information in its complex output fields.
 
-To migrate to the [Microsoft.Skills.Text.V3.EntityRecognitionSkill](cognitive-search-skill-entity-recognition-v3.md), make one or more of the following changes to your skill definition. You can update the skill definition using the [Update Skillset API](/rest/api/searchservice/update-skillset).
+To migrate to the [Microsoft.Skills.Text.V3.EntityRecognitionSkill](cognitive-search-skill-entity-recognition-v3.md), make one or more of the following changes to your skill definition. You can update the skill definition using the [Update Skillset API](/rest/api/searchservice/skillsets/create-or-update).
 
 1. *(Required)* Change the `@odata.type` from `"#Microsoft.Skills.Text.NamedEntityRecognitionSkill"` to `"#Microsoft.Skills.Text.V3.EntityRecognitionSkill"`.
 

articles/search/knowledge-store-projection-overview.md

@@ -164,7 +164,7 @@ Recall that projections are exclusive to knowledge stores, and aren't used to st
 
    1. From the skills array, determine which skill outputs should be referenced in the `source` of each projection. All projections have a source. The source can be the output of an upstream skill, but is often the output of a Shaper skill. The composition of your projection is determined through shapes. 
 
-1. If you're adding projections to an existing skillset, [update the skillset](/rest/api/searchservice/update-skillset) and [run the indexer](/rest/api/searchservice/indexers/run).
+1. If you're adding projections to an existing skillset, [update the skillset](/rest/api/searchservice/skillsets/create-or-update) and [run the indexer](/rest/api/searchservice/indexers/run).
 
 1. Check your results in Azure Storage. On subsequent runs, avoid naming collisions by deleting objects in Azure Storage or changing project names in the skillset.
 

articles/search/knowledge-store-projections-examples.md

@@ -265,7 +265,7 @@ You can process projections by following these steps:
 
 1. Set the knowledge store's `storageConnectionString` property to a valid V2 general purpose storage account connection string.  
 
-1. [Update the skillset](/rest/api/searchservice/update-skillset) by issuing a PUT request with your projection definition in the body of the skillset.
+1. [Update the skillset](/rest/api/searchservice/skillsets/create-or-update) by issuing a PUT request with your projection definition in the body of the skillset.
 
 1. [Run the indexer](/rest/api/searchservice/indexers/run) to put the skillset into execution. 
 

articles/search/search-howto-incremental-index.md

@@ -14,7 +14,7 @@ ms.date: 06/25/2024
 # Enable caching for incremental enrichment in Azure AI Search
 
 > [!IMPORTANT] 
-> This feature is in public preview under [supplemental terms of use](https://azure.microsoft.com/support/legal/preview-supplemental-terms/). The [preview REST API](/rest/api/searchservice/index-preview) supports this feature.
+> This feature is in public preview under [supplemental terms of use](https://azure.microsoft.com/support/legal/preview-supplemental-terms/). [Preview REST APIs](/rest/api/searchservice/index-preview) support this feature.
 
 This article explains how to add caching to an enrichment pipeline so that you can modify downstream enrichment steps without having to rebuild in full every time. By default, a skillset is stateless, and changing any part of its composition requires a full rerun of the indexer. With an [**enrichment cache**](cognitive-search-incremental-indexing-conceptual.md), the indexer can determine which parts of the document tree must be refreshed based on changes detected in the skillset or indexer definitions. Existing processed output is preserved and reused wherever possible. 
 

articles/search/search-synonyms.md

@@ -33,7 +33,7 @@ To create a synonym map, do so programmatically. The portal doesn't support syno
 
 ### [REST](#tab/rest)
 
-Use the [Create Synonym Map (REST API)](/rest/api/searchservice/create-synonym-map) to create a synonym map.
+Use the [Create Synonym Map (REST API)](/rest/api/searchservice/synonym-maps/create) to create a synonym map.
 
 ```http
 POST /synonymmaps?api-version=2024-07-01
@@ -251,4 +251,4 @@ If you have an existing index in a development (nonproduction) environment, expe
 ## Next steps
 
 > [!div class="nextstepaction"]
-> [Create a synonym map (REST API)](/rest/api/searchservice/create-synonym-map)
+> [Create a synonym map (REST API)](/rest/api/searchservice/synonym-maps/create)