Merge pull request #109340 from HeidiSteen/heidist-search

[Azure Cognitive Search] Search explorer as quickstart

Author: v-shils

articles/search/TOC.yml

@@ -21,6 +21,8 @@
       href: cognitive-search-quickstart-blob.md
     - name: Create a knowledge store
       href: knowledge-store-create-portal.md
+    - name: Query with Search explorer
+      href: search-explorer.md
   - name: C#
     href: search-get-started-dotnet.md
   - name: Java
@@ -231,8 +233,6 @@
       href: search-query-simple-examples.md
     - name: Use full Lucene syntax
       href: search-query-lucene-examples.md
-    - name: Use Search Explorer (portal)
-      href: search-explorer.md
     - name: Special characters and partial terms
       href: search-query-partial-matching.md
     - name: Query from Power Apps   

articles/search/media/search-explorer/search-explorer-cmd2.png

@@ -8,7 +8,7 @@ author: HeidiSteen
 ms.author: heidist
 ms.service: cognitive-search
 ms.topic: quickstart
-ms.date: 12/05/2019
+ms.date: 03/25/2020
 ---
 
 # Quickstart: Create a search app in the portal (Azure Cognitive Search)
@@ -19,13 +19,13 @@ If you don't have an Azure subscription, create a [free account](https://azure.m
 
 ## Prerequisites
 
