fix links, add somil as the author, and format the lists

Author: mumian

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

@@ -91,18 +91,16 @@ When an Azure Virtual Machine (VM) protected by a Recovery Services vault is mov
 You can also choose to write a customized script for bulk VM protection:
 
 ```azurepowershell
-
 https://management.azure.com/Subscriptions/{subscriptionId}/resourceGroups/{vaultresourceGroupName}/providers/Microsoft.RecoveryServices/vaults/{vaultName}/backupFabrics/{fabricName}/protectionContainers/{containerName}/protectedItems/{protectedItemName}?api-version=2019-05-13
-
 ```
 
 1. Prepare Azure Virtual Machines (VMs) for relocation:
 
     1. See the [prerequisites associated with VM relocation](../../../resource-mover/tutorial-move-region-virtual-machines.md#prerequisites) and ensure that the VM is eligible for relocation.
     1. [Select the VM on the **Backup Items** tab](../../../backup/backup-azure-delete-vault.md#delete-protected-items-in-the-cloud) of existing vault’s dashboard and select **Stop protection** followed by retain/delete data as per your requirement. When the backup data for a VM is stopped with retain data, the recovery points remain forever and don’t adhere to any policy.
 
-        >[!Note]
-        >Retaining data in the older vault will incur backup charges. If you no longer wish to retain data to avoid billing, you need to delete the retained backup data using the  [Delete data option](../../../backup/backup-azure-manage-vms.md#delete-backup-data).
+        > [!NOTE]
+        > Retaining data in the older vault will incur backup charges. If you no longer wish to retain data to avoid billing, you need to delete the retained backup data using the  [Delete data option](../../../backup/backup-azure-manage-vms.md#delete-backup-data).
   
     1. Ensure that the VMs are turned on. All VMs’ disks that need to be available in the destination region are attached and initialized in the VMs.
     1. Ensure that VMs have the latest trusted root certificates, and an updated certificate revocation list (CRL). To do so:
@@ -126,8 +124,8 @@ https://management.azure.com/Subscriptions/{subscriptionId}/resourceGroups/{vaul
 1. When Azure File Share is copied across regions, its associated snapshots don’t relocate along with it. To relocate the snapshots data to the new region, you need to relocate the individual files and directories of the snapshots to the Storage Account in the new region by using [AzCopy](../../../storage/common/storage-use-azcopy-files.md#copy-all-file-shares-directories-and-files-to-another-storage-account).
 1. Choose whether you want to retain or delete the snapshots (and the corresponding recovery points) of the original Azure File Share by selecting your file share on the [Backup Items tab](../../../backup/backup-azure-delete-vault.md#delete-protected-items-in-the-cloud) of the original vault’s dashboard. When the backup data for Azure File Share is stopped with retain data, the recovery points remain forever and don’t adhere to any policy.
 
->[!NOTE]
->While configuring File Share, if the Recovery Service Vault isn't available, check to see whether it is associated with another Recovery Service vault.
+> [!NOTE]
+> While configuring File Share, if the Recovery Service Vault isn't available, check to see whether it is associated with another Recovery Service vault.
 
 ### Back up SQL Server/SAP HANA in Azure VM
 
@@ -157,6 +155,6 @@ When you relocate a VM that runs SQL or SAP HANA servers, you will no longer be
 
 1. To backup files, folders, and system state for VMs (Hyper-V & VMware) and other on-premises workloads, see [About the Microsoft Azure Recovery Services (MARS)](../../../backup/backup-azure-about-mars.md).
 1. Download vault credentials to register the server in the vault.
-    :::image type="content" source="media\relocation\backup\mars-agent-credential-download.png" alt-text="Screenshot showing how to download vault credentials to register the server in the vault.":::
+    :::image type="content" source="./media/backup/mars-agent-credential-download.png" alt-text="Screenshot showing how to download vault credentials to register the server in the vault.":::
 1. Reconfigure backup agent on on-premises virtual machine.
-    :::image type="content" source="media\relocation\backup\mars-register-to-target-rsv.png" alt-text="Screenshot showing how to reconfigure an on premise virtual machine.":::
+    :::image type="content" source="./media/backup/mars-register-to-target-rsv.png" alt-text="Screenshot showing how to reconfigure an on premise virtual machine.":::

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

@@ -15,7 +15,6 @@ This article shows you how to relocate Azure Container Registry resources to ano
 ## Prerequisites
 
 - You can only relocate a registry within the same Active Directory tenant. This limitation applies to registries that are encrypted and unencrypted with a [customer-managed key](/azure/container-registry/tutorial-enable-customer-managed-keys).
-
 - If the source registry has [availability zones](../../../reliability/availability-zones-overview.md) enabled, then the target region must also support availability zones. For more information on availability zone support for Azure Container Registry, see [Enable zone redundancy in Azure Container Registry](/azure/container-registry/zone-redundancy).
 
 ## Considerations for Service Endpoints
@@ -115,8 +114,10 @@ az group create --name myResourceGroup --location eastus
 Use the [az deployment group create](/cli/azure/deployment/group#az-deployment-group-create) command to deploy the target registry, using the template:
 
 ```azurecli
-az deployment group create --resource-group myResourceGroup \
-   --template-file template.json --name mydeployment
+az deployment group create \
+  --name mydeployment \
+  --resource-group myResourceGroup \
+  --template-file template.json 
 ```
 
 > [!NOTE]
@@ -130,27 +131,27 @@ After creating the registry in the target region:
 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).
-
-```azurecli
-#!/bin/bash
-# Modify registry names for your environment
-SOURCE_REG=myregistry
-TARGET_REG=targetregistry
-
-# Get list of source repositories
-REPO_LIST=$(az acr repository list \
-    --name $SOURCE_REG --output tsv)
-
-# Enumerate tags and import to target registry
-for repo in $REPO_LIST; do
-    TAGS_LIST=$(az acr repository show-tags --name $SOURCE_REG --repository $repo --output tsv);
-    for tag in $TAGS_LIST; do
-        echo "Importing $repo:$tag";
-        az acr import --name $TARGET_REG --source $SOURCE_REG.azurecr.io/$repo":"$tag;
+    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).
+    
+    ```azurecli
+    #!/bin/bash
+    # Modify registry names for your environment
+    SOURCE_REG=myregistry
+    TARGET_REG=targetregistry
+    
+    # Get list of source repositories
+    REPO_LIST=$(az acr repository list \
+        --name $SOURCE_REG --output tsv)
+    
+    # Enumerate tags and import to target registry
+    for repo in $REPO_LIST; do
+        TAGS_LIST=$(az acr repository show-tags --name $SOURCE_REG --repository $repo --output tsv);
+        for tag in $TAGS_LIST; do
+            echo "Importing $repo:$tag";
+            az acr import --name $TARGET_REG --source $SOURCE_REG.azurecr.io/$repo":"$tag;
+        done
     done
-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:

articles/azure-resource-manager/management/relocation/relocation-cosmos-db.md

@@ -26,8 +26,6 @@ This article describes how to either:
 - When you add or remove locations to an Azure Cosmos account, you can’t simultaneously modify other properties.
 - Identify all Cosmos DB dependent resources.
 
-## Downtime
-
 ## Considerations for Service Endpoints
 
 The virtual network service endpoints for Azure Cosmos DB restrict access to a specified virtual network. The endpoints can also restrict access to a list of IPv4 (internet protocol version 4) address ranges. Any user connecting to the Event Hubs from outside those sources is denied access. If Service endpoints were configured in the source region for the Event Hubs resource, the same would need to be done in the target one.

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

@@ -31,6 +31,7 @@ To get started, export a Resource Manager template. This template contains setti
 1. Choose **Download** in the **Export template** page.
 
     :::image type="content" source="../../../event-hubs/media/move-cluster-across-regions/download-template.png" alt-text="Screenshot showing where to download Resource Manager template" lightbox="../../../event-hubs/media/move-cluster-across-regions/download-template.png":::
+
 1. Locate the .zip file that you downloaded from the portal, and unzip that file to a folder of your choice.
 
    This zip file contains the .json files that include the template and scripts to deploy the template.

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

@@ -15,11 +15,8 @@ If you have other resources in the Azure resource group that contains the Event
 ## Prerequisites
 
 - Ensure that the services and features that your account uses are supported in the target region.
-
 - If you have **capture feature** enabled for event hubs in the namespace, move [Azure Storage or Azure Data Lake Store Gen 2](../../../storage/common/storage-account-move.md) accounts before moving the Event Hubs namespace. You can also move the resource group that contains both Storage and Event Hubs namespaces to the other region by following steps similar to the ones described in this article.
-
 - If the Event Hubs namespace is in an **Event Hubs cluster**, [move the dedicated cluster](../../../event-hubs/move-cluster-across-regions.md) to the **target region** before you go through steps in this article. You can also use the [quickstart template on GitHub](https://github.com/Azure/azure-quickstart-templates/tree/master/quickstarts/microsoft.eventhub/eventhubs-create-cluster-namespace-eventhub/) to create an Event Hubs cluster. In the template, remove the namespace portion of the JSON to create only the cluster.
-
 - Identify all resources dependencies. Depending on how you've deployed Event Hubs, the following services *may* need deployment in the target region:
 
   - [Public IP](/azure/virtual-network/move-across-regions-publicip-portal)

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

@@ -56,29 +56,29 @@ To prepare for relocation, you need to first export and modify the template from
 
 1. Sign in to your Azure subscription with the `Connect-AzAccount` command and follow the on-screen directions:
 
-  ```azurecli
-  Connect-AzAccount
-  ```
+    ```azurecli
+    Connect-AzAccount
+    ```
 
 1. If your identity is associated with more than one subscription, then set your active subscription to subscription of the Azure Firewall resource that you want to move.
 
-  ```azurepowershell
-  $context = Get-AzSubscription -SubscriptionId <subscription-id>
-  Set-AzContext $context
-  ```
+    ```azurepowershell
+    $context = Get-AzSubscription -SubscriptionId <subscription-id>
+    Set-AzContext $context
+    ```
 
 1. Export the template of your source Azure Firewall resource by running the following commands:
 
-  ```azurepowershell
-  $resource = Get-AzResource `
-    -ResourceGroupName <resource-group-name> `
-    -ResourceName <resource-name> `
-    -ResourceType <resource-type>
-  
-  Export-AzResourceGroup `
-    -ResourceGroupName <resource-group-name> `
-    -Resource $resource.ResourceId
-  ```
+    ```azurepowershell
+    $resource = Get-AzResource `
+      -ResourceGroupName <resource-group-name> `
+      -ResourceName <resource-name> `
+      -ResourceType <resource-type>
+    
+    Export-AzResourceGroup `
+      -ResourceGroupName <resource-group-name> `
+      -Resource $resource.ResourceId
+    ```
 
 1. Locate the `template.json` in your current directory.
 
@@ -124,14 +124,14 @@ If you're running classic firewall rules without Firewall policy, migrate to Fir
 
 1. Edit the `location` property in the `template.json` file to the target region (The following example sets the target region to `centralus`.):
 
-  ```json
-  "resources": [
-  {
-    "type": "Microsoft.Network/azureFirewalls",
-    "apiVersion": "2023-09-01",
-    "name": "[parameters('azureFirewalls_fw_name')]",
-    "location": "centralus",}]
-  ```
+    ```json
+    "resources": [
+    {
+      "type": "Microsoft.Network/azureFirewalls",
+      "apiVersion": "2023-09-01",
+      "name": "[parameters('azureFirewalls_fw_name')]",
+      "location": "centralus",}]
+    ```
 
 To find the location code for your target region, see [Data residency in Azure](https://azure.microsoft.com/explore/global-infrastructure/data-residency/#overview).
 
@@ -165,16 +165,16 @@ To find the location code for your target region, see [Data residency in Azure](
 
 1. Edit the `location` property in the `template.json` file to the target region (The following example sets the target region to `centralus`.):
 
-  ```json
-  "resources": [
-    {
-      "type": "Microsoft.Network/azureFirewalls",
-      "apiVersion": "2023-09-01",
-      "name": "[parameters('azureFirewalls_fw_name')]",
-      "location": "centralus",
-    }
-  ]
-  ```
+    ```json
+    "resources": [
+      {
+        "type": "Microsoft.Network/azureFirewalls",
+        "apiVersion": "2023-09-01",
+        "name": "[parameters('azureFirewalls_fw_name')]",
+        "location": "centralus",
+      }
+    ]
+    ```
 
 To find the location code for your target region, see [Data residency in Azure](https://azure.microsoft.com/explore/global-infrastructure/data-residency/#overview).
 

articles/azure-resource-manager/management/relocation/relocation-kubernetes-service.md

@@ -57,14 +57,14 @@ Before you begin the relocation planning stage, first review the following prere
 
 Before you begin the cluster relocation process, make sure to complete the following preparations:
 
--. To accommodate the AKS cluster nodes and pods, if using Azure CNI networking, deploy the virtual network with many subnets of sufficient size.
--. If you're using Azure Key Vault, [Deploy the Key Vault](./relocation-key-vault.md).
--. Ensure that the relevant TLS ingress certificates are available for deployment, ideally in a secure store such as Azure Key Vault.
--. Deploy a container registry. Either sync the source registry images automatically or rebuild and push new images to the target registry using a CI/CD pipeline or script.
--. [Deploy an Azure Monitor workspace](./relocation-log-analytics.md).
--. (Optional) [Deploy Azure Application Gateway](./relocation-app-gateway.md) to handle ingress traffic Application Gateway Ingress Controller (AGIC) can tightly integrate with the cluster
--. Deploy any data sources required by the cluster workload and restore or sync the source data.
--. Execute existing IaC artifacts defined in a CI/CD pipeline that were used to deploy the source cluster and the services it depends upon. Change the code or template input parameters to redeploy to a different resource group and Azure region.
+- To accommodate the AKS cluster nodes and pods, if using Azure CNI networking, deploy the virtual network with many subnets of sufficient size.
+- If you're using Azure Key Vault, [Deploy the Key Vault](./relocation-key-vault.md).
+- Ensure that the relevant TLS ingress certificates are available for deployment, ideally in a secure store such as Azure Key Vault.
+- Deploy a container registry. Either sync the source registry images automatically or rebuild and push new images to the target registry using a CI/CD pipeline or script.
+- [Deploy an Azure Monitor workspace](./relocation-log-analytics.md).
+- (Optional) [Deploy Azure Application Gateway](./relocation-app-gateway.md) to handle ingress traffic Application Gateway Ingress Controller (AGIC) can tightly integrate with the cluster
+- Deploy any data sources required by the cluster workload and restore or sync the source data.
+- Execute existing IaC artifacts defined in a CI/CD pipeline that were used to deploy the source cluster and the services it depends upon. Change the code or template input parameters to redeploy to a different resource group and Azure region.
 
 ## Redeploy
 

articles/azure-resource-manager/management/relocation/relocation-postgresql-flexible-server.md

@@ -22,7 +22,7 @@ For an overview of the region pairs supported by native replication, see [cross-
 Prerequisites only apply to [redeployment with data](#redeploy-with-data). To move your database without data, you can skip to [Prepare](#prepare).
 
 - To relocate PostgreSQL with data from one region to another, you must have an additional compute resource to run the backup and restore tools. The examples in this guide use an Azure VM running Ubuntu 20.04 LTS. The compute resources must:
--
+
   - Have network access to both the source and the target server, either on a private network or by inclusion in the firewall rules.
   - Be located in either the source or target region.
   - Use [Accelerated Networking](/azure/virtual-network/accelerated-networking-overview) (if available).

articles/azure-resource-manager/management/relocation/relocation-private-link.md

@@ -36,7 +36,7 @@ Identify all resources that are used by Private Link Service, such as Standard l
 1. Redeploy the private endpoint into the relocated virtual network.
 1. Configure your DNS settings by following guidance in [Private DNS zone values](/azure/private-link/private-endpoint-dns?branch=main).
 
-:::image type="content" source="media/consumer-provider-endpoint.png" alt-text="Diagram that illustrates relocation process for Private Link service.":::
+    :::image type="content" source="media/consumer-provider-endpoint.png" alt-text="Diagram that illustrates relocation process for Private Link service.":::
 
 ## Next steps
 

articles/azure-resource-manager/management/relocation/relocation-virtual-machine-scale-sets.md

@@ -45,7 +45,7 @@ In this section, follow the instructions to prepare for relocating a Virtual Mac
 
 1. Locate the image reference used by the source Virtual Machine Scale Set and replicate it to the Image Gallery in the target region.
 
-    :::image type="content" source="media\relocation\virtual-machine-scale-sets\image-replication.png" alt-text="Screenshot showing how to locate image of virtual machine.":::
+    :::image type="content" source="media/virtual-machine-scale-sets/image-replication.png" alt-text="Screenshot showing how to locate image of virtual machine.":::
 
 1. Relocate the Load Balancer, along with the public IP by doing one of the following methods:
 
@@ -57,7 +57,7 @@ In this section, follow the instructions to prepare for relocating a Virtual Mac
 
 1. Manually set the source Virtual Machine Scale Set instance count to 0.
 
-    :::image type="content" source="media\relocation\virtual-machine-scale-sets\set-instance-count.png" alt-text="Screenshot showing how to set Virtual Machine Scale Set instance count to 0.":::
+    :::image type="content" source="media/virtual-machine-scale-sets/set-instance-count.png" alt-text="Screenshot showing how to set Virtual Machine Scale Set instance count to 0.":::
 
 1. Export the source Virtual Machine Scale Set template from Azure portal: