BULK EDIT: REST API LINKS, sevices, datasource

HeidiSteen · HeidiSteen · commit 3ddbbe72837c · 2024-09-17T15:39:38.000-07:00
diff --git a/articles/search/cognitive-search-tutorial-blob.md b/articles/search/cognitive-search-tutorial-blob.md
@@ -497,7 +497,7 @@ POST {{baseUrl}}/indexers?api-version=2024-07-01  HTTP/1.1
 
 Indexing and enrichment commence as soon as you submit the Create Indexer request. Depending on skillset complexity and operations, indexing can take a while.
 
-To find out whether the indexer is still running, call [Get Indexer Status](/rest/api/searchservice/get-indexer-status) to check the indexer status.
+To find out whether the indexer is still running, call [Get Indexer Status](/rest/api/searchservice/indexers/get-status) to check the indexer status.
 
 ```http
 ### Get Indexer Status (wait several minutes for the indexer to complete)
diff --git a/articles/search/monitor-azure-cognitive-search-data-reference.md b/articles/search/monitor-azure-cognitive-search-data-reference.md
@@ -200,7 +200,7 @@ The following operations can appear in a resource log.
 | Query.Lookup |  A lookup query against an index. See [Query types and composition](search-query-overview.md). |
 | Query.Search |  A full text search request against an index. See [Query types and composition](search-query-overview.md). |
 | Query.Suggest |  Type ahead query against an index. See [Query types and composition](search-query-overview.md). |
-| ServiceStats | This operation is a routine call to [Get Service Statistics](/rest/api/searchservice/get-service-statistics), either called directly or implicitly to populate a portal overview page when it's loaded or refreshed. |
+| ServiceStats | This operation is a routine call to [Get Service Statistics](/rest/api/searchservice/get-service-statistics/get-service-statistics), either called directly or implicitly to populate a portal overview page when it's loaded or refreshed. |
 | Skillsets.* | Applies to a skillset. Can be Create, Delete, Get, List. |
 
 ## Related content
diff --git a/articles/search/search-howto-connecting-azure-sql-database-to-azure-search-using-indexers.md b/articles/search/search-howto-connecting-azure-sql-database-to-azure-search-using-indexers.md
@@ -182,7 +182,7 @@ An indexer runs automatically when it's created. You can prevent this by setting
 
 ## Check indexer status
 
-To monitor the indexer status and execution history, send a [Get Indexer Status](/rest/api/searchservice/get-indexer-status) request:
+To monitor the indexer status and execution history, send a [Get Indexer Status](/rest/api/searchservice/indexers/get-status) request:
 
 ```http
 GET https://myservice.search.windows.net/indexers/myindexer/status?api-version=2024-07-01
diff --git a/articles/search/search-howto-index-azure-data-lake-storage.md b/articles/search/search-howto-index-azure-data-lake-storage.md
@@ -227,7 +227,7 @@ An indexer runs automatically when it's created. You can prevent this by setting
 
 ## Check indexer status
 
-To monitor the indexer status and execution history, send a [Get Indexer Status](/rest/api/searchservice/get-indexer-status) request:
+To monitor the indexer status and execution history, send a [Get Indexer Status](/rest/api/searchservice/indexers/get-status) request:
 
 ```http
 GET https://myservice.search.windows.net/indexers/myindexer/status?api-version=2024-07-01
diff --git a/articles/search/search-howto-index-cosmosdb.md b/articles/search/search-howto-index-cosmosdb.md
@@ -240,7 +240,7 @@ An indexer runs automatically when it's created. You can prevent this by setting
 
 ## Check indexer status
 
-To monitor the indexer status and execution history, send a [Get Indexer Status](/rest/api/searchservice/get-indexer-status) request:
+To monitor the indexer status and execution history, send a [Get Indexer Status](/rest/api/searchservice/indexers/get-status) request:
 
 ```http
 GET https://myservice.search.windows.net/indexers/myindexer/status?api-version=2024-07-01
diff --git a/articles/search/search-howto-indexing-azure-tables.md b/articles/search/search-howto-indexing-azure-tables.md
@@ -112,7 +112,7 @@ To avoid a full scan, you can use table partitions to narrow the scope of each i
 
   + In the data source definition, specify a query similar to the following example: `(PartitionKey ge <TimeStamp>) and (other filters)`. 
 
-  + Monitor indexer progress by using [Get Indexer Status API](/rest/api/searchservice/get-indexer-status), and periodically update the `<TimeStamp>` condition of the query based on the latest successful high-water-mark value. 
+  + Monitor indexer progress by using [Get Indexer Status API](/rest/api/searchservice/indexers/get-status), and periodically update the `<TimeStamp>` condition of the query based on the latest successful high-water-mark value. 
 
   + With this approach, if you need to trigger a full reindex, reset the data source query in addition to [resetting the indexer](search-howto-run-reset-indexers.md). 
 
@@ -199,7 +199,7 @@ An indexer runs automatically when it's created. You can prevent this by setting
 
 ## Check indexer status
 
