Merge pull request #228471 from HeidiSteen/heidist-fix

v-regandowner · web-flow · commit a34eec339c88 · 2023-02-24T13:50:04.000-05:00
[azure search] Reliability template, phase 1
diff --git a/.openpublishing.redirection.json b/.openpublishing.redirection.json
@@ -13399,6 +13399,11 @@
             "redirect_url": "/previous-versions/azure/search/search-how-to-index-power-query-data-sources",
             "redirect_document_id": false
         },
+        {
+            "source_path_from_root": "/articles/search/search-performance-optimization.md",
+            "redirect_url": "/azure/search/search-reliability",
+            "redirect_document_id": true
+        },
         {
             "source_path_from_root": "/articles/search/cognitive-search-quickstart-ocr.md",
             "redirect_url": "/azure/search/cognitive-search-quickstart-blob",
diff --git a/articles/reliability/TOC.yml b/articles/reliability/TOC.yml
@@ -160,7 +160,7 @@
       - name: Azure Cache for Redis
         href: ../azure-cache-for-redis/cache-how-to-zone-redundancy.md?toc=/azure/reliability/toc.json&bc=/azure/reliability/breadcrumb/toc.json
       - name: Azure Cognitive Search
-        href: ../search/search-performance-optimization.md?toc=/azure/reliability/toc.json&bc=/azure/reliability/breadcrumb/toc.json
+        href: ../search/search-reliability.md?toc=/azure/reliability/toc.json&bc=/azure/reliability/breadcrumb/toc.json
       - name: Azure Container Instances
         href: reliability-containers.md
       - name: Azure Container Registry
diff --git a/articles/reliability/availability-zones-service-support.md b/articles/reliability/availability-zones-service-support.md
@@ -101,7 +101,7 @@ Azure offerings are grouped into three categories that reflect their _regional_
 | [Azure Bastion](../bastion/bastion-overview.md) | ![An icon that signifies this service is zone redundant.](media/icon-zone-redundant.svg) |
 | [Azure Batch](../batch/create-pool-availability-zones.md) | ![An icon that signifies this service is zone redundant.](media/icon-zone-redundant.svg) |
 | [Azure Cache for Redis](../azure-cache-for-redis/cache-high-availability.md) | ![An icon that signifies this service is zone redundant.](media/icon-zone-redundant.svg) ![An icon that signifies this service is zonal](media/icon-zonal.svg) |
-| [Azure Cognitive Search](../search/search-performance-optimization.md#availability-zones) | ![An icon that signifies this service is zone redundant.](media/icon-zone-redundant.svg) |
+| [Azure Cognitive Search](../search/search-reliability.md#availability-zones) | ![An icon that signifies this service is zone redundant.](media/icon-zone-redundant.svg) |
 | [Azure Container Apps](../container-apps/disaster-recovery.md) | ![An icon that signifies this service is zone redundant.](media/icon-zone-redundant.svg) |
 | [Azure Container Instances](../container-instances/availability-zones.md) | ![An icon that signifies this service is zonal](media/icon-zonal.svg) |
 | [Azure Container Registry](../container-registry/zone-redundancy.md) | ![An icon that signifies this service is zone redundant.](media/icon-zone-redundant.svg) |
diff --git a/articles/reliability/migrate-search-service.md b/articles/reliability/migrate-search-service.md
@@ -16,17 +16,17 @@ ms.custom: references_regions, subject-reliability
 
 This guide describes how to migrate Azure Cognitive Search from non-availability zone support to availability support.
 
-Azure Cognitive Search services can take advantage of availability support [in regions that support availability zones](../search/search-performance-optimization.md#availability-zones). Services with [two or more replicas](../search/search-capacity-planning.md) in these regions created after availability support was enabled can automatically utilize availability zones. Each replica will be placed in a different availability zone within the region. If you have more replicas than availability zones, the replicas will be distributed across availability zones as evenly as possible.
+Azure Cognitive Search services can take advantage of availability support [in regions that support availability zones](../search/search-reliability.md#availability-zones). Services with [two or more replicas](../search/search-capacity-planning.md) in these regions created after availability support was enabled can automatically utilize availability zones. Each replica will be placed in a different availability zone within the region. If you have more replicas than availability zones, the replicas will be distributed across availability zones as evenly as possible.
 
 If a search service was created before availability zone support was enabled in its region, the search service must be recreated to take advantage of availability zone support.
 
 ## Prerequisites
 
 The following are the current requirements/limitations for enabling availability zone support:
 
-- The search service must be in [a region that supports availability zones](../search/search-performance-optimization.md#availability-zones)
+- The search service must be in [a region that supports availability zones](../search/search-reliability.md#availability-zones)
 - The search service must be created after availability zone support was enabled in its region.
-- The search service must have [at least two replicas](../search/search-performance-optimization.md#high-availability)
+- The search service must have [at least two replicas](../search/search-reliability.md#high-availability)
 
 ## Downtime requirements
 
@@ -40,7 +40,7 @@ If you created your search service in a region that supports availability zones
 
 ### How to recreate your search service
 
-1. [Create a new search service](../search/search-create-service-portal.md) in the same region as the old search service. This region should [support availability zones on or after the current date](../search/search-performance-optimization.md#availability-zones). 
+1. [Create a new search service](../search/search-create-service-portal.md) in the same region as the old search service. This region should [support availability zones on or after the current date](../search/search-reliability.md#availability-zones). 
 
    >[!IMPORTANT]
    >The [free and basic tiers do not support availability zones](../search/search-sku-tier.md#feature-availability-by-tier), and so they should not be used.
@@ -63,4 +63,4 @@ To rebuild all of your search indexes, choose one of the following two options:
 > [ARM Quickstart Templates](https://azure.microsoft.com/resources/templates/)
 
 > [!div class="nextstepaction"]
-> [Learn about high availability in Azure Cognitive Search](../search/search-performance-optimization.md)
+> [Learn about high availability in Azure Cognitive Search](../search/search-reliability.md)
diff --git a/articles/reliability/reliability-guidance-overview.md b/articles/reliability/reliability-guidance-overview.md
@@ -48,7 +48,7 @@ Azure reliability guidance is a collection of service-specific reliability guide
 [Azure Batch](../batch/create-pool-availability-zones.md?toc=/azure/reliability/toc.json&bc=/azure/reliability/breadcrumb/toc.json)|
 [Azure Bot Service](reliability-bot.md)|
 [Azure Cache for Redis](../azure-cache-for-redis/cache-how-to-zone-redundancy.md?toc=/azure/reliability/toc.json&bc=/azure/reliability/breadcrumb/toc.json)|
-[Azure Cognitive Search](../search/search-performance-optimization.md?toc=/azure/reliability/toc.json&bc=/azure/reliability/breadcrumb/toc.json)|
+[Azure Cognitive Search](../search/search-reliability.md?toc=/azure/reliability/toc.json&bc=/azure/reliability/breadcrumb/toc.json)|
 [Azure Communications Gateway](../communications-gateway/reliability-communications-gateway.md?toc=/azure/reliability/toc.json&bc=/azure/reliability/breadcrumb/toc.json)|
 [Azure Container Instances](reliability-containers.md)|
 [Azure Container Registry](../container-registry/zone-redundancy.md?toc=/azure/reliability/toc.json&bc=/azure/reliability/breadcrumb/toc.json)|
diff --git a/articles/search/TOC.yml b/articles/search/TOC.yml
@@ -195,7 +195,7 @@
     - name: Plan and manage costs
       href: search-sku-manage-costs.md
     - name: Availability and recovery
-      href: search-performance-optimization.md
+      href: search-reliability.md
     - name: Availability migration guidance
       href: ../reliability/migrate-search-service.md
     - name: Multi-tenancy
diff --git a/articles/search/media/search-reliability/geo-redundancy.png b/articles/search/media/search-reliability/geo-redundancy.png
diff --git a/articles/search/media/search-reliability/geo-search-traffic-mgr.png b/articles/search/media/search-reliability/geo-search-traffic-mgr.png
diff --git a/articles/search/media/search-reliability/scale-indexers.png b/articles/search/media/search-reliability/scale-indexers.png
diff --git a/articles/search/search-capacity-planning.md b/articles/search/search-capacity-planning.md
@@ -99,7 +99,7 @@ Dedicated resources can accommodate larger sampling and processing times for mor
 
 1. Add replicas if you need high availability or if you experience slow query performance.
 
-   There are no guidelines on how many replicas are needed to accommodate query loads. Query performance depends on the complexity of the query and competing workloads. Although adding replicas clearly results in better performance, the result is not strictly linear: adding three replicas does not guarantee triple throughput. For guidance in estimating QPS for your solution, see [Scale for performance](search-performance-optimization.md)and [Monitor queries](search-monitor-queries.md).
+   There are no guidelines on how many replicas are needed to accommodate query loads. Query performance depends on the complexity of the query and competing workloads. Although adding replicas clearly results in better performance, the result is not strictly linear: adding three replicas does not guarantee triple throughput. For guidance in estimating QPS for your solution, see [Analyze performance](search-performance-analysis.md)and [Monitor queries](search-monitor-queries.md).
 
 > [!NOTE]
 > Storage requirements can be inflated if you include data that will never be searched. Ideally, documents contain only the data that you need for the search experience. Binary data isn't searchable and should be stored separately (maybe in an Azure table or blob storage). A field should then be added in the index to hold a URL reference to the external data. The maximum size of an individual search document is 16 MB (or less if you're bulk uploading multiple documents in one request). For more information, see [Service limits in Azure Cognitive Search](search-limits-quotas-capacity.md).
@@ -111,7 +111,7 @@ Queries per second (QPS) is an important metric during performance tuning, but i
 
 The Standard tiers can provide a balance of replicas and partitions. You can increase query turnaround by adding replicas for load balancing or add partitions for parallel processing. You can then tune for performance after the service is provisioned.
 
-If you expect high sustained query volumes from the outset, you should consider higher Standard tiers, backed by more powerful hardware. You can then take partitions and replicas offline, or even switch to a lower-tier service, if those query volumes don't occur. For more information on how to calculate query throughput, see [Azure Cognitive Search performance and optimization](search-performance-optimization.md).
+If you expect high sustained query volumes from the outset, you should consider higher Standard tiers, backed by more powerful hardware. You can then take partitions and replicas offline, or even switch to a lower-tier service, if those query volumes don't occur. For more information on how to calculate query throughput, see [Monitor queries](search-monitor-queries.md).
 
 The Storage Optimized tiers are useful for large data workloads, supporting more overall available index storage for when query latency requirements are less important. You should still use additional replicas for load balancing and additional partitions for parallel processing. You can then tune for performance after the service is provisioned.
 
diff --git a/articles/search/search-create-service-portal.md b/articles/search/search-create-service-portal.md
@@ -103,7 +103,7 @@ Some features are subject to regional availability. If you require any of follow
 
 Other features that have regional constraints:
 
-+ ["Availability Zones" in Scale for Performance](search-performance-optimization.md#availability-zones)
++ [Availability Zones](search-reliability.md#availability-zones)
 + [Azure roles for data plane operations](search-security-rbac.md) (Azure public cloud only)
 
 ## Choose a tier
diff --git a/articles/search/search-indexer-overview.md b/articles/search/search-indexer-overview.md
@@ -28,7 +28,7 @@ You can use an indexer as the sole means for data ingestion, or in combination w
 |----------|---------|
 | Single data source | This pattern is the simplest: one data source is the sole content provider for a search index. Most supported data sources provide some form of change detection so that subsequent indexer runs pick up the difference when content is added or updated in the source. |
 | Multiple data sources | An indexer specification can have only one data source, but the search index itself can accept content from multiple sources, where each indexer run brings new content from a different data provider. Each source can contribute its share of full documents, or populate selected fields in each document. For a closer look at this scenario, see [Tutorial: Index from multiple data sources](tutorial-multiple-data-sources.md). |
-| Multiple indexers | Multiple data sources are typically paired with multiple indexers if you need to vary run time parameters, the schedule, or field mappings. </br></br>[Cross-region scale out of Cognitive Search](search-performance-optimization.md#data-sync) is another scenario. You might have copies of the same search index in different regions. To synchronize search index content, you could have multiple indexers pulling from the same data source, where each indexer targets a different search index in each region.</br></br>[Parallel indexing](search-howto-large-index.md#parallel-indexing) of very large data sets also requires a multi-indexer strategy, where each indexer targets a subset of the data. |
+| Multiple indexers | Multiple data sources are typically paired with multiple indexers if you need to vary run time parameters, the schedule, or field mappings. </br></br>[Cross-region scale out of Cognitive Search](search-reliability.md#data-sync) is another scenario. You might have copies of the same search index in different regions. To synchronize search index content, you could have multiple indexers pulling from the same data source, where each indexer targets a different search index in each region.</br></br>[Parallel indexing](search-howto-large-index.md#parallel-indexing) of very large data sets also requires a multi-indexer strategy, where each indexer targets a subset of the data. |
 | Content transformation | Indexers drive [AI enrichment](cognitive-search-concept-intro.md). Content transforms are defined in a [skillset](cognitive-search-working-with-skillsets.md) that you attach to the indexer.|
 
 <a name="supported-data-sources"></a>
diff --git a/articles/search/search-reliability.md b/articles/search/search-reliability.md
@@ -1,19 +1,19 @@
 ---
-title: Availability and continuity
+title: Reliability in Azure Cognitive Search
 titleSuffix: Azure Cognitive Search
-description: learn how to make a search service highly available and resilient against period disruptions or even catastrophic failures.
+description: Find out about reliability in Azure Cognitive Search.
 
 author: LiamCavanagh
 ms.author: liamca
 ms.service: cognitive-search
 ms.topic: conceptual
-ms.date: 07/11/2022
-ms.custom: references_regions
+ms.date: 02/24/2023
+ms.custom: subject-reliability, references_regions
 ---
 
-# Availability and business continuity in Azure Cognitive Search
+# Reliability in Azure Cognitive Search
 
-In Cognitive Search, availability is achieved through multiple replicas, whereas business continuity (and disaster recovery) is achieved through multiple search services. This article provides guidance that you can use as a starting point for developing a strategy that meets your business requirements for both availability and continuous operations.
+In Cognitive Search, reliability and availability is achieved through multiple replicas, whereas business continuity (and disaster recovery) is achieved through multiple search services. This article provides guidance that you can use as a starting point for developing a strategy that meets your business requirements for both availability and continuous operations.
 
 <a name="scale-for-availability"></a>
 
@@ -37,7 +37,7 @@ If both the storage account and the search service are in the same region, netwo
 
 <a name="availability-zones"></a>
 
-## Availability Zones
+## Availability zone support
 
 [Availability Zones](../availability-zones/az-overview.md) are an Azure platform capability that divides a region's data centers into distinct physical location groups to provide high-availability, within the same region. If you use Availability Zones for Cognitive Search, individual replicas are the units for zone assignment. A search service runs within one region; its replicas run in different zones.
 
@@ -135,6 +135,6 @@ Otherwise, your application code used for creating and populating an index is th
 To learn more about the pricing tiers and services limits for each one, see [Service limits](search-limits-quotas-capacity.md). Review [Plan for capacity](search-capacity-planning.md) to learn more about partition and replica combinations, or checkout [Case Study: Use Cognitive Search to Support Complex AI Scenarios](https://techcommunity.microsoft.com/t5/azure-ai/case-study-effectively-using-cognitive-search-to-support-complex/ba-p/2804078) for real-world tips.
 
 <!--Image references-->
-[1]: ./media/search-performance-optimization/geo-redundancy.png
-[2]: ./media/search-performance-optimization/scale-indexers.png
-[3]: ./media/search-performance-optimization/geo-search-traffic-mgr.png
+[1]: ./media/search-reliability/geo-redundancy.png
+[2]: ./media/search-reliability/scale-indexers.png
+[3]: ./media/search-reliability/geo-search-traffic-mgr.png
diff --git a/articles/search/search-sku-tier.md b/articles/search/search-sku-tier.md
diff --git a/articles/search/whats-new.md b/articles/search/whats-new.md