-You will want to upgrade to the [latest version of Microsoft Edge](https://www.microsoft.com/edge) or use Google's Chrome browser for this quickstart at this time.
+Upgrade to the [latest version of Microsoft Edge](https://www.microsoft.com/edge) or use Google's Chrome browser for this quickstart.
 
 [Create an Azure Cognitive Search service](search-create-service-portal.md) or [find an existing service](https://ms.portal.azure.com/#blade/HubsExtension/BrowseResourceBlade/resourceType/Microsoft.Search%2FsearchServices) under your current subscription. You can use a free service for this quickstart. 
 
 [Create an index](search-create-index-portal.md) to use as the basis of your application. 
 
-This quickstart uses the built-in Real Estate sample data and index because it has thumbnail images. To create the index used in this exercise, run the **Import data** wizard, choosing the *realestate-us-sample* data source.
+This quickstart uses the built-in Real Estate sample data and index because it has thumbnail images (the wizard supports adding images to the results page). To create the index used in this exercise, run the **Import data** wizard, choosing the *realestate-us-sample* data source.
 
 ![data source page for sample data](media/search-create-app-portal/import-data-realestate.png)
 

articles/search/media/search-explorer/search-explorer-tab.png

@@ -1,45 +1,61 @@
 ---
 title: Search explorer query tool in Azure portal
 titleSuffix: Azure Cognitive Search
-description: Search explorer is built into the Azure portal, useful for exploring content and validating queries in Azure Cognitive Search. Enter strings for term or phrase search, or fully qualified search expressions with advanced syntax.
+description: In this Azure portal quickstart, use Search Explorer to learn query syntax, test query expressions, or inspect a search document. Search explorer queries indexes in Azure Cognitive Search. 
 
 manager: nitinme
 author: HeidiSteen
 ms.author: heidist
 ms.service: cognitive-search
-ms.topic: conceptual
-ms.date: 11/04/2019
+ms.topic: quickstart
+ms.date: 03/27/2020
 ---
 
-# Use Search explorer in the Azure portal for querying documents in Azure Cognitive Search 
+# Quickstart: Use Search explorer to run queries in the portal
 
-This article shows you how to query an existing Azure Cognitive Search index using **Search explorer** in the Azure portal. You can start Search explorer from the command bar to submit simple or full Lucene query expressions to any existing index in your service. 
+**Search explorer** is a built-in query tool used for running queries against a search index in Azure Cognitive Search. This tool makes it easy to learn query syntax, test a query or filter expression, or confirm the results of an index refresh by verifying newer content exists.
+
+This quickstart uses **realestate-us-sample-index** to demonstrate Search explorer. Requests are formulated using the [Search REST API](https://docs.microsoft.com/rest/api/searchservice/), with responses returned as JSON documents.
+
+## Prerequisites
+
++ [Create an Azure Cognitive Search service](search-create-service-portal.md) or [find an existing service](https://ms.portal.azure.com/#blade/HubsExtension/BrowseResourceBlade/resourceType/Microsoft.Search%2FsearchServices) under your current subscription. You can use a free service for this quickstart.
+
++ **realestate-us-sample-index** is used for this quickstart. Step through the [**Import data**](search-import-data-portal.md) wizard to generate the index from the built-in samples data source.
+
+## Start Search explorer
+
+1. In the [Azure portal](https://portal.azure.com), open the search service page from the dashboard or [find your service](https://ms.portal.azure.com/#blade/HubsExtension/BrowseResourceBlade/resourceType/Microsoft.Search%2FsearchServices).
+
+1. Open Search explorer from the command bar:
 
    ![Search explorer command in portal](./media/search-explorer/search-explorer-cmd2.png "Search explorer command in portal")
 
-## Basic search strings
+    Or use the embedded **Search explorer** tab on an open index:
 
-The following examples assume the built-in real estate sample index. You can create this index using the Import data wizard in the portal, choosing **Samples** as the data source.
+   ![Search explorer tab](./media/search-explorer/search-explorer-tab.png "Search explorer tab")
 
-### Example 1 - empty search
+## Unspecified query
 
-For a first look at your content, execute an empty search by clicking **Search** with no terms provided. An empty search is useful as a first query because it returns entire documents so that you can review document composition. On an empty search, there is no search rank and documents are returned in arbitrary order (`"@search.score": 1` for all documents). By default, 50 documents are returned in a search request.
+For a first look at content, execute an empty search by clicking **Search** with no terms provided. An empty search is useful as a first query because it returns entire documents so that you can review document composition. On an empty search, there is no search rank and documents are returned in arbitrary order (`"@search.score": 1` for all documents). By default, 50 documents are returned in a search request.
 
 Equivalent syntax for an empty search is `*` or `search=*`.
-
-   ```Input
+   
+   ```http
    search=*
    ```
 
    **Results**
 
    ![Empty query example](./media/search-explorer/search-explorer-example-empty.png "Unqualified or empty query example")
 
-### Example 2 - free text search
+## Free text search
 
-Free-form queries, with or without operators, are useful for simulating user-defined queries sent from a custom app to Azure Cognitive Search. Notice that when you provide query terms or expressions, search rank comes into play. The following example illustrates a free text search.
+Free-form queries, with or without operators, are useful for simulating user-defined queries sent from a custom app to Azure Cognitive Search. Only those fields attributed as **Searchable** in the index definition are scanned for matches. 
 
-   ```Input
+Notice that when you provide search criteria, such as query terms or expressions, search rank comes into play. The following example illustrates a free text search.
+
+   ```http
    Seattle apartment "Lake Washington" miele OR thermador appliance
    ```
 
@@ -49,34 +65,35 @@ Free-form queries, with or without operators, are useful for simulating user-def
 
    ![Free text query example](./media/search-explorer/search-explorer-example-freetext.png "Free text query example")
 
-### Example 3 - count of matching documents 
+## Count of matching documents 
 
-Add **$count** to get the number of matches found in an index. On an empty search, count is the total number of documents in the index. On a qualified search, it's the number of documents matching the query input.
+Add **$count=true** to get the number of matches found in an index. On an empty search, count is the total number of documents in the index. On a qualified search, it's the number of documents matching the query input.
 
-   ```Input1
+   ```http
    $count=true
    ```
+
    **Results**
 
    ![Count of documents example](./media/search-explorer/search-explorer-example-count.png "Count of matching documents in index")
 
-### Example 4 - restrict fields in search results
+## Limit fields in search results
 
-Add **$select** to limit results to the explicitly named fields for more readable output in **Search explorer**. To keep the search string and **$count=true**, prefix arguments with **&**. 
+Add [**$select**](search-query-odata-select.md) to limit results to the explicitly named fields for more readable output in **Search explorer**. To keep the search string and **$count=true**, prefix arguments with **&**. 
 
-   ```Input
+   ```http
    search=seattle condo&$select=listingId,beds,baths,description,street,city,price&$count=true
    ```
 
    **Results**
 
    ![Limit fields example](./media/search-explorer/search-explorer-example-selectfield.png "Restrict fields in search results")
 
-### Example 5 - return next batch of results
+## Return next batch of results
 
 Azure Cognitive Search returns the top 50 matches based on the search rank. To get the next set of matching documents, append **$top=100,&$skip=50** to increase the result set to 100 documents (default is 50, maximum is 1000), skipping the first 50 documents. Recall that you need to provide search criteria, such as a query term or expression, to get ranked results. Notice that search scores decrease the deeper you reach into search results.
 
-   ```Input
+   ```http
    search=seattle condo&$select=listingId,beds,baths,description,street,city,price&$count=true&$top=100&$skip=50
    ```
 
@@ -86,9 +103,9 @@ Azure Cognitive Search returns the top 50 matches based on the search rank. To g
 
 ## Filter expressions (greater than, less than, equal to)
 
-Use the **$filter** parameter when you want to specify precise criteria rather than free text search. This example searches for bedrooms greater than 3:
+Use the [**$filter**](search-query-odata-filter.md) parameter when you want to specify precise criteria rather than free text search. The field must be attributed as **Filterable** in the index. This example searches for bedrooms greater than 3:
 
-   ```Input
+   ```http
    search=seattle condo&$filter=beds gt 3&$count=true
    ```
 
@@ -98,9 +115,9 @@ Use the **$filter** parameter when you want to specify precise criteria rather t
 
 ## Order-by expressions
 
-Add **$orderby** to sort results by another field besides search score. An example expression you can use to test this out is:
+Add [**$orderby**](search-query-odata-orderby.md) to sort results by another field besides search score. The field must be attributed as **Sortable** in the index. An example expression you can use to test this out is:
 
-   ```Input
+   ```http
    search=seattle condo&$select=listingId,beds,price&$filter=beds gt 3&$count=true&$orderby=price asc
    ```
 
@@ -112,40 +129,29 @@ Both **$filter** and **$orderby** expressions are OData constructions. For more
 
 <a name="start-search-explorer"></a>
 
-## How to start Search explorer
-
-1. In the [Azure portal](https://portal.azure.com), open the search service page from the dashboard or [find your service](https://ms.portal.azure.com/#blade/HubsExtension/BrowseResourceBlade/resourceType/Microsoft.Search%2FsearchServices) in the service list.
+## Takeaways
 
-2. In the service overview page, click **Search explorer**.
-
-   ![Search explorer command in portal](./media/search-explorer/search-explorer-cmd2.png "Search explorer command in portal")
-
-3. Select the index to query.
-
-   ![Select the index to query](./media/search-explorer/search-explorer-changeindex-se2.png "Select the index")
-
-4. Optionally, set the API version. By default, the current generally available API version is selected, but you can choose a preview or older API if the syntax you want to use is version-specific.
-
-5. Once the index and API version is selected, enter search terms or fully qualified query expressions in the search bar and click **Search** to execute.
-
-   ![Enter search terms and click Search](./media/search-explorer/search-explorer-query-string-example.png "Enter search terms and click Search")
-
-Tips for searching in **Search explorer**:
+In this quickstart, you used **Search explorer** to query an index using the REST API.
 
 + Results are returned as verbose JSON documents so that you can view document construction and content, in entirety. You can use query expressions, shown in the examples, to limit which fields are returned.
 
 + Documents are composed of all fields marked as **Retrievable** in the index. To view index attributes in the portal, click *realestate-us-sample* in the **Indexes** list on the search overview page.
 
 + Free-form queries, similar to what you might enter in a commercial web browser, are useful for testing an end-user experience. For example, assuming the built-in realestate sample index, you could enter "Seattle apartments lake washington", and then you can use Ctrl-F to find terms within the search results. 
 
-+ Query and filter expressions must be articulated in a syntax supported by Azure Cognitive Search. The default is a [simple syntax](https://docs.microsoft.com/rest/api/searchservice/simple-query-syntax-in-azure-search), but you can optionally use [full Lucene](https://docs.microsoft.com/rest/api/searchservice/lucene-query-syntax-in-azure-search) for more powerful queries. [Filter expressions](https://docs.microsoft.com/rest/api/searchservice/odata-expression-syntax-for-azure-search) are an OData syntax.
++ Query and filter expressions are articulated in a syntax supported by Azure Cognitive Search. The default is a [simple syntax](https://docs.microsoft.com/rest/api/searchservice/simple-query-syntax-in-azure-search), but you can optionally use [full Lucene](https://docs.microsoft.com/rest/api/searchservice/lucene-query-syntax-in-azure-search) for more powerful queries. [Filter expressions](https://docs.microsoft.com/rest/api/searchservice/odata-expression-syntax-for-azure-search) are an OData syntax.
+
+## Clean up resources
+
+When you're working in your own subscription, it's a good idea at the end of a project to identify whether you still need the resources you created. Resources left running can cost you money. You can delete resources individually or delete the resource group to delete the entire set of resources.
+
+You can find and manage resources in the portal, using the **All resources** or **Resource groups** link in the left-navigation pane.
 
+If you are using a free service, remember that you are limited to three indexes, indexers, and data sources. You can delete individual items in the portal to stay under the limit. 
 
 ## Next steps
 
-The following resources provide additional query syntax information and examples.
+To learn more about query structures and syntax, use Postman or an equivalent tool to create query expressions that leverage more parts of the API. The [Search REST API](https://docs.microsoft.com/rest/api/searchservice/) is especially helpful for learning and exploration.
 
- + [Simple query syntax](https://docs.microsoft.com/rest/api/searchservice/simple-query-syntax-in-azure-search) 
- + [Lucene query syntax](https://docs.microsoft.com/rest/api/searchservice/lucene-query-syntax-in-azure-search) 
- + [Lucene query examples](search-query-lucene-examples.md) 
- + [OData Filter expression syntax](https://docs.microsoft.com/rest/api/searchservice/odata-expression-syntax-for-azure-search) 
+> [!div class="nextstepaction"]
+> [Create a basic query in Postman](search-query-simple-examples.md)

articles/search/search-create-app-portal.md

@@ -1,7 +1,7 @@
 ---
 title: Create a search index in the Azure portal
 titleSuffix: Azure Cognitive Search
-description: In this portal quickstart, learn how to use the Import Data wizard to create, load, and query your first search index in Azure Cognitive Search. 
+description: In this Azure portal quickstart, use the Import Data wizard to create, load, and query your first search index in Azure Cognitive Search. 
 
 author: tchristiani
 manager: nitinme