update links and format about 1/3 of the articles

Author: mumian

articles/azure-resource-manager/management/relocation/overview-relocation.md

@@ -37,19 +37,19 @@ The following tables provide links to each Azure service relocation document. Th
 | --- | --- | --- | ---|
 |[Azure Event Hubs](relocation-event-hub.md)| ✅   | ❌| ❌ |
 |[Azure Event Hubs Cluster](relocation-event-hub-cluster.md)| ✅ | ❌  | ❌ |
-|[Azure Stream Analytics -  Stream Analytics jobs](../../stream-analytics/copy-job.md?toc=/azure/operational-excellence/toc.json)| ✅ | ✅|  ❌  |
-|[Azure Stream Analytics -  Stream Analytics cluster](../../stream-analytics/move-cluster.md?toc=/azure/operational-excellence/toc.json)|✅ | ✅|  ❌  |
+|[Azure Stream Analytics -  Stream Analytics jobs](../../../stream-analytics/copy-job.md?toc=/azure/operational-excellence/toc.json)| ✅ | ✅|  ❌  |
+|[Azure Stream Analytics -  Stream Analytics cluster](../../../stream-analytics/move-cluster.md?toc=/azure/operational-excellence/toc.json)|✅ | ✅|  ❌  |
 |[Power BI](/power-bi/admin/service-admin-region-move?toc=/azure/operational-excellence/toc.json)| ✅ |❌ | ❌ |
 
 ### Compute
 
 | Product  | Relocation | Relocation with data migration | Resource Mover |
 | --- | --- | --- | ---|
-|[Azure App Service](../../app-service/manage-move-across-regions.md?toc=/azure/operational-excellence/toc.json)|✅  |  ❌| ❌ |
-|[Azure Batch](../../batch/account-move.md?toc=/azure/operational-excellence/toc.json)|✅ | ✅|  ❌  |
+|[Azure App Service](../../../app-service/manage-move-across-regions.md?toc=/azure/operational-excellence/toc.json)|✅  |  ❌| ❌ |
+|[Azure Batch](../../../batch/account-move.md?toc=/azure/operational-excellence/toc.json)|✅ | ✅|  ❌  |
 |[Azure Functions](relocation-functions.md)|✅  |❌  | ❌ |
 |[Azure Static Web Apps](./relocation-static-web-apps.md) |  ✅ |❌ | ❌ |
-|[Azure Virtual Machines]( ../../resource-mover/tutorial-move-region-virtual-machines.md?toc=/azure/operational-excellence/toc.json)| ❌ | ❌|  ✅  |
+|[Azure Virtual Machines]( ../../../resource-mover/tutorial-move-region-virtual-machines.md?toc=/azure/operational-excellence/toc.json)| ❌ | ❌|  ✅  |
 |[Azure Virtual Machine Scale Sets](./relocation-virtual-machine-scale-sets.md)|❌  |✅   | ❌ |
 
 ### Containers
@@ -64,7 +64,7 @@ The following tables provide links to each Azure service relocation document. Th
 
 | Product  | Relocation | Relocation with data migration | Resource Mover |
 | --- | --- | --- | ---|
-|[Azure Cache for Redis](../../azure-cache-for-redis/cache-moving-resources.md?toc=/azure/operational-excellence/toc.json)| ✅ |  ❌| ❌ |
+|[Azure Cache for Redis](../../../azure-cache-for-redis/cache-moving-resources.md?toc=/azure/operational-excellence/toc.json)| ✅ |  ❌| ❌ |
 |[Azure Cosmos DB](relocation-cosmos-db.md)|✅ | ✅|  ❌  |
 |[Azure Database for MariaDB Server](/azure/mariadb/howto-move-regions-portal?toc=/azure/operational-excellence/toc.json)|✅ | ✅|  ❌  |
 |[Azure Database for MySQL Server](/azure/mysql/howto-move-regions-portal?toc=/azure/operational-excellence/toc.json)|✅ | ✅|  ❌  |
@@ -74,22 +74,22 @@ The following tables provide links to each Azure service relocation document. Th
 
 | Product  | Relocation |Relocation with data migration |  Resource Mover |
 | --- | --- | --- | ---|
-|[Azure API Management](../../api-management/api-management-howto-migrate.md?toc=/azure/operational-excellence/toc.json)| ✅ | ✅|  ❌  |
-|[Azure Logic apps](../../logic-apps/move-logic-app-resources.md?toc=/azure/operational-excellence/toc.json)|  ✅| ❌ | ❌ |
+|[Azure API Management](../../../api-management/api-management-howto-migrate.md?toc=/azure/operational-excellence/toc.json)| ✅ | ✅|  ❌  |
+|[Azure Logic apps](../../../logic-apps/move-logic-app-resources.md?toc=/azure/operational-excellence/toc.json)|  ✅| ❌ | ❌ |
 
 ### Internet of Things
 
 | Product  | Relocation |Relocation with data migration |  Resource Mover |
 | --- | --- | --- | ---|
