Merge pull request #249588 from RoseHJM/dtl-cruft-regions

DTL - reduce number of articles

Author: v-regandowner

.openpublishing.redirection.json

@@ -23387,6 +23387,11 @@
             "redirect_url": "/azure/devtest-labs/samples-cli",
             "redirect_document_id": false
         },
+        {
+            "source_path_from_root": "/articles/devtest-labs/how-to-move-schedule-to-new-region.md",
+            "redirect_url": "/azure/devtest-labs/how-to-move-labs",
+            "redirect_document_id": false
+        },
         {
             "source_path_from_root": "/articles/azure/virtual-desktop/azure-advisor.md",
             "redirect_url": "/azure/advisor/advisor-overview",

articles/devtest-labs/TOC.yml

@@ -263,8 +263,6 @@
       href: create-alerts.md
   - name: Move to new region
     href: how-to-move-labs.md
-  - name: Move schedules to another region
-    href: how-to-move-schedule-to-new-region.md
 - name: Reference
   items:
   - name: CLI

articles/devtest-labs/how-to-move-labs.md

@@ -5,12 +5,12 @@ ms.topic: how-to
 ms.custom: devx-track-azurepowershell, UpdateFrequency2
 ms.author: rosemalcolm
 author: RoseHJM
-ms.date: 03/03/2022
+ms.date: 08/28/2023
 ---
 
-# Move DevTest Labs to another region
+# Move DevTest Labs and schedules to another region
 
-To move a lab, create a copy of an existing lab in another region.
+You can move DevTest Labs and their associated schedules to another reason. To move a lab, create a copy of an existing lab in another region. When you've moved your lab, and you have a virtual machine (VM) in the target region, you can move your lab schedules.
 
 In this article, you learn how to:
 > [!div class="checklist"]
@@ -20,6 +20,7 @@ In this article, you learn how to:
 > - Deploy the template to create the new lab in the target region.
 > - Configure the new lab.
 > - Move data to the new  lab.
+> - Move schedules to the new lab.
 > - Delete the resources in the source region.
 
 ## Prerequisites
@@ -34,23 +35,41 @@ In this article, you learn how to:
   - the Stored Secrets
   - PAT tokens of the private Artifact Repos to move the private repos together with the lab.
 
-## Prepare to move
+- When moving a lab schedule, ensure a Compute VM exists in the target region.
 
-To get started, export and modify a Resource Manager template.
+## Move a lab
+
+The following section describes how to create and customize an ARM template to move a lab from one region to another. 
+
+You can move a schedule without moving a lab, if you have a VM in the target region. If you want to move a schedule without moving a lab, see [Move a schedule](#move-a-schedule).
+
+### Prepare to move a lab
 
-### Prepare your Virtual Network
+When you move a lab, there are some steps you must take to prepare for the move. You need to:
+
+- Prepare the virtual network
+- Export an ARM template of the lab
+- Modify the template
+- Deploy the template to move the lab
+- Configure the new lab
+- Swap the OS disks of the Compute VMs under the new VMs
+- Clean up the original lab
+
+#### Prepare the Virtual Network
+
+To get started, export and modify a Resource Manager template.
 
 1. Sign in to the [Azure portal](https://portal.azure.com).
 
 1. If you don't have [Resource Group](../azure-resource-manager/management/manage-resource-groups-portal.md#create-resource-groups) under the target region, create one now.
 
-1. Move your current Virtual Network to the new region and resource group using the steps included in the article, "[Move an Azure virtual network to another region](../virtual-network/move-across-regions-vnet-portal.md)".
+1. Move the current Virtual Network to the new region and resource group using the steps included in the article, "[Move an Azure virtual network to another region](../virtual-network/move-across-regions-vnet-portal.md)".
 
    Alternately, you can create a new virtual network, if you don't have to keep the original one.
 
-### Export an ARM template of your lab.
+#### Export an ARM template of the lab
 
-Next, you export a JSON template contains settings that describe your lab.
+Next, you export a JSON template contains settings that describe the lab.
 
 To export a template by using Azure portal:
 
@@ -64,7 +83,7 @@ To export a template by using Azure portal:
 
    This zip file contains the .json files that comprise the template and scripts to deploy the template. It contains all the resources under your lab listed in ARM template format, except for the Shared Image Gallery resources.
 
-### Modify the template
+#### Modify the template
 
 In order for the ARM template to deploy correctly in the new region, you must change a few parts of the template.
 
@@ -75,8 +94,8 @@ To update the template by using Azure portal:
 1. In **Search the Marketplace**, type **template deployment**, and then press **ENTER**.
 
 1. Select **Template deployment**.
-
-   ![Azure Resource Manager templates library](../storage/common/media/storage-account-move/azure-resource-manager-template-library.png)
+ 
+     :::image type="content" source="./media/how-to-move-labs/azure-resource-manager-template-library.png" alt-text="Screenshot that shows the Azure Marketplace with template deployment selected.":::
 
 1. Select **Create**.
 
@@ -123,7 +142,7 @@ To update the template by using Azure portal:
       }
       ```
 
-   1. Find the `"type": "microsoft.devtestlab/labs/virtualnetworks"` resource. If you created a new virtual network earlier in these steps, you must add the actual subnet name in `/subnets/[SUBNET_NAME]`. If you chose to move the Vnet to a new region, you should skip this step.
+   1. Find the `"type": "microsoft.devtestlab/labs/virtualnetworks"` resource. If you created a new virtual network earlier in these steps, you must add the actual subnet name in `/subnets/[SUBNET_NAME]`. If you chose to move the virtual network to a new region, you should skip this step.
 
    1. Find the `"type": "microsoft.devtestlab/labs/virtualmachines"` resource.
 
@@ -180,7 +199,7 @@ To update the template by using Azure portal:
 
    1. In the editor, save the template.
 
-## Deploy to move
+### Deploy the template to move the lab
 
 Deploy the template to create a new lab in the target region.
 
@@ -203,14 +222,14 @@ Deploy the template to create a new lab in the target region.
 
 1. Select the bell icon (notifications) from the top of the screen to see the deployment status. You shall see **Deployment in progress**. Wait until the deployment is completed.
 
-### Configure the new lab
+#### Configure the new lab
 
 While most Lab resources have been replicated under the new region using the ARM template, a few edits still need to be moved manually.
 
 1. Add the Compute Gallery back to the lab if there are any in the original one.
 1. Add the policies "Virtual machines per user", "Virtual machines per lab" and "Allowed Virtual machine sizes" back to the moved lab
 
-### Swap the OS disks of the Compute VMs under the new VMs.
+#### Swap the OS disks of the Compute VMs under the new VMs
 
 Note the VMs under the new Lab have the same specs as the ones under the old Lab. The only difference is their OS Disks.
 
@@ -247,9 +266,55 @@ Note the VMs under the new Lab have the same specs as the ones under the old Lab
 
    1. Swap the OS disk of the Compute VM under the new lab with the new disk. To learn how, see the article, "[Change the OS disk used by an Azure VM using PowerShell](../virtual-machines/windows/os-disk-swap.md)".
 
+## Move a schedule
+
+There are two ways to move a schedule:
+
+ - Manually recreate the schedules on the moved VMs. This process can be time consuming and error prone. This approach is most useful when you have a few schedules and VMs.
+ - Export and redeploy the schedules by using ARM templates.
+
+Use the following steps to export and redeploy your schedule in another Azure region by using an ARM template:
+
+1. Sign in to the [Azure portal](https://portal.azure.com).
+
+2. Go to the source resource group that held your VMs.
+
+3. On the **Resource Group Overview** page, under **Resources**, select **Show hidden types**.
+
+4. Select all resources with the type **microsoft.devtestlab/schedules**.
+ 
+5. Select **Export template**.
+
+    :::image type="content" source="./media/how-to-move-labs/move-compute-schedule.png" alt-text="Screenshot that shows the hidden resources in a resource group, with schedules selected.":::
+
+6. On the **Export resource group template** page, select **Deploy**.
+
+7. On the **Custom deployment** page, select **Edit template**.
+ 
+8. In the template code, change all instances of `"location": "<old location>"` to `"location": "<new location>"` and then select **Save**.
+
+9. On the **Custom deployment** page, enter values that match the target VM:
+
+   |Name|Value|
+   |----|----|
+   |**Subscription**|Select an Azure subscription.|
+   |**Resource group**|Select the resource group name. |
+   |**Region**|Select a location for the lab schedule. For example, **Central US**. |
+   |**Schedule Name**|Must be a globally unique name. |
+   |**VirtualMachine_xxx_externalId**|Must be the target VM. |
+ 
+    :::image type="content" source="./media/how-to-move-labs/move-schedule-custom-deployment.png" alt-text="Screenshot that shows the custom deployment page, with new location values for the relevant settings.":::
+
+    >[!IMPORTANT]
+    >Each schedule must have a globally unique name; you will need to change the schedule name for the new location.
+
+10. Select **Review and create** to create the deployment.
+
+11. When the deployment is complete, verify that the new schedule is configured correctly on the new VM.
+
 ## Discard or clean up
 
-After the deployment, if you want to start over, you can delete the target lab, and repeat the steps described in the [Prepare](#prepare-to-move) and [Move](#deploy-to-move) sections of this article.
+After the deployment, if you want to start over, you can delete the target lab, and repeat the steps described in the [Prepare](#prepare-to-move-a-lab) and [Move](#deploy-the-template-to-move-the-lab) sections of this article.
 
 To commit the changes and complete the move, you must delete the original lab.
 
@@ -261,10 +326,11 @@ To remove a lab by using the Azure portal:
 
 1. Select **Delete**, and confirm.
 
+You can also choose to clean up the original schedules if they're no longer used. Go to the original schedule resource group (where you exported templates from in step 5 above) and delete the schedule resource.
+
 ## Next steps
 
 In this article, you moved DevTest Labs from one region to another and cleaned up the source resources.  To learn more about moving resources between regions and disaster recovery in Azure, refer to:
 
 - [Move resources to a new resource group or subscription](../azure-resource-manager/management/move-resource-group-and-subscription.md)
-- [Move Azure VMs to another region](../site-recovery/azure-to-azure-tutorial-migrate.md)
-- [Move Microsoft.DevtestLab/schedules to another region](./how-to-move-schedule-to-new-region.md)
+- [Move Azure VMs to another region](../site-recovery/azure-to-azure-tutorial-migrate.md)