Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into nw-redundancy

Author: halkazwini

.openpublishing.redirection.json

@@ -245,7 +245,7 @@
       "redirect_url": "/azure/resiliency/quick-understand-protection-estate",
       "redirect_document_id": false
     },
-      {
+    {
       "source_path": "articles/business-continuity-center/business-continuity-center-support-matrix.md",
       "redirect_url": "/azure/resiliency/resiliency-support-matrix",
       "redirect_document_id": false
@@ -273,42 +273,27 @@
     {
       "source_path": "articles/migrate/concepts-azure-spring-apps-assessment-calculation.md",
       "redirect_url": "/azure/migrate",
-      "redirect_document_id": false,
-      "monikers": [
-        "migrate"
-      ]
+      "redirect_document_id": false
     },
     {
       "source_path": "articles/migrate/how-to-create-azure-spring-apps-assessment.md",
       "redirect_url": "/azure/migrate",
-      "redirect_document_id": false,
-      "monikers": [
-        "migrate"
-      ]
+      "redirect_document_id": false
     },
     {
       "source_path": "articles/migrate/troubleshoot-spring-boot-discovery.md",
       "redirect_url": "/azure/migrate",
-      "redirect_document_id": false,
-      "monikers": [
-        "migrate"
-      ]
+      "redirect_document_id": false
     },
     {
       "source_path": "articles/migrate/tutorial-assess-spring-boot.md",
       "redirect_url": "/azure/migrate",
-      "redirect_document_id": false,
-      "monikers": [
-        "migrate"
-      ]
+      "redirect_document_id": false
     },
     {
       "source_path": "articles/migrate/tutorial-discover-spring-boot.md",
       "redirect_url": "/azure/migrate",
-      "redirect_document_id": false,
-      "monikers": [
-        "migrate"
-      ]
+      "redirect_document_id": false
     },
     {
       "source_path": "articles/azure-functions/functions-proxies.md",
@@ -1242,7 +1227,8 @@
     },
     {
       "source_path": "articles/databox-online/azure-stack-edge-2301-release-notes.md",
-      "redirect_url": "/previous-versions/azure/databox-online/azure-stack-edge-2301-release-notes"
+      "redirect_url": "/previous-versions/azure/databox-online/azure-stack-edge-2301-release-notes",
+      "redirect_document_id": false
     },
     {
       "source_path": "articles/network-watcher/nsg-flow-logs-rest.md",
@@ -6394,8 +6380,7 @@
       "redirect_url": "/azure/cyclecloud/release-notes/ccws/2025-02-06",
       "redirect_document_id": false
     },
-
-    {  
+    {
       "source_path": "articles/app-service/sre-agent-overview.md",
       "redirect_url": "/azure/sre-agent/overview",
       "redirect_document_id": false
@@ -6445,26 +6430,11 @@
       "redirect_url": "/azure/iot-hub-device-update/",
       "redirect_document_id": false
     },
-    {
-      "source_path": "articles/reliability/asm-retirement.md",
-      "redirect_url": "/azure/azure-resource-manager/management/asm-retirement",
-      "redirect_document_id": false
-    },
-    {
-      "source_path": "articles/reliability/reliability-azure-container-apps.md",
-      "redirect_url": "/azure/reliability/reliability-container-apps",
-      "redirect_document_id": false
-    },
     {
       "source_path": "articles/storage/container-storage/container-storage-aks-quickstart.md",
       "redirect_url": "/azure/storage/container-storage/install-container-storage-aks",
       "redirect_document_id": true
     },
-    {
-      "source_path": "articles/reliability/reliability-cosmos-mongodb.md",
-      "redirect_url": "/azure/reliability/reliability-documentdb",
-      "redirect_document_id": true
-    },
     {
       "source_path": "articles/communications-gateway/connectivity.md",
       "redirect_url": "/previous-versions/azure/communications-gateway/connectivity",
@@ -6654,7 +6624,7 @@
       "source_path": "articles/communications-gateway/whats-new.md",
       "redirect_url": "/previous-versions/azure/communications-gateway/whats-new",
       "redirect_document_id": false
-      },
+    },
     {
       "source_path": "articles/vpn-gateway/about-zone-redundant-vnet-gateways.md",
       "redirect_url": "/azure/reliability/reliability-virtual-network-gateway",
@@ -6665,25 +6635,15 @@
       "redirect_url": "https://learn.microsoft.com/dotnet/api/overview/azure/resourcemanager.dns-readme",
       "redirect_document_id": false
     },
-    { 
+    {
       "source_path": "articles/oracle/oracle-db/exadata-vm-clusters.md",
       "redirect_url": "/azure/oracle/oracle-db/database-overview",
       "redirect_document_id": false
     },
-    { 
-      "source_path": "articles/reliability/reliability-health-insights.md",
-      "redirect_url": "/azure/azure-health-insights/reliability-health-insights",
-      "redirect_document_id": false
-    },
-    {
-      "source_path": "articles/reliability/migrate-load-balancer.md",
-      "redirect_url": "/azure/reliability/reliability-load-balancer",
-      "redirect_document_id": false
-    },
     {
       "source_path": "articles/nat-gateway/nat-availability-zones.md",
       "redirect_url": "/azure/reliability/reliability-nat-gateway",
       "redirect_document_id": false
     }
   ]
-}
+}

