Merge pull request #211435 from HeidiSteen/heidist-fresh

v-dirichards · web-flow · commit dd08d8f5f03f · 2022-09-15T14:04:12.000-05:00
[azure search] Freshness pass on multitenancy article
diff --git a/articles/search/cognitive-search-predefined-skills.md b/articles/search/cognitive-search-predefined-skills.md
@@ -1,5 +1,5 @@
 ---
-title: Built-in text and image processing during indexing
+title: Built-in skills
 titleSuffix: Azure Cognitive Search
 description: Data extraction, natural language, and image processing skills add semantics and structure to raw content in an Azure Cognitive Search enrichment pipeline.
 
diff --git a/articles/search/samples-rest.md b/articles/search/samples-rest.md
@@ -8,7 +8,7 @@ author: HeidiSteen
 ms.author: heidist
 ms.service: cognitive-search
 ms.topic: conceptual
-ms.date: 01/27/2021
+ms.date: 09/15/2022
 ---
 
 # REST code samples for Azure Cognitive Search
@@ -19,8 +19,8 @@ REST is the definitive programming interface for Azure Cognitive Search, and all
 
 REST samples are usually developed and tested on Postman, but you can use any client that supports HTTP calls:
 
-+ Start with [Quickstart: Create an Azure Cognitive Search index using REST APIs](search-get-started-rest.md) for help in formulating HTTP calls.
-+ Try [Visual Studio Code extension for Azure Cognitive Search](search-get-started-vs-code.md), currently in preview, if you work in Visual Studio Code.
++ [Use Postman](search-get-started-rest.md). This quickstart explains how to formulate the HTTP request from end-to-end.
++ [Use the Visual Studio Code extension for Azure Cognitive Search](search-get-started-vs-code.md), currently in preview. This quickstart uses Azure integration and builds the requests internally, which means you can complete tasks more quickly.
 
 ## Doc samples
 
