Merge pull request #210760 from HeidiSteen/heidist-fresh

[azure search] Freshness pass (nav pages, find encryption key)

Author: BCS2022

articles/search/cognitive-search-predefined-skills.md

@@ -7,7 +7,7 @@ author: HeidiSteen
 ms.author: heidist
 ms.service: cognitive-search
 ms.topic: conceptual
-ms.date: 08/12/2021
+ms.date: 09/09/2022
 ---
 # Built-in skills for text and image processing during indexing (Azure Cognitive Search)
 

articles/search/samples-dotnet.md

@@ -8,7 +8,7 @@ author: HeidiSteen
 ms.author: heidist
 ms.service: cognitive-search
 ms.topic: conceptual
-ms.date: 10/01/2021
+ms.date: 09/09/2022
 ---
 
 # .NET (C#) code samples for Azure Cognitive Search
@@ -58,7 +58,7 @@ Code samples from the Cognitive Search team demonstrate features and workflows.
 
 ## Other samples
 
-The following samples are also published by the Cognitive Search team, but are not referenced in documentation. Associated readme files provide usage instructions.
+The following samples are also published by the Cognitive Search team, but aren't referenced in documentation. Associated readme files provide usage instructions.
 
 | Samples | Description |
 |---------|-------------|

articles/search/samples-java.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/09/2022
 ---
 
 # Java code samples for Azure Cognitive Search
@@ -42,16 +42,16 @@ Code samples from the Cognitive Search team demonstrate features and workflows.
 
 | Samples | Article | 
 |---------|-------------|