articles/api-center/TOC.yml

@@ -99,7 +99,7 @@
 - name: API center management and operations
   items:
   - name: Reliability
-    href: ../reliability/reliability-api-center.md?toc=/azure/api-center/toc.json&bc=/azure/api-center/breadcrumb/toc.json
+    href: /azure/reliability/reliability-api-center?toc=/azure/api-center/toc.json&bc=/azure/api-center/breadcrumb/toc.json
 - name: Reference
   items:
   - name: Azure CLI

articles/api-management/api-management-howto-deploy-multi-region.md

@@ -35,7 +35,7 @@ When adding a region, you configure:
 
 ## Prerequisites
 
-* Thoroughly understand all [requirements and considerations for enabling multi-region deployment in API Management](../reliability/reliability-api-management.md).
+* Thoroughly understand all [requirements and considerations for enabling multi-region deployment in API Management](/azure/reliability/reliability-api-management).
 
 * If you haven't created an API Management service instance, see [Create an API Management service instance](get-started-create-service-instance.md). Select the Premium service tier.
 
@@ -188,7 +188,7 @@ This section provides considerations for multi-region deployments when the API M
 
 ## Related content
 
-* Learn more about [reliability in API Management](../reliability/reliability-api-management.md)
+* Learn more about [reliability in API Management](/azure/reliability/reliability-api-management)
 
 * Learn more about enabling [availability zone support](enable-availability-zone-support.md) for an API Management instance.
 

articles/api-management/api-management-howto-disaster-recovery-backup-restore.md