@@ -36,7 +36,7 @@ Code samples from the Cognitive Search team demonstrate features and workflows.
 | [projections](https://github.com/Azure-Samples/azure-search-postman-samples/tree/master/projections) | Source code for [Define projections in a knowledge store](knowledge-store-projections-examples.md). This article explains how to specify the physical data structures in a knowledge store.|
 | [index-encrypted-blobs](https://github.com/Azure-Samples/azure-search-postman-samples/commit/f5ebb141f1ff98f571ab84ac59dcd6fd06a46718) | Source code for [How to index encrypted blobs using blob indexers and skillsets](search-howto-index-encrypted-blobs.md). This article shows how to index documents in Azure Blob Storage that have been previously encrypted using Azure Key Vault. |
 
-> [!Tip]
+> [!TIP]
 > Try the [Samples browser](/samples/browse/?expanded=azure&languages=http&products=azure-cognitive-search) to search for Microsoft code samples in GitHub, filtered by product, service, and language.
 
 ## Other samples
diff --git a/articles/search/search-howto-monitor-indexers.md b/articles/search/search-howto-monitor-indexers.md
@@ -8,7 +8,7 @@ author: HeidiSteen
 ms.author: heidist
 ms.service: cognitive-search
 ms.topic: conceptual
-ms.date: 01/28/2021
+ms.date: 09/15/2022
 ---
 
 # Monitor indexer status and results in Azure Cognitive Search
@@ -17,32 +17,32 @@ You can monitor indexer processing in the Azure portal, or programmatically thro
 
 ## Monitor using Azure portal
 
-You can see the current status of all of your indexers in your search service Overview page. Portal pages refresh every few minutes, so you won't see evidence of a new indexer run right away.
+You can see the current status of all of your indexers in your search service Overview page. Portal pages refresh every few minutes, so you won't see evidence of a new indexer run right away. Select **Refresh** at the top of the page to immediately retrieve the most recent view.
 
    ![Indexers list](media/search-monitor-indexers/indexers-list.png "Indexers list")
 
 | Status | Description |
 |--------|-------------|
-| **In Progress** | Indicates active execution. The portal will report on partial information. As indexing progresses, you can watch the **Docs Succeeded** value grow in response. Indexers that process large volumes of data can take a long time to run. For example, indexers that handle millions of source documents can run for 24 hours, and then restart almost immediately. The status for high-volume indexers might always say **In Progress** in the portal. Even when an indexer is running, details are available about ongoing progress and previous runs. |
+| **In Progress** | Indicates active execution. The portal will report on partial information. As indexing progresses, you can watch the **Docs Succeeded** value grow in response. Indexers that process large volumes of data can take a long time to run. For example, indexers that handle millions of source documents can run for 24 hours, and then restart almost immediately to pick up where it left off. As such, the status for high-volume indexers might always say **In Progress** in the portal. Even when an indexer is running, details are available about ongoing progress and previous runs. |
 | **Success** | Indicates the run was successful. An indexer run can be successful even if individual documents have errors, if the number of errors is less than the indexer's **Max failed items** setting. |
 | **Failed** | The number of errors exceeded **Max failed items** and indexing has stopped. |
 | **Reset** | The indexer's internal change tracking state was reset. The indexer will run in full, refreshing all documents, and not just those with newer timestamps. |
 
-You can click on an indexer in the list to see more details about the indexer's current and recent runs.
+You can select on an indexer in the list to see more details about the indexer's current and recent runs.
 
    ![Indexer summary and execution history](media/search-monitor-indexers/indexer-summary.png "Indexer summary and execution history")
 
 The **Indexer summary** chart displays a graph of the number of documents processed in its most recent runs.
 
-The **Execution details** list shows up to 50 of the most recent execution results. Click on an execution result in the list to see specifics about that run. This includes its start and end times, and any errors and warnings that occurred.
+The **Execution details** list shows up to 50 of the most recent execution results. Select on an execution result in the list to see specifics about that run. This includes its start and end times, and any errors and warnings that occurred.
 
    ![Indexer execution details](media/search-monitor-indexers/indexer-execution.png "Indexer execution details")
 
-If there were document-specific problems during the run, they will be listed in the Errors and Warnings fields.
+If there were document-specific problems during the run, they'll be listed in the Errors and Warnings fields.
 
    ![Indexer details with errors](media/search-monitor-indexers/indexer-execution-error.png "Indexer details with errors")
 
-Warnings are common with some types of indexers, and do not always indicate a problem. For example indexers that use Cognitive Services can report warnings when image or PDF files don't contain any text to process. 
+Warnings are common with some types of indexers, and don't always indicate a problem. For example indexers that use Cognitive Services can report warnings when image or PDF files don't contain any text to process. 
 
 For more information about investigating indexer errors and warnings, see [Indexer troubleshooting guidance](search-indexer-troubleshooting.md).
 
@@ -55,13 +55,13 @@ Metric views can be filtered or split up by a set of predefined dimensions.
 | Metric Name  |  Description | Dimensions  | Sample use cases |
 |---|---|---|---|
 | Document processed count  | Shows the number of indexer processed documents.  | Data source name, failed, index name, indexer name, skillset name  | <br> - Can be referenced as a rough measure of throughput (number of documents processed by indexer over time) <br> - Set up to alert on failed documents | 
-|  Skill execution invocation count | Shows the number of skill invocations. | Data source name, failed, index name, indexer name, skill name, skill type, skillset name | <br> - Reference to ensure skills are invoked as expected by comparing relative invocation numbers between skills and number of skill invocation to the number of documents. <br> - Set up to alert on failed skill invocations |
+|  Skill execution invocation count | Shows the number of skill invocations. | Data source name, failed, index name, indexer name, skill name, skill type, skillset name | <br> - Reference to ensure skills are invoked as expected by comparing relative invocation numbers between skills and number of skill invocations to the number of documents. <br> - Set up to alert on failed skill invocations |
 
 The screenshot below shows the number of documents processed by indexers within a service over an hour, split up by indexer name.
 
    ![Indexer documents processed metric](media/search-monitor-indexers/indexers-documents-processed-metric.png "Indexer documents processed metric")
 
-You can also configure the graph to see the number of skill invocation over the same hour interval.
+You can also configure the graph to see the number of skill invocations over the same hour interval.
 
    ![Indexer skills invoked metric](media/search-monitor-indexers/indexers-skill-invocation-metric.png "Indexer skill invocation metric")
 
@@ -107,13 +107,13 @@ The response contains overall indexer status, the last (or in-progress) indexer
 
 Execution history contains up to the 50 most recent runs, which are sorted in reverse chronological order (most recent first).
 
-Note there are two different status values. The top level status is for the indexer itself. A indexer status of **running** means the indexer is set up correctly and available to run, but not that it's currently running.
+Note there are two different status values. The top level status is for the indexer itself. An indexer status of **running** means the indexer is set up correctly and available to run, but not that it's currently running.
 
 Each run of the indexer also has its own status that indicates whether that specific execution is ongoing (**running**), or already completed with a **success**, **transientFailure**, or **persistentFailure** status. 
 
 When an indexer is reset to refresh its change tracking state, a separate execution history entry is added with a **Reset** status.
 
-For more details about status codes and indexer monitoring data, see [Get Indexer Status](/rest/api/searchservice/get-indexer-status).
+For more information about status codes and indexer monitoring data, see [Get Indexer Status](/rest/api/searchservice/get-indexer-status).
 
 ## Monitor using .NET
 
@@ -163,15 +163,15 @@ Latest run
   Document Errors: 0, Warnings: 0
 ```
 
-Note there are two different status values. The top-level status is the status of the indexer itself. A indexer status of **Running** means that the indexer is set up correctly and available for execution, but not that it is currently executing.
+Note there are two different status values. The top-level status is the status of the indexer itself. An indexer status of **Running** means that the indexer is set up correctly and available for execution, but not that it's currently executing.
 
 Each run of the indexer also has its own status for whether that specific execution is ongoing (**Running**), or was already completed with a **Success** or **TransientError** status. 
 
 When an indexer is reset to refresh its change tracking state, a separate history entry is added with a **Reset** status.
 
 ## Next steps
 
-For more details about status codes and indexer monitoring information, refer to the following API reference:
+For more information about status codes and indexer monitoring information, see the following API reference:
 
 * [GetIndexerStatus (REST API)](/rest/api/searchservice/get-indexer-status)
 * [IndexerStatus](/dotnet/api/azure.search.documents.indexes.models.indexerstatus)
diff --git a/articles/search/search-indexer-field-mappings.md b/articles/search/search-indexer-field-mappings.md
@@ -16,7 +16,7 @@ ms.date: 09/14/2022
 
 ![Indexer Stages](./media/search-indexer-field-mappings/indexer-stages-field-mappings.png "indexer stages")
 
-When an [Azure Cognitive Search indexer](search-indexer-overview.md) loads a search index, it determines the data path  through source-to-destination field mappings. Implicit field mappings are internal and occur when field names and data types are compatible between the source and destination. 
+When an [Azure Cognitive Search indexer](search-indexer-overview.md) loads a search index, it determines the data path through source-to-destination field mappings. Implicit field mappings are internal and occur when field names and data types are compatible between the source and destination. 
 
 If inputs and outputs don't match, you can define explicit *field mappings* to set up the data path, as described in this article. Field mappings can also be used to introduce light-weight data conversion, such as encoding or decoding, through [mapping functions](#mappingFunctions). If more processing is required, consider [Azure Data Factory](../data-factory/index.yml) to bridge the gap.
 
diff --git a/articles/search/search-modeling-multitenant-saas-applications.md b/articles/search/search-modeling-multitenant-saas-applications.md
diff --git a/articles/search/search-monitor-logs-powerbi.md b/articles/search/search-monitor-logs-powerbi.md