-| [quickstart](https://github.com/Azure-Samples/azure-search-java-samples/tree/java-rest-api/quickstart) | Source code for [Quickstart: Create a search index in Java and REST](search-get-started-java.md). This sample has not been updated for the Java SDK. It calls the REST APIs. |
+| [quickstart](https://github.com/Azure-Samples/azure-search-java-samples/tree/java-rest-api/quickstart) | Source code for [Quickstart: Create a search index in Java and REST](search-get-started-java.md). This sample hasn't been updated for the Java SDK. It calls the REST APIs. |
 
 > [!Tip]
 > Try the [Samples browser](/samples/browse/?languages=java&products=azure-cognitive-search) to search for Microsoft code samples in GitHub, filtered by product, service, and language.
 
 ## Other samples
 
-The following samples are also published by the Cognitive Search team, but are not referenced in documentation. Associated readme files provide usage instructions.
+The following samples are also published by the Cognitive Search team, but aren't referenced in documentation. Associated readme files provide usage instructions.
 
 | Samples | Description |
 |---------|-------------|
 | [search-java-getting-started](https://github.com/Azure-Samples/azure-search-java-samples/tree/master/search-java-getting-started) | Uses the Java SDK client library to create, load, and query a search index. This sample is currently standalone. |
-| [search-java-indexer-demo](https://github.com/Azure-Samples/azure-search-java-samples/tree/java-rest-api/search-java-indexer-demo) | Demonstrates an Azure Cosmos DB indexer in Java. This sample has not been updated for the Java SDK. It calls the REST APIs.|
+| [search-java-indexer-demo](https://github.com/Azure-Samples/azure-search-java-samples/tree/java-rest-api/search-java-indexer-demo) | Demonstrates an Azure Cosmos DB indexer in Java. This sample hasn't been updated for the Java SDK. It calls the REST APIs.|

articles/search/samples-javascript.md

@@ -8,7 +8,7 @@ author: HeidiSteen
 ms.author: heidist
 ms.service: cognitive-search
 ms.topic: conceptual
-ms.date: 06/11/2021
+ms.date: 09/09/2022
 ---
 
 # JavaScript code samples for Azure Cognitive Search
@@ -60,7 +60,7 @@ Code samples from the Cognitive Search team demonstrate features and workflows.
 
 ## Other samples
 
-The following samples are also published by the Cognitive Search team, but are not referenced in documentation. Associated readme files provide usage instructions.
+The following samples are also published by the Cognitive Search team, but aren't referenced in documentation. Associated readme files provide usage instructions.
 
 | Samples | Description |
 |---------|-------------|

articles/search/samples-python.md

@@ -8,7 +8,7 @@ author: HeidiSteen
 ms.author: heidist
 ms.service: cognitive-search
 ms.topic: conceptual
-ms.date: 06/11/2021
+ms.date: 09/09/2022
 ---
 
 # Python code samples for Azure Cognitive Search

articles/search/search-security-get-encryption-keys.md

@@ -8,15 +8,15 @@ author: HeidiSteen
 ms.author: heidist
 ms.service: cognitive-search
 ms.topic: conceptual
-ms.date: 06/21/2021 
+ms.date: 09/09/2022 
 ms.custom: devx-track-azurepowershell
 ---
 
 # Find encrypted objects and information
 
 In Azure Cognitive Search, customer-managed encryption keys are created, stored, and managed in Azure Key Vault. If you need to determine whether an object is encrypted, or what key name or version was used in Azure Key Vault, use the REST API or an Azure SDK to retrieve the **encryptionKey** property from the object definition in your search service.
 
-Objects that are not encrypted with a customer-managed key will have an empty **encryptionKey** property. Otherwise, you might see a definition similar to the following example.
+Objects that aren't encrypted with a customer-managed key will have an empty **encryptionKey** property. Otherwise, you might see a definition similar to the following example.
 
 ```json
 "encryptionKey": {
@@ -34,47 +34,65 @@ The **encryptionKey** construct is the same for all encrypted objects. It's a fi
 
 ## Get the admin API key
 
-Before you can retrieve object definitions from a search service, you will need to provide an admin API key. Admin API keys are required on requests that query for object definitions and metadata. The easiest way to get the admin API key is through the portal.
+Before you can retrieve object definitions from a search service, you'll need to provide an admin API key. Admin API keys are required on requests that query for object definitions and metadata. The easiest way to get the admin API key is through the portal.
 
 1. Sign in to the [Azure portal](https://portal.azure.com/) and open the search service overview page.
 
-1. On the left side, click **Keys** and copy an admin API. An admin key is required for index and synonym map retrieval.
+1. On the left side, select **Keys** and copy an admin API. 
 
-For the remaining steps, switch to PowerShell and the REST API. The portal does not show encryption key information for any object.
+For the remaining steps, switch to PowerShell and the REST API. The portal doesn't show encryption key information for any object.
 
 ## Retrieve object properties
 
 Use PowerShell and REST to run the following commands to set up the variables and get object definitions. 
 
 Alternatively, you can also use the Azure SDKs for [.NET](/dotnet/api/azure.search.documents.indexes.searchindexclient.getindexes), [Python](/python/api/azure-search-documents/azure.search.documents.indexes.searchindexclient), [JavaScript](/javascript/api/@azure/search-documents/searchindexclient), and [Java](/java/api/com.azure.search.documents.indexes.searchindexclient.getindex).
 
+First, connect to your Azure account.
+
 ```powershell
-<# Connect to Azure #>
-$Connect-AzAccount
+Connect-AzAccount
+```
 
-<# Provide the admin API key used for search service authentication  #>
+Set up the headers used on each request in the current session. Provide the admin API key used for search service authentication.
+
+```powershell
 $headers = @{
 'api-key' = '<YOUR-ADMIN-API-KEY>'
 'Content-Type' = 'application/json'
 'Accept' = 'application/json' }
+```
 
-<# List all existing synonym maps #>
-$uri= 'https://<YOUR-SEARCH-SERVICE>.search.windows.net/synonyms?api-version=2020-06-30&$select=name'
-Invoke-RestMethod -Uri $uri -Headers $headers | ConvertTo-Json
+To return a list of all search indexes, set the endpoint to the indexes collection.
 
-<# List all existing indexes #>
+```powershell
 $uri= 'https://<YOUR-SEARCH-SERVICE>.search.windows.net/indexes?api-version=2020-06-30&$select=name'
 Invoke-RestMethod -Uri $uri -Headers $headers | ConvertTo-Json
+```
 
-<# Return a specific synonym map definition. The encryptionKey property is at the end #>
-$uri= 'https://<YOUR-SEARCH-SERVICE>.search.windows.net/synonyms/<YOUR-SYNONYM-MAP-NAME>?api-version=2020-06-30'
-Invoke-RestMethod -Uri $uri -Headers $headers | ConvertTo-Json
+To return a specific index definition, provide its name in the path. The encryptionKey property is at the end.
 
-<# Return a specific index definition. The encryptionKey property is at the end #>
+```powershell
 $uri= 'https://<YOUR-SEARCH-SERVICE>.search.windows.net/indexes/<YOUR-INDEX-NAME>?api-version=2020-06-30'
 Invoke-RestMethod -Uri $uri -Headers $headers | ConvertTo-Json
 ```
 
+To return synonym maps, set the endpoint to the synonyms collection and then send the request.
+
+```powershell
+$uri= 'https://<YOUR-SEARCH-SERVICE>.search.windows.net/synonyms?api-version=2020-06-30&$select=name'
+Invoke-RestMethod -Uri $uri -Headers $headers | ConvertTo-Json
+```
+
+The following example returns a specific synonym map definition, including the encryptionKey property at the end.
+
+```powershell
+$uri= 'https://<YOUR-SEARCH-SERVICE>.search.windows.net/synonyms/<YOUR-SYNONYM-MAP-NAME>?api-version=2020-06-30'
+Invoke-RestMethod -Uri $uri -Headers $headers | ConvertTo-Json
+```
+
+Use the same pattern to return the encryptionKey property for other top-level objects such as indexers, skillsets, data sources, and index aliases.
+
 ## Next steps
 
 We recommend that you [enable logging](../key-vault/general/logging.md) on Azure Key Vault so that you can monitor key usage.