Skip to content

Commit 45a0197

Browse files
committed
Incorporated Vinay's feedback
1 parent 4b46bff commit 45a0197

File tree

2 files changed

+14
-9
lines changed

2 files changed

+14
-9
lines changed

articles/search/search-multi-region.md

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -6,22 +6,24 @@ author: haileytap
66
ms.author: haileytapia
77
ms.service: azure-ai-search
88
ms.topic: conceptual
9-
ms.date: 06/23/2025
9+
ms.date: 07/11/2025
1010
---
1111

1212
# Multi-region deployments in Azure AI Search
1313

14-
Although Azure AI Search is a single-region service, you can achieve higher availability and resiliency by deploying multiple search services with identical configurations and content across multiple regions. This article describes the components of a multi-region solution, which relies on your custom script or code to handle failover if a service becomes unavailable.
14+
Although Azure AI Search is a single-region service, you can achieve higher availability and resiliency by deploying multiple search services with identical configurations and content across multiple regions.
15+
16+
This article describes the components of a multi-region solution, which relies on your custom script or code to handle failover if a service becomes unavailable.
1517

1618
For more information about the reliability features of Azure AI Search, including intra-regional resiliency via availability zones, see [Reliability in Azure AI Search](search-reliability.md).
1719

1820
## Why use multiple regions?
1921

2022
If you need two or more search services, creating them in different regions can meet the following operational requirements:
2123

22-
+ Resiliency to region outages. If there's an outage, Azure AI Search doesn't provide instant failover to another region.
24+
+ **Resiliency to region outages**. If there's an outage, Azure AI Search doesn't provide instant failover to another region.
2325

24-
+ Fast performance for a globally distributed application. If indexing and query requests come from around the world, users who are closest to the host data center experience faster performance. Creating more services in regions with close proximity to these users can equalize performance for everyone.
26+
+ **Fast performance for a globally distributed application**. If indexing and query requests come from around the world, users who are closest to the host data center experience faster performance. Creating more services in regions with close proximity to these users can equalize performance for everyone.
2527

2628
## Multi-region architecture
2729

articles/search/search-reliability.md

Lines changed: 8 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ author: haileytap
66
ms.author: haileytapia
77
ms.service: azure-ai-search
88
ms.topic: reliability-article
9-
ms.date: 07/02/2025
9+
ms.date: 07/11/2025
1010
ms.custom:
1111
- subject-reliability
1212
- ignite-2023
@@ -20,7 +20,7 @@ Reliability is a shared responsibility between you and Microsoft, so this articl
2020

2121
In Azure AI Search, you can achieve reliability by:
2222

23-
+ **Scaling a single search service**. Add multiple [replicas](search-capacity-planning.md#concepts-search-units-replicas-partitions) to increase availability and handle higher indexing and query workloads. If your region supports availability zones, replicas are automatically provisioned in different physical data centers for extra resiliency.
23+
+ **Scaling a single search service**. Add multiple [replicas](search-capacity-planning.md#concepts-search-units-replicas-partitions) to increase availability and handle higher indexing and query workloads. If your region supports availability zones, replicas are distributed across different physical data centers on a best-effort basis for extra resiliency.
2424

2525
+ **Deploying multiple search services across different regions**. Each service operates independently within its region. However, in a multi-service scenario, you have options for synchronizing content across all services. You can also use a load-balancing solution to redistribute requests or fail over if there's a service outage.
2626

@@ -44,7 +44,10 @@ Availability zones are physically separate groups of datacenters within each Azu
4444

4545
Azure AI Search is a zone-redundant service that spreads your replicas across availability zones. A search service runs in one region, while its replicas run in zones within that region.
4646

47-
When you add two or more replicas to your service, Azure AI Search automatically places each replica in a different availability zone. If your service has more than three replicas, they're distributed across zones as evenly as possible.
47+
When you add two or more replicas to your service, Azure AI Search strives to place each replica in a different availability zone. For services with more replicas than available zones, replicas are distributed across zones as evenly as possible.
48+
49+
> [!IMPORTANT]
50+
> Azure AI Search doesn't guarantee the exact placement of replicas, which are subject to capacity constraints, scaling operations, and other factors.
4851
4952
### Region support
5053

@@ -68,7 +71,7 @@ Each search service starts with one replica. Zone redundancy requires two or mor
6871

6972
### Configure availability zone support
7073

71-
If your search service meets the [requirements for zone redundancy](#requirements), no extra configuration is necessary. Azure AI Search automatically places your replicas in different availability zones.
74+
If your search service meets the [requirements for zone redundancy](#requirements), no extra configuration is necessary. Whenever possible, Azure AI Search attempts to place your replicas in different availability zones.
7275

7376
### Zone-down experience
7477

@@ -82,7 +85,7 @@ When an availability zone experiences an outage, your search service continues t
8285

8386
+ **Expected data loss**: A zone failure isn't expected to cause data loss.
8487

85-
+ **Expected downtime**: A zone failure isn't expected to cause downtime to your search service, but it can temporarily reduce your service's overall capacity. To maintain optimal performance, consider provisioning more replicas than you typically need.
88+
+ **Expected downtime**: A zone failure isn't expected to cause downtime to your search service, but it can temporarily reduce your service's overall capacity. To maintain optimal performance, consider provisioning more replicas than you typically need. Adding replicas during an outage is challenging, so overprovisioning helps ensure that your service can handle normal request volumes, even with reduced capacity.
8689

8790
+ **Traffic rerouting**: When a zone fails, Azure AI Search detects the failure and routes requests to active replicas in the surviving zones.
8891

0 commit comments

Comments
 (0)