Update links to reliability content

johndowns · johndowns · commit 01f3baf3317d · 2024-11-21T14:58:32.000+13:00
diff --git a/articles/ai-services/custom-vision-service/overview.md b/articles/ai-services/custom-vision-service/overview.md
@@ -64,7 +64,7 @@ The Custom Vision portal can be used by the following web browsers:
 
 ## Backup and disaster recovery
 
-As a part of Azure, Custom Vision Service has components that are maintained across multiple regions. Service zones and regions are used by all of our services to provide continued service to our customers. For more information on zones and regions, see [Azure regions](/azure/availability-zones/az-overview). If you need additional information or have any issues, [contact support](/answers/topics/azure-custom-vision.html).
+As a part of Azure, Custom Vision Service has components that are maintained across multiple regions. Service zones and regions are used by all of our services to provide continued service to our customers. For more information on zones and regions, see [Azure regions](/azure/reliability/availability-zones-overview). If you need additional information or have any issues, [contact support](/answers/topics/azure-custom-vision.html).
 
 
 ## Data privacy and security
diff --git a/articles/ai-services/luis/luis-reference-regions.md b/articles/ai-services/luis/luis-reference-regions.md
@@ -23,7 +23,7 @@ LUIS authoring regions are supported by the LUIS portal. To publish a LUIS app t
 
 Authoring regions are the regions where the application gets created and the training take place.
 
-LUIS has the following authoring regions available with [paired fail-over regions](/azure/availability-zones/cross-region-replication-azure):
+LUIS has the following authoring regions available with [paired fail-over regions](/azure/reliability/cross-region-replication-azure):
 	
 * Australia east
 * West Europe
