Merge pull request #185602 from HeidiSteen/heidist-fresh

PRMerger6 · web-flow · commit c6b3108ef19c · 2022-01-20T12:02:16.000-08:00
Portal tab consistency pass
diff --git a/articles/search/cognitive-search-attach-cognitive-services.md b/articles/search/cognitive-search-attach-cognitive-services.md
@@ -30,7 +30,9 @@ You can use the Azure portal, REST API, or an Azure SDK to attach a billable res
 
 If you leave the property unspecified, execution of billable skills will stop at 20 transactions per indexer invocation and a "Time Out" message will appear in indexer execution history.
 
-### [**Azure portal**](#tab/cogkey-portal)
+### [**Azure portal**](#tab/portal)
+
+1. [Sign in to Azure portal](https://portal.azure.com).
 
 1. Create a [multi-service Cognitive Services resource](../cognitive-services/cognitive-services-apis-create-account.md) in the [same region](#same-region-requirement) as your search service.
 
diff --git a/articles/search/knowledge-store-concept-intro.md b/articles/search/knowledge-store-concept-intro.md
@@ -76,17 +76,19 @@ To create knowledge store, use the portal or an API. You will need [Azure Storag
 
 Go with the portal approach for the fastest route to a finished knowledge store. Or, choose the REST API for a deeper understanding of how objects are defined and related.
 
-### [**Azure portal**](#tab/kstore-portal)
+### [**Azure portal**](#tab/portal)
 
 [**Create your first knowledge store in four steps**](knowledge-store-create-portal.md) using the **Import data** wizard.
 
-1. Define your data source
+1. [Sign in to Azure portal](https://portal.azure.com).
+
+1. Define your data source.
 
 1. Define  your skillset and specify a knowledge store.
 
 1. Define  an index schema. The wizard requires it and can infer one for you.
 
-1. Run the wizard. Extraction, enrichment, and storage occur in this last step.
+1. Complete the wizard. Extraction, enrichment, and storage occur in this last step.
 
 The wizard automates tasks that you would otherwise have to be handled manually. Specifically, both shaping and projections (definitions of physical data structures in Azure Storage) are created for you. 
 
diff --git a/articles/search/search-how-to-create-search-index.md b/articles/search/search-how-to-create-search-index.md
@@ -64,11 +64,11 @@ When you're ready to create the index, use a search client that can send the req
 
 During development, plan on frequent rebuilds. Because physical structures are created in the service, [dropping and re-creating indexes](search-howto-reindex.md) is necessary for many modifications. You might consider working with a subset of your data to make rebuilds go faster.
 
-### [**Azure portal**](#tab/index-portal)
+### [**Azure portal**](#tab/portal)
 
 Index design through the portal enforces requirements and schema rules for specific data types, such as disallowing full text search capabilities on numeric fields. 
 
-1. [Sign in to the Azure portal](https://portal.azure.com)
+1. [Sign in to Azure portal](https://portal.azure.com).
 
 1. In the search service Overview page, choose either option for creating a search index: 
 
diff --git a/articles/search/search-how-to-load-search-index.md b/articles/search/search-how-to-load-search-index.md
@@ -27,7 +27,7 @@ A search service accepts JSON documents that conform to the index schema.
 
 You can prepare these documents yourself, but if content resides in a [supported data source](search-indexer-overview.md#supported-data-sources), running an [indexer](search-indexer-overview.md) or the Import data wizard can automate document retrieval, JSON serialization, and indexing.
 
-### [**Azure portal**](#tab/import-portal)
+### [**Azure portal**](#tab/portal)
 
 Using Azure portal, the sole means for loading an index is the [Import Data wizard](search-import-data-portal.md). The wizard creates objects. If you want to load an existing index, you will need to use an alternative approach.
 
diff --git a/articles/search/search-howto-complex-data-types.md b/articles/search/search-howto-complex-data-types.md
@@ -71,7 +71,9 @@ As with any index definition, you can use the portal, [REST API](/rest/api/searc
 
 Other Azure SDKs provide samples in [Python](https://github.com/Azure/azure-sdk-for-python/blob/main/sdk/search/azure-search-documents/samples/sample_index_crud_operations.py), [Java](https://github.com/Azure/azure-sdk-for-java/blob/main/sdk/search/azure-search-documents/src/samples/java/com/azure/search/documents/indexes/CreateIndexExample.java), and [JavaScript](https://github.com/Azure/azure-sdk-for-js/blob/main/sdk/search/search-documents/samples/v11/javascript/indexOperations.js).
 
-### [**Azure portal**](#tab/complex-type-portal)
+### [**Azure portal**](#tab/portal)
+
+1. [Sign in to Azure portal](https://portal.azure.com).
 
 1. On the search service **Overview** page, select the **Indexes** tab.
 
diff --git a/articles/search/search-howto-create-indexers.md b/articles/search/search-howto-create-indexers.md
@@ -118,13 +118,19 @@ In terms of how indexers interact with an index, an indexer only checks field na
 
 When you are ready to create an indexer on a remote search service, you will need a search client, such as Azure portal or Postman, or code that instantiates an indexer client. We recommend the Azure portal or REST APIs for early development and proof-of-concept testing.
 
-### [**Azure portal**](#tab/indexer-portal)
+### [**Azure portal**](#tab/portal)
 
-The portal provides two options for creating an indexer: [**Import data wizard**](search-import-data-portal.md) and **New Indexer** that provides a visual editor for specifying an indexer definition. The wizard is unique in that it creates all of the required elements. Other approaches require that you have predefined a data source and index.
+1. [Sign in to Azure portal](https://portal.azure.com).
 
-The following screenshot shows where you can find these features in the portal. 
+1. On the search service Overview page, choose from two options: 
 
-  :::image type="content" source="media/search-howto-create-indexers/portal-indexer-client.png" alt-text="hotels indexer" border="true":::
+   + [**Import data wizard**](search-import-data-portal.md). The wizard is unique in that it creates all of the required elements. Other approaches require that you have predefined a data source and index.
+
+   + **New Indexer**, a visual editor for specifying an indexer definition. 
+
+   The following screenshot shows where you can find these features in the portal. 
+
+   :::image type="content" source="media/search-howto-create-indexers/portal-indexer-client.png" alt-text="hotels indexer" border="true":::
 
 ### [**REST**](#tab/indexer-rest)
 
diff --git a/articles/search/search-howto-run-reset-indexers.md b/articles/search/search-howto-run-reset-indexers.md
@@ -72,7 +72,7 @@ Reset also applies to just new and update operations. It will not trigger deleti
 
 Once you reset an indexer, you cannot undo the action.
 
-### [**Azure portal**](#tab/reset-indexer-portal)
+### [**Azure portal**](#tab/portal)
 
 1. [Sign in to Azure portal](https://portal.azure.com) and open the search service page.
 1. On the **Overview** page, select the **Indexers** tab.
diff --git a/articles/search/search-security-rbac.md b/articles/search/search-security-rbac.md
@@ -94,9 +94,7 @@ In this step, configure your search service to recognize an **authorization** he
 
 ### [**Azure portal**](#tab/config-svc-portal)
 
-1. Open the [Azure portal](https://ms.portal.azure.com).
-
-1. Navigate to your search service.
+1. [Sign in to Azure portal](https://portal.azure.com) and open the search service page.
 
 1. Select **Keys** in the left navigation pane.
 
diff --git a/articles/search/semantic-how-to-query-request.md b/articles/search/semantic-how-to-query-request.md
@@ -101,18 +101,17 @@ Similar to [scoring profiles](index-add-scoring-profiles.md), semantic configura
 
 ### [**Azure portal**](#tab/portal)
 
-To create a semantic configuration in the Azure portal:
+1. [Sign in to Azure portal](https://portal.azure.com) and navigate to a search service that has [semantic search enabled](semantic-search-overview.md#enable-semantic-search).
 
-1. Open the [Azure portal](https://portal.azure.com) and navigate to a search service that has semantic search [enabled](semantic-search-overview.md#enable-semantic-search).
-
-1. Navigate to the index you want to add a semantic configuration to.
+1. Open an index.
 
 1. Select **Semantic Configurations** and then select **Add Semantic Configuration**.
 
-1. At this point, a wizard will appear allowing you to select a title field, content fields, and keyword fields. Make sure to list content fields and keyword fields in priority order. After you're finished, select **OK** and then save the changes.
+   The **New Semantic Configuration** page opens with options for selecting a title field, content fields, and keyword fields. Make sure to list content fields and keyword fields in priority order.
 
-:::image type="content" source="./media/semantic-search-overview/create-semantic-config.png" alt-text="Screenshot that shows how to create a semantic configuration in the Azure portal." border="true":::
+   Select **OK** to save the changes.
 
+   :::image type="content" source="./media/semantic-search-overview/create-semantic-config.png" alt-text="Screenshot that shows how to create a semantic configuration in the Azure portal." border="true":::
 
 ### [**REST API**](#tab/rest)
 