-|[Azure API Management](../../api-management/api-management-howto-migrate.md?toc=/azure/operational-excellence/toc.json)| ✅ | ✅|  ❌  |
+|[Azure API Management](../../../api-management/api-management-howto-migrate.md?toc=/azure/operational-excellence/toc.json)| ✅ | ✅|  ❌  |
 |[Azure Cosmos DB](relocation-cosmos-db.md)|✅ | ✅|  ❌  |
 |[Azure Event Grid domains](relocation-event-grid-domains.md)| ✅ | ❌| ❌ |
 |[Azure Event Grid custom topics](relocation-event-grid-custom-topics.md)| ✅ | ❌| ❌ |
 |[Azure Event Grid system topics](relocation-event-grid-system-topics.md)| ✅ | ❌| ❌ |
 |[Azure Functions](relocation-functions.md)|✅  |❌  | ❌ |
 |[Azure IoT Hub](/azure/iot-hub/iot-hub-how-to-clone?toc=/azure/operational-excellence/toc.json)| ✅ | ✅|  ❌  |
-|[Azure Stream Analytics -  Stream Analytics jobs](../../stream-analytics/copy-job.md?toc=/azure/operational-excellence/toc.json)| ✅ | ✅|  ❌  |
-|[Azure Stream Analytics -  Stream Analytics cluster](../../stream-analytics/move-cluster.md?toc=/azure/operational-excellence/toc.json)|✅ | ✅|  ❌  |
+|[Azure Stream Analytics -  Stream Analytics jobs](../../../stream-analytics/copy-job.md?toc=/azure/operational-excellence/toc.json)| ✅ | ✅|  ❌  |
+|[Azure Stream Analytics -  Stream Analytics cluster](../../../stream-analytics/move-cluster.md?toc=/azure/operational-excellence/toc.json)|✅ | ✅|  ❌  |
 
 ### Management and governance
 
@@ -105,7 +105,7 @@ The following tables provide links to each Azure service relocation document. Th
 | Product  | Relocation |Relocation with data migration |  Resource Mover |
 | --- | --- | --- | ---|
 |[Azure Application Gateway and Web Application Firewall](relocation-app-gateway.md)| ✅ | ❌| ❌ |
-|[Azure Load Balancer](../../load-balancer/move-across-regions-external-load-balancer-portal.md)| ✅ | ✅| ❌ |
+|[Azure Load Balancer](../../../load-balancer/move-across-regions-external-load-balancer-portal.md)| ✅ | ✅| ❌ |
 |[Azure Private Link Service](./relocation-private-link.md) | ✅| ❌ | ❌ |
 |[Azure Virtual Network](./relocation-virtual-network.md)|  ✅| ❌  | ✅ |
 |[Azure Virtual Network - Network Security Groups](./relocation-virtual-network-nsg.md)|✅  |❌   | ✅ |

articles/azure-resource-manager/management/relocation/overview.md

@@ -10,15 +10,13 @@ ms.custom:
 
 # Azure Operational Excellence documentation (Preview)
 
-
 The Azure Operational Excellence documentation is an organized collection of service specific guidance in the context of targeted workflow operations. Each service specific operational excellence guidance set is grounded in the [Azure Well-Architected Framework (WAF) principles for Operational Excellence](/azure/well-architected/operational-excellence/principles), and designed based on the [Cloud Adoption Framework (CAF)](/azure/cloud-adoption-framework/) architecture. 
 
 Currently in preview, the Operational Excellence documentation set contains the following service-specific content:
 
 - [Service region relocation](./overview-relocation.md). The region relocation documentation is designed to provide service-specific relocation guidance, so that you can move your services from one region to another safely and with confidence, in accordance with the following Well-architected Framework (WAF) principles:
