fix links

Author: mumian

articles/azure-resource-manager/management/relocation/relocation-container-registry.md

@@ -58,7 +58,7 @@ To understand the possible downtimes involved, see [Cloud Adoption Framework for
 
 ### Export template
 
-To get started, export a Resource Manager template. This template contains settings that describe your Container Registry. For more information on how to use exported templates, see [Use exported template from the Azure portal](../template-tutorial-export-template.md) and the [template reference](/azure/templates/microsoft.containerregistry/registries).
+To get started, export a Resource Manager template. This template contains settings that describe your Container Registry. For more information on how to use exported templates, see [Use exported template from the Azure portal](../../templates/template-tutorial-export-template.md) and the [template reference](/azure/templates/microsoft.containerregistry/registries).
 
 1. In the [Azure portal](https://portal.azure.com), navigate to your source registry.
 1. In the menu, under **Automation**, select **Export template** > **Download**.
@@ -128,9 +128,7 @@ az deployment group create --resource-group myResourceGroup \
 After creating the registry in the target region:
 
 1. Use the [az acr import](/cli/azure/acr#az-acr-import) command, or the equivalent PowerShell command `Import-AzContainerImage`, to import images and other artifacts you want to preserve from the source registry to the target registry. For command examples, see [Import container images to a container registry](/azure/container-registry/container-registry-import-images).
-
 1. Use the Azure CLI commands [az acr repository list](/cli/azure/acr/repository#az-acr-repository-list) and [az acr repository show-tags](/cli/azure/acr/repository#az-acr-repository-show-tags), or Azure PowerShell equivalents, to help enumerate the contents of your source registry.
-
 1. Run the import command for individual artifacts, or script it to run over a list of artifacts.
 
 The following sample Azure CLI script enumerates the source repositories and tags and then imports the artifacts to a target registry in the same Azure subscription. Modify as needed to import specific repositories or tags. To import from a registry in a different subscription or tenant, see examples in [Import container images to a container registry](/azure/container-registry/container-registry-import-images).
@@ -156,19 +154,14 @@ done
 ```
 
 1. Associate the dependent resources to the target Azure Container Registry such as log analytics workspace in Diagnostic settings.
-
 1. Configure Azure Container Registry integration with both type of AKS clusters, provisioned or yet to be provisioned by running the following command:
 
 ```azurecli
-
 Set-AzAksCluster -Name myAKSCluster -ResourceGroupName myResourceGroup -AcrNameToAttach <acr-name>
-
 ```
 
 1. Make the necessary changes to the Kubernetes manifest file to integrate same with relocated Azure Container Registry (ACR).
-
 1. Update development and deployment systems to use the target registry instead of the source registry.
-
 1. Update any client firewall rules to allow access to the target registry.
 
 ## Verify

articles/azure-resource-manager/management/relocation/relocation-event-hub.md

@@ -240,7 +240,7 @@ Modify the template by changing the Event Hubs namespace name and region.
     },
    ```
 
-2. Edit the **location** property in the **template.json** file to the target region. This example sets the target region to `centralus`.
+1. Edit the **location** property in the **template.json** file to the target region. This example sets the target region to `centralus`.
 
    ```json
    "resources": [
@@ -323,38 +323,38 @@ Modify the template by changing the Event Hubs namespace name and region.
    Get-AzLocation | format-table
    ```
 
-3. Remove resources of typ private endpoint in the template.
+1. Remove resources of typ private endpoint in the template.
 
    ```json
     {
         "type": "Microsoft.EventHub/namespaces/privateEndpointConnections",
     }
    ```
 
-4. If you configured a service endpoint in your Event Hubs, in the `networkrulesets` section, under `virtualNetworkRules`, add the rule for the target subnet. Ensure that the `ignoreMissingVnetServiceEndpoint` flag is set to False, so that the IaC fails to deploy the Event Hubs in case the service endpoint isn’t configured in the target region.
+1. If you configured a service endpoint in your Event Hubs, in the `networkrulesets` section, under `virtualNetworkRules`, add the rule for the target subnet. Ensure that the `ignoreMissingVnetServiceEndpoint` flag is set to False, so that the IaC fails to deploy the Event Hubs in case the service endpoint isn’t configured in the target region.
 
-   **parameter.json**
+    **parameter.json**
 
-   ```json
-   {
-     "$schema": "https://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#",
-     "contentVersion": "1.0.0.0",
-     "parameters": {
-       ...
-       "target_vnet_externalid": {
-         "value": "virtualnetwork-externalid"
-       },
-       "target_subnet_name": {
-         "value": "subnet-name"
-       }
-     }
-   }
-   ```
+    ```json
+    {
+      "$schema": "https://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#",
+      "contentVersion": "1.0.0.0",
+      "parameters": {
+        ...
+        "target_vnet_externalid": {
+          "value": "virtualnetwork-externalid"
+        },
+        "target_subnet_name": {
+          "value": "subnet-name"
+        }
+      }
+    }
+    ```
 
-   **_template.json**
+    **_template.json**
 
-   ```json
-  {
+    ```json
+    {
     "type": "Microsoft.EventHub/namespaces/networkrulesets",
     "apiVersion": "2023-01-01-preview",
     "name": "[concat(parameters('namespaces_name'), '/default')]",
@@ -376,10 +376,11 @@ Modify the template by changing the Event Hubs namespace name and region.
       "ipRules": [],
       "trustedServiceAccessEnabled": false
     }
-  }
-  ```
+    }
+    ```
 
 1. Select **Save** to save the template.
+
 ---
 
 ## Redeploy

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

@@ -99,8 +99,8 @@ Then you can package and redeploy the actual application source code or containe
 
 There are several ways to create a function app and related resources in Azure at the target region:
 
-- **Deployment templates**: If you originally deployed your function app using infrastructure-as-code (IaC) files (Bicep, ARM templates, or Terraform), you can update those previous deployments to target the new region and use them to recreate resources in the new region. If you no longer have these deployment files, you can always [download an ARM template for your existing resource group from the Azure portal](../export-template-portal.md).
-- **Azure CLI/PowerShell scripts**: If you originally deployed your function app using Azure CLI or Azure PowerShell scripts, you can update these scripts to instead target the new region and run them again. If you no longer have these scripts, then you can also [download an ARM template for your existing resource group from the Azure portal](../export-template-portal.md).  
+- **Deployment templates**: If you originally deployed your function app using infrastructure-as-code (IaC) files (Bicep, ARM templates, or Terraform), you can update those previous deployments to target the new region and use them to recreate resources in the new region. If you no longer have these deployment files, you can always [download an ARM template for your existing resource group from the Azure portal](../../templates/export-template-portal.md).
+- **Azure CLI/PowerShell scripts**: If you originally deployed your function app using Azure CLI or Azure PowerShell scripts, you can update these scripts to instead target the new region and run them again. If you no longer have these scripts, then you can also [download an ARM template for your existing resource group from the Azure portal](../../templates/export-template-portal.md).  
 - **Azure portal**: If you created your function app in the portal originally or don't feel comfortable using scripts or IaC files, you can just recreate everything in the portal. Make sure to use the same [hosting plan](../../../azure-functions/functions-scale.md#overview-of-plans), [language runtime](../../../azure-functions/supported-languages.md), and language version as your original app.
 
 ### Review configured resources

articles/azure-resource-manager/management/toc.yml

@@ -102,7 +102,7 @@
             - name: Move encrypted Azure VMs to another region
               href: ../../resource-mover/tutorial-move-region-encrypted-virtual-machines.md?toc=/azure/azure-resource-manager/management/toc.json
           - name: Virtual Machine Scale Sets
-            href: ./relocation-virtual-machine-scale-sets.md
+            href: ./relocation/relocation-virtual-machine-scale-sets.md
         - name: Containers
           items:
           - name: Azure Container Registry

articles/backup/toc.yml

@@ -309,7 +309,7 @@
       - name: Delete
         href: backup-azure-delete-vault.md
       - name: Relocate
-        href: ../operational-excellence/relocation-backup.md?toc=/azure/backup/toc.json
+        href: ../azure-resource-manager/management/relocation/relocation-backup.md?toc=/azure/backup/toc.json
       - name: Manage
         href: backup-azure-manage-windows-server.md
     - name: Backup vault

articles/event-grid/toc.yml

@@ -619,11 +619,11 @@ items:
       - name: Relocate
         items:
         - name: Relocate system topics across regions
-          href: ../operational-excellence/relocation-event-grid-system-topics.md?toc=/azure/event-grid/toc.json
+          href: ../azure-resource-manager/management/relocation/relocation-event-grid-system-topics.md?toc=/azure/event-grid/toc.json
         - name: Relocate custom topics across regions
-          href: ../operational-excellence/relocation-event-grid-custom-topics.md?toc=/azure/event-grid/toc.json
+          href: ../azure-resource-manager/management/relocation/relocation-event-grid-custom-topics.md?toc=/azure/event-grid/toc.json
         - name: Relocate domains across regions
-          href: ../operational-excellence/relocation-event-grid-domains.md?toc=/azure/event-grid/toc.json
+          href: ../azure-resource-manager/management/relocation/relocation-event-grid-domains.md?toc=/azure/event-grid/toc.json
       - name: Secure
         items:
         - name: Publish events securely over a private link

articles/event-hubs/TOC.yml

@@ -368,9 +368,9 @@
     - name: Move
       items:
       - name: Move a namespace to another region
-        href: ../operational-excellence/relocation-event-hub.md?toc=/azure/event-hubs/TOC.json
+        href: ../azure-resource-manager/management/relocation/relocation-event-hub.md?toc=/azure/event-hubs/TOC.json
       - name: Move a dedicated cluster to another region
-        href: ../operational-excellence/relocation-event-hub-cluster.md?toc=/azure/event-hubs/TOC.json
+        href: ../azure-resource-manager/management/relocation/relocation-event-hub-cluster.md?toc=/azure/event-hubs/TOC.json
 - name: Reference
   items:
     - name: Monitor data reference

articles/firewall/toc.yml

@@ -210,7 +210,7 @@ items:
   - name: Best practices for performance
     href: firewall-best-practices.md
   - name: Relocate to another region
-    href: ../operational-excellence/relocation-firewall.md?toc=/azure/firewall/toc.json&bc=/azure/firewall/breadcrumb/toc.json
+    href: ../azure-resource-manager/management/relocation/relocation-firewall.md?toc=/azure/firewall/toc.json&bc=/azure/firewall/breadcrumb/toc.json
   - name: Remote work support
     href: remote-work-support.md
 - name: Reference

articles/private-link/toc.yml

@@ -101,7 +101,7 @@
   - name: Manage private endpoints
     href: manage-private-endpoint.md
   - name: Relocate Private Link Service to another region
-    href: ../operational-excellence/relocation-private-link.md?toc=/azure/private-link/toc.json
+    href: ../azure-resource-manager/management/relocation/relocation-private-link.md?toc=/azure/private-link/toc.json
   - name: Azure Security blog
     href: https://techcommunity.microsoft.com/category/azure-network-security/blog/azurenetworksecurityblog
   - name: Network security perimeter

articles/reliability/migrate-monitor-log-analytics.md

@@ -55,7 +55,7 @@ The new cluster isn’t billed during its first day to avoid double billing duri
 
 Learn more about:
 
-- [Relocate Log Analytics workspaces to another region](../operational-excellence/relocation-log-analytics.md)
+- [Relocate Log Analytics workspaces to another region](../azure-resource-manager/management/relocation/relocation-log-analytics.md)
 
 - [Azure Monitor Logs Dedicated Clusters](/azure/azure-monitor/logs/logs-dedicated-clusters)