@@ -419,7 +419,7 @@ Check out the following related resources for the backup/restore process:
 
 -   [Automating API Management Backup and Restore with Logic Apps](https://github.com/Azure/api-management-samples/tree/master/tutorials/automating-apim-backup-restore-with-logic-apps)
 - [How to move Azure API Management across regions](api-management-howto-migrate.md)
-- API Management **Premium** tier also supports [zone redundancy](../reliability/migrate-api-mgt.md), which provides resiliency and high availability to a service instance in a specific Azure region (location).
+- API Management **Premium** tier also supports [zone redundancy](/azure/reliability/migrate-api-mgt), which provides resiliency and high availability to a service instance in a specific Azure region (location).
 
 [backup an api management service]: #step1
 [restore an api management service]: #step2

articles/api-management/api-management-howto-ip-addresses.md

@@ -136,7 +136,7 @@ In the Developer, Basic, Standard, and Premium tiers of API Management, the publ
 * (Developer and Premium tiers) Azure Virtual Network is added to or removed from the service.
 * (Developer and Premium tiers) API Management is switched between external and internal virtual network deployment mode.
 * (Developer and Premium tiers) API Management is moved to a different subnet or configured with a different public IP address resource.
-* (Premium tier) [Availability zones](../reliability/migrate-api-mgt.md) are enabled, added, or removed.
+* (Premium tier) [Availability zones](/azure/reliability/migrate-api-mgt) are enabled, added, or removed.
 * (Premium tier) In [multi-regional deployments](api-management-howto-deploy-multi-region.md), the regional IP address changes if a region is vacated and then reinstated.
 
     > [!IMPORTANT]

articles/api-management/enable-availability-zone-support.md

@@ -16,7 +16,7 @@ ms.custom: references_regions, subject-reliability
 
 This article describes how to enable and configure availability zones on an Azure API Management instance.
 
-For more detailed information about reliability features of API Management, such as availability zones and multiregion deployments, see [Reliability in API Management](../reliability/reliability-api-management.md).
+For more detailed information about reliability features of API Management, such as availability zones and multiregion deployments, see [Reliability in API Management](/azure/reliability/reliability-api-management).
 
 
 ## Availability zone support
@@ -36,14 +36,14 @@ When you create a new API Management instance in the **Premium** tier in a regio
 - **Manual:** API Management provides manual availability zone support when you explicitly specify which availability zones to use.
 
 > [!IMPORTANT]
-> To ensure the reliability of your API Management instance, use the automatic availability zone support. To achieve maximum zone redundancy, deploy a minimum of two units in each region where you deploy API Management to ensure that an availability zone outage doesn't affect your instance. For more information, see [Reliability in API Management](../reliability/reliability-api-management.md).
+> To ensure the reliability of your API Management instance, use the automatic availability zone support. To achieve maximum zone redundancy, deploy a minimum of two units in each region where you deploy API Management to ensure that an availability zone outage doesn't affect your instance. For more information, see [Reliability in API Management](/azure/reliability/reliability-api-management).
 
 ### Manual availability zone support
 
 We recommend automatic availability zone configuration in the Premium tier, but you can manually configure or update availability zones for an existing location of your API Management instance. The following sections provide steps for manually configuring zone redundancy on an existing location of your API Management instance, depending on whether the instance is injected in a virtual network.
 
 > [!NOTE]
-> You can optionally enable a *zonal* configuration, where the API Management instance or location is deployed in a single availability zone. Because it doesn't provide resiliency to an outage in that zone, this configuration generally isn't recommended except for specific scenarios. For more information, see [Reliability in API Management](../reliability/reliability-api-management.md).
+> You can optionally enable a *zonal* configuration, where the API Management instance or location is deployed in a single availability zone. Because it doesn't provide resiliency to an outage in that zone, this configuration generally isn't recommended except for specific scenarios. For more information, see [Reliability in API Management](/azure/reliability/reliability-api-management).
 
 > [!CAUTION]
 > If you manually configure availability zones on an API Management instance that's configured with autoscaling, you might need to adjust your autoscale settings after configuration. In this case, the number of API Management units in autoscale rules and limits must be a multiple of the number of zones. If you use the automatic availability zone support, you don't need to adjust your autoscale settings. 
@@ -58,15 +58,15 @@ In the **Premium v2** tier, you can enable availability zone support only when y
 
 #### [Premium](#tab/prem)
 
-* Your instance must be in one of the [Azure regions that support availability zones](../reliability/regions-list.md).
+* Your instance must be in one of the [Azure regions that support availability zones](/azure/reliability/regions-list).
 
 * If you don't have an API Management instance, create one by following the [create a new API Management instance by using the Azure portal](../api-management/get-started-create-service-instance.md) quickstart. Select the **Premium** service tier.
 
 * If you have an existing API Management instance, make sure that it's in the **Premium** (classic) tier. If it isn't, [upgrade to the Premium tier](../api-management/upgrade-and-scale.md#change-your-api-management-service-tier).
 
 #### [Premium v2](#tab/premv2)
 
-* Choose an Azure region that supports both [Premium v2 instances](api-management-region-availability.md) and [availability zones](../reliability/regions-list.md).
+* Choose an Azure region that supports both [Premium v2 instances](api-management-region-availability.md) and [availability zones](/azure/reliability/regions-list).
 
 ---
 
@@ -86,7 +86,7 @@ In the **Premium** tier, availability zone support is automatically enabled when
 
 To manually configure availability zone support on an existing location of an API Management instance, follow these steps:
 
-1. Thoroughly understand all [requirements and considerations for availability zones in API Management](../reliability/reliability-api-management.md).
+1. Thoroughly understand all [requirements and considerations for availability zones in API Management](/azure/reliability/reliability-api-management).
 
 1. In the Azure portal, go to your API Management instance.
 
@@ -106,7 +106,7 @@ To manually configure availability zone support on an existing location of an AP
 
 To manually configure availability zone support on an existing location of an API Management instance that's injected in a virtual network, follow these steps:
 
-1. Review all [requirements and considerations for enabling zone redundancy in API Management](../reliability/reliability-api-management.md).
+1. Review all [requirements and considerations for enabling zone redundancy in API Management](/azure/reliability/reliability-api-management).
 
 1. Create a public IP address in the location to enable availability zones. For detailed requirements, see the [virtual networking guidance](../api-management/api-management-using-with-vnet.md?tabs=stv2#prerequisites).
 
@@ -130,7 +130,7 @@ To manually configure availability zone support on an existing location of an AP
 
 To add a new location to your API Management instance and to configure availability zones in that location, follow these steps:
 
-1. Thoroughly understand all [requirements and considerations for enabling availability zones in API Management](../reliability/reliability-api-management.md).
+1. Thoroughly understand all [requirements and considerations for enabling availability zones in API Management](/azure/reliability/reliability-api-management).
 
 1. If your API Management instance is deployed in a virtual network in the primary location, set up a [virtual network](../api-management/api-management-using-with-vnet.md), subnet, and optional public IP address in the new location where you plan to enable availability zones.
 
@@ -169,8 +169,8 @@ You can enable zone redundancy when you create a new API Management instance in
 
 ## Related content
 
-- [Reliability in API Management](../reliability/reliability-api-management.md)
+- [Reliability in API Management](/azure/reliability/reliability-api-management)
 - [Architecture best practices for API Management](/azure/well-architected/service-guides/azure-api-management)
 - [Design review checklist for reliability](/azure/well-architected/reliability/checklist)
-- [Azure services with availability zones](../reliability/availability-zones-service-support.md)
-- [Azure regions with availability zones](../reliability/regions-list.md)
+- [Azure services with availability zones](/azure/reliability/availability-zones-service-support)
+- [Azure regions with availability zones](/azure/reliability/regions-list)