+
     - [Deploy with confidence](/azure/well-architected/operational-excellence/principles#deploy-with-confidence) 
     - [Adopt safe deployment practices](/azure/well-architected/operational-excellence/principles#adopt-safe-deployment-practices)  
 
     Each service-specific guide is derived from [Relocate cloud workloads](/azure/cloud-adoption-framework/relocate/) in the Cloud Adoption Framework for Azure.
-
-

articles/azure-resource-manager/management/relocation/relocation-app-gateway.md

@@ -13,31 +13,33 @@ ms.custom:
 
 [!INCLUDE [relocate-reasons](./includes/service-relocation-reason-include.md)]
 
- This article covers the recommended approach, guidelines, and practices to relocate Application Gateway and WAF between Azure regions. 
+ This article covers the recommended approach, guidelines, and practices to relocate Application Gateway and WAF between Azure regions.
 
 >[!IMPORTANT]
->The redeployment steps in this document apply only to the application gateway itself and not the backend services to which the application gateway rules are routing traffic. 
+>The redeployment steps in this document apply only to the application gateway itself and not the backend services to which the application gateway rules are routing traffic.
 
 ## Prerequisites
 
 - Verify that your Azure subscription allows you to create Application Gateway SKUs in the target region.
 
 - Plan your relocation strategy with an understanding of all services that are required for your Application Gateway. For the services that are in scope of the relocation, you must select the appropriate relocation strategy.
-    - Ensure that the Application Gateway subnet at the target location has enough address space to accommodate the number of instances required to serve your maximum expected traffic.
 
+  - Ensure that the Application Gateway subnet at the target location has enough address space to accommodate the number of instances required to serve your maximum expected traffic.
+  
 - For Application Gateway's deployment, you must consider and plan the setup of the following sub-resources:
-    - Frontend configuration (Public/Private IP)
-    - Backend Pool Resources (ex. VMs, Virtual Machine Scale Sets, Azure App Services)
-    - Private Link
-    - Certificates
-    - Diagnostic Settings
-    - Alert Notifications
 
- - Ensure that the Application Gateway subnet at the target location has enough address space to accommodate the number of instances required to serve your maximum expected traffic.
+  - Frontend configuration (Public/Private IP)
+  - Backend Pool Resources (ex. VMs, Virtual Machine Scale Sets, Azure App Services)
+  - Private Link
+  - Certificates
+  - Diagnostic Settings
+  - Alert Notifications
+
+- Ensure that the Application Gateway subnet at the target location has enough address space to accommodate the number of instances required to serve your maximum expected traffic.
 
 ## Redeploy
 
-To relocate Application Gateway and optional WAF, you must create a separate Application Gateway deployment with a new public IP address at the target location. Workloads are then migrated from the source Application Gateway setup to the new one.  Since you're changing the public IP address, changes to DNS configuration, virtual networks, and subnets are also required. 
+To relocate Application Gateway and optional WAF, you must create a separate Application Gateway deployment with a new public IP address at the target location. Workloads are then migrated from the source Application Gateway setup to the new one.  Since you're changing the public IP address, changes to DNS configuration, virtual networks, and subnets are also required.
 
 If you only want to relocate in order to gain availability zones support, see [Migrate Application Gateway and WAF to availability zone support](../reliability/migrate-app-gateway-v2.md).
 
@@ -53,7 +55,7 @@ If you only want to relocate in order to gain availability zones support, see [M
 
 1. Create an Application Gateway and configure a new Frontend Public IP Address for the virtual network:
     - Without WAF:  [Create an application gateway](../application-gateway/quick-create-portal.md#create-an-application-gateway).
-    - With WAF: [Create an application gateway with a Web Application Firewall](../web-application-firewall/ag/application-gateway-web-application-firewall-portal.md) 
+    - With WAF: [Create an application gateway with a Web Application Firewall](../web-application-firewall/ag/application-gateway-web-application-firewall-portal.md).
 
 1. If you have a WAF config or custom rules-only WAF Policy, [transition it to to a full WAF policy](../web-application-firewall/ag/migrate-policy.md).
 
@@ -62,24 +64,21 @@ If you only want to relocate in order to gain availability zones support, see [M
 1. Verify that the Application Gateway and WAF are working as intended.
 
 1. Migrate your configuration to the new public IP address.
-    1. Switch Public and Private endpoints in order to point to the new application gateway. 
+    1. Switch Public and Private endpoints in order to point to the new application gateway.
     1. Migrate your DNS configuration to the new Public- and/or Private  IP address.
     1. Update endpoints in consumer applications/services. Consumer application/services updates are usually done by means of a properties change and redeployment. However, perform this method whenever a new hostname is used in respect to deployment in the old region.
 
 1. Delete the source Application Gateway and WAF resources.
 
 ## Relocate certificates for Premium TLS Termination (Application Gateway v2)
 
-
 The certificates for TLS termination can be supplied in two ways:
 
 - *Upload.* Provide an TLS/SSL certificate by directly uploading it to your Application Gateway.
 
-- *Key Vault reference.* Provide a reference to an existing Key Vault certificate when you create a HTTPS/TLS-enabled listener. For more information on downloading a certificate, see [Relocate Key Vault to another region](./relocation-key-vault.md). 
+- *Key Vault reference.* Provide a reference to an existing Key Vault certificate when you create a HTTPS/TLS-enabled listener. For more information on downloading a certificate, see [Relocate Key Vault to another region](./relocation-key-vault.md).
 
 >[!WARNING]
 >References to Key Vaults in other Azure subscriptions are supported, but must be configured via ARM template, Azure PowerShell, CLI, Bicep, etc. Cross-subscription key vault configuration is not supported by Application Gateway via Azure portal.
 
-
-Follow the documented procedure to enable [TLS termination with Key Vault certificates](/azure/application-gateway/key-vault-certs#configure-your-key-vault) for your relocated Application Gateway. 
-
+Follow the documented procedure to enable [TLS termination with Key Vault certificates](/azure/application-gateway/key-vault-certs#configure-your-key-vault) for your relocated Application Gateway.