-To monitor the indexer status and execution history, send a [Get Indexer Status](/rest/api/searchservice/get-indexer-status) request:
+To monitor the indexer status and execution history, send a [Get Indexer Status](/rest/api/searchservice/indexers/get-status) request:
 
 ```http
 GET https://myservice.search.windows.net/indexers/myindexer/status?api-version=2024-07-01
diff --git a/articles/search/search-indexer-how-to-access-private-sql.md b/articles/search/search-indexer-how-to-access-private-sql.md
@@ -175,7 +175,7 @@ This article assumes a [REST client](search-get-started-rest.md) and uses the RE
 
 1. Run the indexer. If the indexer execution succeeds and the search index is populated, the shared private link is working.
 
-You can monitor the status of the indexer in Azure portal or by using the [Indexer Status API](/rest/api/searchservice/get-indexer-status).
+You can monitor the status of the indexer in Azure portal or by using the [Indexer Status API](/rest/api/searchservice/indexers/get-status).
 
 You can use [**Search explorer**](search-explorer.md) in Azure portal to check the contents of the index.
 
diff --git a/articles/search/search-indexer-howto-access-private.md b/articles/search/search-indexer-howto-access-private.md
@@ -368,7 +368,7 @@ This step shows you how to configure the indexer to run in the private environme
     }
     ```
 
-After the indexer is created successfully, it should connect to the Azure resource over the private endpoint connection. You can monitor the status of the indexer by using the [Indexer Status API](/rest/api/searchservice/get-indexer-status).
+After the indexer is created successfully, it should connect to the Azure resource over the private endpoint connection. You can monitor the status of the indexer by using the [Indexer Status API](/rest/api/searchservice/indexers/get-status).
 
 > [!NOTE]
 > If you already have existing indexers, you can update them via the [PUT API](/rest/api/searchservice/indexers/create) by setting the `executionEnvironment` to `private` or using the JSON editor in the portal.
diff --git a/articles/search/search-indexer-overview.md b/articles/search/search-indexer-overview.md
@@ -146,7 +146,7 @@ For more information, see [Create an indexer](search-howto-create-indexers.md)
 
 After the first indexer run, you can [rerun it on demand](search-howto-run-reset-indexers.md) or [set up a schedule](search-howto-schedule-indexers.md).
 
-You can monitor [indexer status in the portal](search-howto-monitor-indexers.md) or through [Get Indexer Status API](/rest/api/searchservice/get-indexer-status). You should also [run queries on the index](search-query-create.md) to verify the result is what you expected.
+You can monitor [indexer status in the portal](search-howto-monitor-indexers.md) or through [Get Indexer Status API](/rest/api/searchservice/indexers/get-status). You should also [run queries on the index](search-query-create.md) to verify the result is what you expected.
 
 Indexers don't have dedicated processing resources. Based on this, indexers' status may show as idle before running (depending on other jobs in the queue) and run times may not be predictable. Other factors define indexer performance as well, such as document size, document complexity, image analysis, among others.
 
diff --git a/articles/search/search-limits-quotas-capacity.md b/articles/search/search-limits-quotas-capacity.md
@@ -86,7 +86,7 @@ Vector limits vary by service creation date and tier.
 
 + To check the age of your search service or learn more about vector indexes, see [Vector index size and staying under limits](vector-search-index-size.md).
 
-+ To view the vector quota in effect for your search service, use [GET Service Statistics](/rest/api/searchservice/get-service-statistics), or check the **Properties** and **Usage** tabs for your search service in the Azure portal.
++ To view the vector quota in effect for your search service, use [GET Service Statistics](/rest/api/searchservice/get-service-statistics/get-service-statistics), or check the **Properties** and **Usage** tabs for your search service in the Azure portal.
 
 #### Storage quota (GB)
 
diff --git a/articles/search/search-what-is-an-index.md b/articles/search/search-what-is-an-index.md
@@ -112,7 +112,7 @@ Although you can add new fields at any time, existing field definitions are lock
 
 In Azure AI Search, the physical structure of an index is largely an internal implementation. You can access its schema, query its content, monitor its size, and manage capacity, but the clusters themselves (indexes, [shards](index-similarity-and-scoring.md#sharding-effects-on-query-results), and other files and folders) are managed internally by Microsoft.
 
-You can monitor index size in the Indexes tab in the Azure portal, or by issuing a [GET INDEX request](/rest/api/searchservice/get-index) against your search service. You can also issue a [Service Statistics request](/rest/api/searchservice/get-service-statistics) and check the value of storage size.
+You can monitor index size in the Indexes tab in the Azure portal, or by issuing a [GET INDEX request](/rest/api/searchservice/get-index) against your search service. You can also issue a [Service Statistics request](/rest/api/searchservice/get-service-statistics/get-service-statistics) and check the value of storage size.
 
 The size of an index is determined by:
 

Original file line number	Diff line number	Diff line change
`@@ -368,7 +368,7 @@ This step shows you how to configure the indexer to run in the private environme`
`368`	`368`	`}`
`369`	`369`	```
`370`	`370`
`371`		`-After the indexer is created successfully, it should connect to the Azure resource over the private endpoint connection. You can monitor the status of the indexer by using the [Indexer Status API](/rest/api/searchservice/get-indexer-status).`
	`371`	`+After the indexer is created successfully, it should connect to the Azure resource over the private endpoint connection. You can monitor the status of the indexer by using the [Indexer Status API](/rest/api/searchservice/indexers/get-status).`
`372`	`372`
`373`	`373`	`> [!NOTE]`
`374`	`374`	> If you already have existing indexers, you can update them via the [PUT API](/rest/api/searchservice/indexers/create) by setting the `executionEnvironment` to `private` or using the JSON editor in the portal.