@@ -109,7 +109,7 @@ Learn more about the [authoring and prediction endpoints](developer-reference-re
 
 Each region has a secondary region to fail over to. Failover will only happen in the same geographical region.
 
-Authoring regions have [paired fail-over regions](/azure/availability-zones/cross-region-replication-azure).
+Authoring regions have [paired fail-over regions](/azure/reliability/cross-region-replication-azure).
 
 The following publishing regions do not have a failover region:
 
diff --git a/articles/ai-services/qnamaker/how-to/configure-qna-maker-resources.md b/articles/ai-services/qnamaker/how-to/configure-qna-maker-resources.md
@@ -97,7 +97,7 @@ The primary objective of the business continuity plan is to create a resilient k
 
 The high-level idea as represented above is as follows:
 
-1. Set up two parallel [QnA Maker services](set-up-qnamaker-service-azure.md) in [Azure paired regions](/azure/availability-zones/cross-region-replication-azure).
+1. Set up two parallel [QnA Maker services](set-up-qnamaker-service-azure.md) in [Azure paired regions](/azure/reliability/cross-region-replication-azure).
 
 1. [Backup](/azure/app-service/manage-backup) your primary QnA Maker App service and [restore](/azure/app-service/manage-backup) it in the secondary setup. This will ensure that both setups work with the same hostname and keys.
 
diff --git a/articles/ai-services/speech-service/resiliency-and-recovery-plan.md b/articles/ai-services/speech-service/resiliency-and-recovery-plan.md
@@ -115,6 +115,6 @@ Check the [public voices available](language-support.md?tabs=tts). You can also
 
 ### Speaker recognition
 
-Speaker recognition uses [Azure paired regions](/azure/availability-zones/cross-region-replication-azure) to automatically fail over operations. Speaker enrollments and voice signatures are backed up regularly to prevent data loss and to be used if there's an outage.
+Speaker recognition uses [Azure paired regions](/azure/reliability/cross-region-replication-azure) to automatically fail over operations. Speaker enrollments and voice signatures are backed up regularly to prevent data loss and to be used if there's an outage.
 
 During an outage, the speaker recognition service automatically fails over to a paired region and use the backed-up data to continue processing requests until the main region is back online.
diff --git a/articles/ai-studio/how-to/disaster-recovery.md b/articles/ai-studio/how-to/disaster-recovery.md
@@ -104,7 +104,7 @@ To enable fast recovery and restart in the secondary region, we recommend the fo
 
 Certain Azure services support availability zones. For regions that support availability zones, if a zone goes down any project pauses and data should be saved. However, the data is unavailable to refresh until the zone is back online.
 
-For more information, see [Availability zone service and regional support](/azure/reliability/availability-zones-service-support).
+For more information, see [Availability zone service support](/azure/reliability/availability-zones-service-support).
 
 ### Deploy critical components to multiple regions
 
diff --git a/articles/machine-learning/how-to-access-azureml-behind-firewall.md b/articles/machine-learning/how-to-access-azureml-behind-firewall.md
@@ -128,7 +128,7 @@ When using Azure Machine Learning __compute instance__ or __compute cluster__ (_
 
 # [IP Address routes](#tab/ipaddress)
 
-For the Azure Machine Learning service, you must add the IP address of both the __primary__ and __secondary__ regions. To find the secondary region, see the [Cross-region replication in Azure](/azure/availability-zones/cross-region-replication-azure). For example, if your Azure Machine Learning service is in East US 2, the secondary region is Central US. 
+For the Azure Machine Learning service, you must add the IP address of both the __primary__ and __secondary__ regions. To find the secondary region, see the [Cross-region replication in Azure](/azure/reliability/cross-region-replication-azure). For example, if your Azure Machine Learning service is in East US 2, the secondary region is Central US. 
 
 To get a list of IP addresses of the Azure Machine Learning service, download the [Azure IP Ranges and Service Tags](https://www.microsoft.com/download/details.aspx?id=56519) and search the file for `AzureMachineLearning.<region>`, where `<region>` is your Azure region.
 
diff --git a/articles/machine-learning/how-to-deploy-kubernetes-extension.md b/articles/machine-learning/how-to-deploy-kubernetes-extension.md
@@ -42,7 +42,7 @@ In this article, you can learn:
 - [Using a service principal with AKS](/azure/aks/kubernetes-service-principal) is **not supported** by Azure Machine Learning. The AKS cluster must use a **managed identity** instead. Both **system-assigned managed identity** and **user-assigned managed identity** are supported. For more information, see [Use a managed identity in Azure Kubernetes Service](/azure/aks/use-managed-identity).
     -  When your AKS cluster used service principal is converted to use Managed Identity, before installing the extension, all node pools need to be deleted and recreated, rather than updated directly.
 - [Disabling local accounts](/azure/aks/manage-local-accounts-managed-azure-ad#disable-local-accounts) for AKS is **not supported**  by Azure Machine Learning. When the AKS Cluster is deployed, local accounts are enabled by default.
-- If your AKS cluster has an [Authorized IP range enabled to access the API server](/azure/aks/api-server-authorized-ip-ranges), enable the Azure Machine Learning control plane IP ranges for the AKS cluster. The Azure Machine Learning control plane is deployed across paired regions. Without access to the API server, the machine learning pods can't be deployed. Use the [IP ranges](https://www.microsoft.com/download/confirmation.aspx?id=56519) for both the [paired regions](/azure/availability-zones/cross-region-replication-azure) when enabling the IP ranges in an AKS cluster.
+- If your AKS cluster has an [Authorized IP range enabled to access the API server](/azure/aks/api-server-authorized-ip-ranges), enable the Azure Machine Learning control plane IP ranges for the AKS cluster. The Azure Machine Learning control plane is deployed across paired regions. Without access to the API server, the machine learning pods can't be deployed. Use the [IP ranges](https://www.microsoft.com/download/confirmation.aspx?id=56519) for both the [paired regions](/azure/reliability/cross-region-replication-azure) when enabling the IP ranges in an AKS cluster.
 - Azure Machine Learning doesn't support attaching an AKS cluster cross subscription. If you have an AKS cluster in a different subscription, you must first [connect it to Azure-Arc](/azure/azure-arc/kubernetes/quickstart-connect-cluster) and specify in the same subscription as your Azure Machine Learning workspace.
 - Azure Machine Learning doesn't guarantee support for all preview stage features in AKS. For example, [Microsoft Entra pod identity](/azure/aks/use-azure-ad-pod-identity) isn't supported.
 - If you've followed the steps from [Azure Machine Learning AKS v1 document](./v1/how-to-create-attach-kubernetes.md?view=azureml-api-1&preserve-view=true) to create or attach your AKS as inference cluster, use the following link to [clean up the legacy azureml-fe related resources](./v1/how-to-create-attach-kubernetes.md?view=azureml-api-1&preserve-view=true#delete-azureml-fe-related-resources) before you continue the next step.
diff --git a/articles/machine-learning/how-to-high-availability-machine-learning.md b/articles/machine-learning/how-to-high-availability-machine-learning.md
@@ -127,7 +127,7 @@ __Data services__
 
 Certain Azure services support availability zones. For regions that support availability zones, if a zone goes down any workload pauses and data should be saved. However, the data is unavailable to refresh until the zone is back online.
 
-For more information, see [Availability zone service and regional support](/azure/reliability/availability-zones-service-support).
+For more information, see [Availability zone service support](/azure/reliability/availability-zones-service-support).
 
 ### Deploy critical components to multiple regions
 
diff --git a/articles/machine-learning/v1/how-to-create-attach-kubernetes.md b/articles/machine-learning/v1/how-to-create-attach-kubernetes.md
@@ -45,7 +45,7 @@ Azure Machine Learning can deploy trained machine learning models to Azure Kuber
 
 - To attach an AKS cluster, the service principal/user performing the operation must be assigned the __Owner or contributor__ Azure role-based access control (Azure RBAC) role on the Azure resource group that contains the cluster. The service principal/user must also be assigned [Azure Kubernetes Service Cluster Admin Role](/azure/role-based-access-control/built-in-roles#azure-kubernetes-service-cluster-admin-role) on the cluster.
 
-- If you **attach** an AKS cluster, which has an [Authorized IP range enabled to access the API server](/azure/aks/api-server-authorized-ip-ranges), enable the Azure Machine Learning control plane IP ranges for the AKS cluster. The Azure Machine Learning control plane is deployed across paired regions and deploys inference pods on the AKS cluster. Without access to the API server, the inference pods cannot be deployed. Use the [IP ranges](https://www.microsoft.com/download/confirmation.aspx?id=56519) for both the [paired regions](/azure/availability-zones/cross-region-replication-azure) when enabling the IP ranges in an AKS cluster.
+- If you **attach** an AKS cluster, which has an [Authorized IP range enabled to access the API server](/azure/aks/api-server-authorized-ip-ranges), enable the Azure Machine Learning control plane IP ranges for the AKS cluster. The Azure Machine Learning control plane is deployed across paired regions and deploys inference pods on the AKS cluster. Without access to the API server, the inference pods cannot be deployed. Use the [IP ranges](https://www.microsoft.com/download/confirmation.aspx?id=56519) for both the [paired regions](/azure/reliability/cross-region-replication-azure) when enabling the IP ranges in an AKS cluster.
 
     Authorized IP ranges only works with Standard Load Balancer.
 
diff --git a/articles/machine-learning/v1/how-to-high-availability-machine-learning.md b/articles/machine-learning/v1/how-to-high-availability-machine-learning.md
@@ -73,7 +73,7 @@ The rest of this article describes the actions you need to take to make each of
 A multi-regional deployment relies on creation of Azure Machine Learning and other resources (infrastructure) in two Azure regions. If a regional outage occurs, you can switch to the other region. When planning on where to deploy your resources, consider:
 
 * __Regional availability__: Use regions that are close to your users. To check regional availability for Azure Machine Learning, see [Azure products by region](https://azure.microsoft.com/global-infrastructure/services/).
-* __Azure paired regions__: Paired regions coordinate platform updates and prioritize recovery efforts where needed. For more information, see [Azure paired regions](/azure/availability-zones/cross-region-replication-azure).
+* __Azure paired regions__: Paired regions coordinate platform updates and prioritize recovery efforts where needed. For more information, see [Azure paired regions](/azure/reliability/cross-region-replication-azure).
 * __Service availability__: Decide whether the resources used by your solution should be hot/hot, hot/warm, or hot/cold.
     
     * __Hot/hot__: Both regions are active at the same time, with one region ready to begin use immediately.
diff --git a/articles/search/search-create-service-portal.md b/articles/search/search-create-service-portal.md
@@ -105,7 +105,7 @@ Generally, choose a region near you, unless the following considerations apply:
 
 1. Do you have a specific tier in mind? Check [region availability by tier](search-sku-tier.md#region-availability-by-tier).
 
-1. Do you have business continuity and disaster recovery (BCDR) requirements? Create two or more search services in [regional pairs](/azure/availability-zones/cross-region-replication-azure#azure-paired-regions) within [availability zones](search-reliability.md#availability-zones). For example, if you're operating in North America, you might choose East US and West US, or North Central US and South Central US, for each search service.
+1. Do you have business continuity and disaster recovery (BCDR) requirements? Create two or more search services in [regional pairs](/azure/reliability/cross-region-replication-azure#azure-paired-regions) within [availability zones](search-reliability.md#availability-zones). For example, if you're operating in North America, you might choose East US and West US, or North Central US and South Central US, for each search service.
 
 1. Do you need [AI enrichment](cognitive-search-concept-intro.md), [integrated data chunking and vectorization](vector-search-integrated-vectorization.md), or [multimodal image search](search-get-started-portal-image-search.md)? Azure AI Search, Azure OpenAI, and Azure AI multiservice must coexist in the same region.
 
@@ -188,7 +188,7 @@ Most customers use just one service provisioned at a tier [sufficient for expect
 
 Although most customers use just one service, service redundancy might be necessary if operational requirements include the following:
 
-+ [Business continuity and disaster recovery (BCDR)](/azure/availability-zones/cross-region-replication-azure). Azure AI Search doesn't provide instant failover if there's an outage.
++ [Business continuity and disaster recovery (BCDR)](/azure/reliability/cross-region-replication-azure). Azure AI Search doesn't provide instant failover if there's an outage.
 
 + [Multitenant architectures](search-modeling-multitenant-saas-applications.md) sometimes call for two or more services.
 
diff --git a/articles/search/search-region-support.md b/articles/search/search-region-support.md
@@ -132,5 +132,5 @@ AI service integration refers to internal connections to an Azure AI multi-servi
 - [Azure AI Studio region availability](/azure/ai-studio/reference/region-support)
 - [Azure OpenAI model region availability](/azure/ai-services/openai/concepts/models#model-summary-table-and-region-availability)
 - [Azure AI Vision region list](/azure/ai-services/computer-vision/overview-image-analysis#region-availability)
-- [Availability zone region availability](/azure/reliability/availability-zones-service-support#azure-regions-with-availability-zone-support)
+- [Availability zone region availability](/azure/reliability/availability-zones-region-support)
 - [Azure product by region page](https://azure.microsoft.com/explore/global-infrastructure/products-by-region/?products=search)
diff --git a/articles/search/search-reliability.md b/articles/search/search-reliability.md
@@ -43,7 +43,7 @@ No Service Level Agreement (SLA) is provided for the *Free* tier. For more infor
 
 ## Availability zone support
 
-[Availability zones](/azure/availability-zones/az-overview) 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. In Azure AI Search, individual replicas are the units for zone assignment. A search service runs within one region; its replicas run in different physical data centers (or zones) within that region.
+[Availability zones](/azure/reliability/availability-zones-overview) 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. In Azure AI Search, individual replicas are the units for zone assignment. A search service runs within one region; its replicas run in different physical data centers (or zones) within that region.
 
 Availability zones are used when you add two or more replicas to your search service. Each replica is placed in a different availability zone within the region. If you have more replicas than available zones in the search service region, the replicas are distributed across zones as evenly as possible. There's no specific action on your part, except to [create a search service](search-create-service-portal.md) in a region that provides availability zones, and then to configure the service to [use multiple replicas](search-capacity-planning.md#adjust-capacity).
 
diff --git a/articles/search/toc.yml b/articles/search/toc.yml
@@ -203,7 +203,7 @@ items:
       href: search-sku-manage-costs.md
     - name: Reliability and recovery
       href: search-reliability.md
-    - name: Availability migration guidance
+    - name: Availability zone migration guidance
       href: /azure/reliability/migrate-search-service
     - name: Multi-tenancy
       href: search-modeling-multitenant-saas-applications.md
